[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78F325F0VEANPZ4MPEM0XNB":3,"skill-same:01M78F325F0VEANPZ4MPEM0XNB":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M78F325F0VEANPZ4MPEM0XNB","ghl-calendars",null,"GoHighLevel calendars, appointments, Services and Rentals — the three booking modules, appointment statuses (custom statuses, statusId\u002Fstate), recurring appointments, booking notifications, staff and availability. Use when the user says 'set up a calendar', 'book an appointment', 'service appointment', 'sell a service with add-on products', 'rental listing', 'deposit \u002F partial payment', 'custom appointment status', 'recurring appointment', 'why is no slot bookable', 'my booking widget shows no times', 'the confirmation email didn't\u002Fdid go out', or asks why an appointment workflow does not fire for a service booking. Classic calendars and appointments are on the PUBLIC rail; Services, Rentals, statuses and the module switch are internal.","uxieee\u002Fuxie-ghl-factory","uxieee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83715980?v=4","01M78F1K57TCCXME78DK6XTK6S","uxie","01M78F1K5WT9N3WHVE4N532ZWM",12,"MIT","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-calendars\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ghl-calendars\ndescription: \"GoHighLevel calendars, appointments, Services and Rentals — the three booking modules, appointment statuses (custom statuses, statusId\u002Fstate), recurring appointments, booking notifications, staff and availability. Use when the user says 'set up a calendar', 'book an appointment', 'service appointment', 'sell a service with add-on products', 'rental listing', 'deposit \u002F partial payment', 'custom appointment status', 'recurring appointment', 'why is no slot bookable', 'my booking widget shows no times', 'the confirmation email didn't\u002Fdid go out', or asks why an appointment workflow does not fire for a service booking. Classic calendars and appointments are on the PUBLIC rail; Services, Rentals, statuses and the module switch are internal.\"\n---\n\n# GHL Calendars\n\nCorpus: `knowledge\u002Fcorpus\u002Fcalendars\u002F` — start at `00-overview\u002Findex.md`; the 2026-10 wave is\n`70-research\u002F2026-10-30-calendars-wave.md`. The write gates in `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fwrite-rails.md`\napply to every write below: preview, confirm, read back on a separate request.\n\n## First: which product is the user talking about?\n\nSince 2026-09 Calendars is three modules, switched per sub-account in `subAccountConfig.modules`\n(default `[\"meetings\"]`):\n\n| Module | Books | Object | Rail |\n|---|---|---|---|\n| `meetings` | classic calendars: personal, round robin, class, collective, event, and the v1 **Service menu** type (`service_booking`, now labelled \"Service calendars (v1)\") | a calendar | **public** (`calendars-v3__*`) |\n| `services` | a **service**: duration, price, staff, a catalog product, retail add-on products, an attached form | a service (`industryType: \"service\"`) | internal |\n| `rentals` | a **listing** by day\u002Ftime with fees, add-ons, deposits, partial payments | a service (`industryType: \"rental\"`) | internal |\n\n🔴 **\"Service calendar\" is ambiguous.** A v1 `service_booking` calendar is a meetings calendar; the Services product\nis a different object on a different route family. Ask, or read the module config, before building either. Never\nbuild a classic Service-menu calendar when the user wants the 2026 Services product, or the reverse.\n\n**Read the module config first** (raw_request, backend host):\n`GET \u002Fcalendars\u002Fconfiguration\u002Flocation\u002F{locationId}` → `{subAccountConfig: {modules, isRentalsEnabled},\nisMigrationCompleted}`. If `services` or `rentals` is missing, those screens and routes do not exist on that account.\nTurning a module on is an **account-level change the operator makes** (agency view → Sub-accounts → Setup Calendars)\n— do not do it yourself. If they ask you to: it is a PUT of the same path; 🔴 **services appears asynchronously** —\nthe PUT echoes it, an immediate re-read lacks it, it lands ~30 s later with `isMigrationCompleted: true`. And the\nmigration has side effects: it copies every v1 service calendar into a Service plus a product (originals untouched),\ncreates a staff record for every user, and turns on staff e-mails for every booking (below).\n\n## Classic calendars and appointments — public rail\n\n`search_actions` → `calendars-v3__create-calendar`, `calendars-v3__update-calendar`, `calendars-v3__get-calendar-events`,\n`calendars-v3__create-appointment`, `calendars-v3__edit-appointment`, the event-calendar schedule ops. Traps:\n\n- 🔴 **The calendar PUT replaces.** A body naming only slot fields reset `openHours` to `{}`; the calendar then still\n  read active and rendered its widget while offering **no slots**. GET the calendar, change the whole document, send it\n  back, then check a field you did NOT send (corpus `40-rules\u002Fcalendar-put-replaces-it-does-not-merge.md`).\n- 🔴 **`startTime`\u002F`endTime` on the events read are epoch MILLISECONDS.** An ISO string answers 200 with no events — a\n  booked day looks free.\n- 🔴 **`toNotify: false` is not silent.** The calendar's notification settings decide; a confirmation went out with it.\n  To stop e-mails, change the calendar's notifications, not the flag.\n- **Read status by `appoinmentStatus ?? appointmentStatus`** (GHL's typo; the contact route carries only the typo), and\n  never by `isCancelled` — it read `false` on a cancelled appointment.\n- `autoConfirm` decides the status an appointment is BORN with; a `status == new` trigger never sees an auto-confirmed\n  booking.\n- **Stored settings the public calendar update accepts** (verified on a test calendar, each read back on a separate GET and\n  restored): the booking form (form id, submit type, redirect URL, thank-you message), `autoConfirm`, guest type and the\n  consent label. A changed value shows on the public widget payload (thank-you message, guest type and consent label do).\n- 🔴 **A partial calendar PUT is refused on a collective calendar** (the server answers that the primary team member flag is required). Send the team\n  members, form id, submit type and thank-you message from a fresh GET together with the change, then check that no\n  other field moved.\n- **Keys outside the public update schema** (enable guests, guest collection mode, enable consent check, show seats per\n  slot, reserve-service, price id) are writable only with a raw PUT to the same calendar route; the public tool does not\n  accept them. The seats-per-slot flag shows on the public payload.\n- **Raw keys on the same calendar PUT** (`PUT \u002Fcalendars\u002F{calendarId}`, the whole document: send the team members and form id too, then read back on a separate GET and restore): look busy is the nested `lookBusyConfig` `{enabled, lookBusyPercentage}` (the flat `lookBusyEnabled` and `lookBusyPercentage` keys are refused 422 \"should not exist\"); the redirect after booking is `formSubmitType` `RedirectURL` together with `formSubmitRedirectURL` (capital R in URL), since the lower-case form is refused and the read-back key is `formSubmitRedirectUrl`; guests are `enableGuests` with `guestType` (set and restored on a TEST collective calendar). Evidence for each is cited in the knowledge calendars sniffs.\n\n**Calendar fields a raw_request PUT \u002Fcalendars\u002F{calendarId} sets** (the route is in the plugin catalogue on both hosts; send the required keys with the change, read back on a separate GET, restore):\n\n| Field (stored key) | What it controls | Live proof (knowledge sniff) |\n|---|---|---|\n| `enableOfficeHours` | the availability office-hours switch | live-f4s-b1-editor-set.json |\n| `showSeatsPerSlot` | the seats-per-slot display flag on event capacity | live-cal2-stored-seats.json |\n| `stripe.amount` | accept payments on a meetings calendar (a positive amount) | live-cal.payments.b.json |\n| `stripe.deposit` and `stripe.depositType` | a meeting deposit as an amount or a percentage | live-cal.payments.b.json |\n| `enableChargeGuests` with `enableGuests` and a `stripe` amount | charge per attendee | live-cal.payments.b.json |\n| `stripe.deposit` and `stripe.depositType` (percentage) | booking deposit | live-log.jsonl |\n| `preBuffer` | the pre-buffer time before a booking (Booking rules) | live-f4s-b1-editor-set.json |\n| `slotBuffer` (with `slotBufferUnit`) | the post-buffer time after a booking (Booking rules) | live-log.jsonl |\n| `allowBookingAfter` (with `allowBookingAfterUnit`) | how far ahead a booking may be made, in hours (allow booking after). Clearing it needs both keys sent as explicit `null`: a PUT that omits them returns 200 and leaves the value (a restore without them did not take) | live-log.jsonl |\n| `teamMembers[].locationConfigurations[].kind` (the meeting location, sent in the team members of the calendar PUT) | the meeting location: `custom`, `inbound_call` (phone) or `physical` (address). `phone` and `address` are refused with 422, so send the stored kinds | live-log.jsonl |\n| `allowCancellation` | whether a booker may cancel from the public page | live-cal2-bulk-d-scrubbed.json |\n| `allowReschedule` | whether a booker may reschedule from the public page | live-cal2-bulk-d-scrubbed.json |\n| `stickyContact` | sticky contact on the booking | live-log.jsonl |\n- Creating a calendar in the UI also rewrites the assignee's default availability schedule with `calendarIds:\n  [\u003Cnew id>]` only. Whether that unbinds an earlier calendar is untested — read the schedule after.\n\n## Appointment statuses (2026-10)\n\nEvery appointment now carries **`statusId`** (an id from its module's status set) and **`state`** (`pending`,\n`active`, `completed`, `noshow`, `cancelled`, `invalid`), beside the old string. With the Lab\n`calendars.customStatuses` (🔴 **irreversible** — never flip it without the operator's explicit yes) the operator can add\nstatuses under each state (Settings → Calendars → Preferences → Appointment status; `GET\u002FPOST\n\u002Fcalendars\u002Fstatuses\u002F{module}[\u002F{state}]` on the services host). 🔴 **Status ids are per module** (`meeting`, `service`): a\n\"Confirmed\" id from meetings does not match a service booking. What the old `appointmentStatus` string reads after an\nappointment is set to a *custom* status is **unproven** — do not promise a workflow filter on the old strings will\ncatch custom statuses.\n\n**Rename a custom status** (proven live on the production services host: one rename and one restore, each read back on a separate GET): `PATCH \u002Fcalendars\u002Fstatuses\u002Frename\u002F{statusId}` with body `{locationId, status: \"\u003Cnew label>\"}`. Only the rename route is covered here. Reorder, archive and restore are not proven, and custom statuses exist only with the Lab flag on.\n\n## Recurring appointments\n\nThe in-app Custom → Recurring create adds `isCustomRecurring: true` and an RFC 5545 `rrule`; each occurrence's id is\n`\u003CmasterId>_\u003CepochMs>_\u003CdurationSec>`. A series sends ONE confirmation with the recurrence text in the date. Changing\none occurrence takes `recurringEventUpdateType` (`this_event` proven). 🔴 **Cancelling one occurrence detaches it into\na NEW appointment** (new id, its own status) and the contact's activity logs \"New appointment created\" — expect\nappointment-created automations to see it.\n\n## Services (internal, services host unless noted)\n\n- **Create a service**: `POST \u002Fcalendars\u002Fservices` — a catalog product is created with it; a new service has no\n  `calendarId`. The service PUT is **whole-document** (like the calendar PUT).\n- **Book one**: the proven path is the app's own **multipart** `POST \u002Fcalendars\u002Fbookings\u002Fcreate` (backend host) with\n  parts `bookingData`, `formId`, `formData`. The public rail also lists `calendars-v3__create-service-booking` — never\n  executed here; prefer it only after proving it on a test account.\n  - custom price per appointment: `selectedSlotInfo.services[].custom.price` + `orderDetails.products[].overridePrice`.\n    🔴 A **negative** price saves as **$0** — validate before sending.\n  - retail products: `retailProducts[]` + `orderDetails.products[]` with `skipPriceLookup`; stock is decremented, the\n    catalog price is not changed.\n  - 🔴 `paymentMeta.paymentStatus` reads `\"completed\"` even with `processPayment: false` — do not report it as paid.\n- 🔴 **A service appointment's `calendarId` is the SERVICE id** (`serviceId`) and its `groupId` the service category.\n  A workflow trigger filtered to a calendar, or any pre-flight keyed on a calendar id, **misses every service\n  booking**. Filter on the service id, or not by calendar at all.\n- **Staff**: `\u002Fcalendars\u002Fservice-users`. Assigning a role badge (`\u002Fcalendars\u002Fcalendar-badges`, label ≤ 30 chars) from\n  the staff editor also writes a default availability onto the staff record — read it back.\n- 🔴 **Notifications**: enabling Services stores defaults that e-mail the **contact AND the assigned staff member** on\n  booked and confirmation. Ask before leaving staff e-mails on. Toggle with `PUT \u002Fcalendars\u002Fevent-notifications\u002Fbulk-update`\n  `{_id, isActive, altId: \u003ClocationId>, altType: \"location\"}` (the UI's body, on the services host); a bare `{_id, isActive}` sent to the backend host answered **500** — send the UI's body.\n\n## Rentals (internal, services host)\n\nA listing is `POST \u002Fcalendars\u002Fservices` with `industryType: \"rental\"`, `bookingUnit`, `pricingRule`. Fees are\n`\u002Fcalendars\u002Fservice-entities` (`entityType: \"additionalFee\"`, flat or percentage); add-ons are\n`\u002Fcalendars\u002Fservice-addons`. 🔴 The same idea is spelled `perBookingUnit` on fees and `per_booking` on add-ons. Attaching a\nfee is a whole-document listing PUT (`serviceEntities[]`). Partial payments, deposits and the self-serve cancellation\nwindow are Global settings; a rental booking needs a connected payment provider and has **not** been executed here.\n\n## Notifications (meetings)\n\nTurning a calendar's e-mail channel on **auto-saves with every receiver active** (contact, assigned user, extra\ne-mails) until each is unticked; send the receiver set in one write if scripting it. The defaults are stored as literal\ntext in the business's language at the moment of enabling and are not re-translated later.\n\n## \"Why is this slot not bookable?\"\n\nThe calendar setup assistant's Troubleshoot mode reads the troubleshoot-free-slots grid: per slot `status` and\n`conflicts` (`past`, `duration` with `blockingEventIds`, `blocked_slot`). Only in-hours slots exist in it, so \"why not\n7 AM\" outside working hours gets no clean answer — check the availability schedule and `openHours` first. The\nassistant's troubleshoot state sticks across turns: start a new chat per question.\n\n## The booking-page view (UI only)\n\nThe booking-pages list and the View booking page tab are a rendered view. The calendar object and the public widget payload carry no page-view key, so there is no API setting to read back or set. Open it in the app at `app.gohighlevel.com\u002Fv2\u002Flocation\u002F{locationId}\u002Fsettings\u002Fcalendars` (the settings tab, then the booking pages list). Do not send a write for the view itself.\n\n## Raw-route rows for calendar fields (proven by set and restore)\n\nEach row names a catalogued route, the body shape the proof sent, and what to read back. Every set is followed by a restore to the prior value and a separate read-back. Ids are left out.\n\n- **Editor Basic details, description:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document (teamMembers, formId, formSubmitType, formSubmitThanksMessage) and the one changed field. A partial body is refused on a collective calendar. Read back on a separate GET.\n- **Editor Staff and location, custom meeting location label:** `PUT \u002Fcalendars\u002F{calendarId}` with teamMembers, the custom label changed on one team member and the rest of the member kept. Read back on a separate GET; the label goes back to the original.\n- **Services create:** `POST \u002Fcalendars\u002Fservices` returns 201 for one service. Then `PUT \u002Fcalendars\u002Fservices\u002F{serviceId}` with the full document and one changed field, read back, and the original document restored.\n- **Payments, recurring meetings:** `PUT \u002Fcalendars\u002F{calendarId}` with enableRecurring and stripe.recurringAppointmentsPaymentType, set and restored to false and {}. No checkout, no provider call.\n- **Payments, coupon on the payment page:** `PUT \u002Fcalendars\u002F{calendarId}` with stripe.isCouponEnabled, set and restored.\n- **Service setup, reserve service:** `PUT \u002Fcalendars\u002F{calendarId}` with reserveService, set and restored. The price id and the wizard step are not sent.\n- **Class seats per class:** `PUT \u002Fcalendars\u002F{calendarId}` with appointmentPerSlot. The key is proven on a class calendar; the UI label \"Seats per class\" is not yet confirmed to save to it.\n- **Round robin event type and distribution:** `PUT \u002Fcalendars\u002F{calendarId}` with eventType, set between `RoundRobin_OptimizeForAvailability` and `RoundRobin_OptimizeForEqualDistribution` and restored to the prior value; read back on a separate GET. The calendar type is set at create and read back.\n- **Round robin staff priority:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole teamMembers array, one member's priority changed (1 to 0.5) and the rest of the array unchanged. Read back on a separate GET; the array is restored to the exact prior value.\n- **Round robin max bookings per slot per user:** `PUT \u002Fcalendars\u002F{calendarId}` with appoinmentPerSlot (2) on the round-robin calendar. Read back on a separate GET; restored to absent, which reads back absent.\n- **Booking date range:** `PUT \u002Fcalendars\u002F{calendarId}` with allowBookingFor (60) and allowBookingForUnit (days), set and read back on a separate GET; restored with both keys null, which GHL drops, so the keys read back absent. Effect check: free-slots beyond day 60 go to zero after the set.\n- **Calendar groups:** `POST \u002Fcalendars\u002Fgroups` creates a group (201). `PUT \u002Fcalendars\u002Fgroups\u002F{groupId}` with name and slug only (a body that carries locationId is refused 422) renames it, read back on a separate GET, then restored. `PUT \u002Fcalendars\u002Fgroups\u002F{groupId}\u002Fstatus` with isActive set false, read back, then restored to true.\n- **Activity log (audit feed):** `GET \u002Faudit\u002Fsearch\u002Fv2` (services host; query page, pageSize, startAt, endAt, locationId). After a calendar PUT, the newest entries show a calendar UPDATED entry naming the changed field. The feed does not record every PUT, so the restore may not appear in it; read the calendar object to confirm the restore.\n- **User default meeting location:** `PUT \u002Fusers\u002F{userId}` with locationWiseMeetingLocation for the location. Restored to null; the prior absence of the location key is not reproduced.\n- **Account language and week start:** `PUT \u002Flocations\u002F{locationId}` with appStartDayOfWeek and the language, set and restored.\n- **Booking page, client portal booking:** `PUT \u002Fcalendars\u002F{calendarId}` with the stored key enableClientPortalBooking (false, then true, then restored), read back on a separate GET. The other keys on the booking-page screen are page copy and are not stored settings.\n- **Calendar view, view mode and week:** UI only. The view is kept in the browser (a local key, set and read back after a reload), and no server route stores it. There is no raw route to name, so the calendar setup and this view are a UI step.\n- **Module gate (read only):** `GET \u002Fcalendars\u002Fconfiguration\u002Flocation\u002F{locationId}` returns subAccountConfig modules. No sub-account write route is captured, so the modules are read, not set.\n- **Recurring meeting settings (the recurring object):** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document, enableRecurring true and `recurring` set to the object (freq, interval, count, weekDays, bookingOption, bookingOverlapDefaultStatus). Each sub-field is set and read back on a separate GET. The restore sets `recurring` back to its prior value; a recurring object that was absent before reads back as an empty object after the restore. Proven live 2026-11-11 on a TEST class calendar.\n- **Collective owner:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole teamMembers array. The owner flag moves to a second team member, read back on a separate GET, then the exact prior team is restored. The second member must already exist in the location; the availability change on that member is left as residue. Proven live 2026-11-11 on a TEST collective calendar.\n- **Collective video, custom link:** `PUT \u002Fcalendars\u002F{calendarId}` with teamMembers, the owner member's locationConfigurations[0] set to a custom link (kind custom), read back on a separate GET, then the prior team restored. Proven live 2026-11-11 on the same TEST collective calendar. The integration kinds (Zoom, Google Meet, Microsoft Teams, LC meet) are not tested here: they need connected outside accounts.\n- **Event notifications (WhatsApp, SMS and email rows):** `PUT \u002Fcalendars\u002Fevent-notifications\u002Fbulk-update` with a one-element array holding the row as read from `GET \u002Fcalendars\u002Fevent-notifications\u002Flist`, with one field changed (the body text, the additional phone, the subject or the additional email IDs). Read back on a separate list GET, then the prior row is sent the same way. Proven live 2026-11-10 on a TEST calendar. Do not create a row to test: the create path can revive a deleted row. A recipient-name list on a contact-type row is not stored by this write; the write is accepted and dropped.\n- **Slot duration and interval:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document and slotDuration and slotInterval changed in one PUT (30 to 45 and 30 to 15), read back on a separate GET, then both restored. Proven live 2026-11-11 on a TEST class calendar.\n- **Event share link (slug):** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document and slug set to a probe value, read back on a separate GET, then the original slug restored and read back equal. Proven live 2026-11-09 on a TEST calendar.\n- **Rooms and equipment:** `POST \u002Fcalendars\u002Fresources\u002F{type}`, with type `rooms` (name, capacity, locationId) or `equipments` (name, quantity, locationId). A create returns 201 and the new item reads back on a separate GET. Proven live 2026-11-09 on the sandbox with a TEST-CONF name. The TEST item is left in place; no delete route is in the catalogue for it.\n\n### UI-only units (no raw route to name)\n\nThese units are a rendered view, a browser-side setting, or a page the calendar object does not store. Use the app for them; do not send a write for them.\n\n- **Calendar list: service calendars (v1), calendar troubleshoot, calendar export, manage view, timezone release:** no catalogued write route was found for a stored value. The app is the only path named here.\n- **Appointment list view and settings modal:** the saved view and timezone keys go through a user-settings features route that is not in the catalogue. Read it in the app; no raw route is named.\n- **Booking page view:** blocked on the booking-page view; see the booking-page view section above.\n\n## Side effects to tell the operator about\n\nA booking on a calendar whose user has Google\u002FOutlook connected is written to that external calendar. A calendar create\nrewrites the assignee's default schedule. Enabling Services creates staff records, products and staff e-mails.\n","# GHL Calendars\n\nCorpus: `knowledge\u002Fcorpus\u002Fcalendars\u002F` — start at `00-overview\u002Findex.md`; the 2026-10 wave is\n`70-research\u002F2026-10-30-calendars-wave.md`. The write gates in `${CLAUDE_PLUGIN_ROOT}\u002Fdocs\u002Fwrite-rails.md`\napply to every write below: preview, confirm, read back on a separate request.\n\n## First: which product is the user talking about?\n\nSince 2026-09 Calendars is three modules, switched per sub-account in `subAccountConfig.modules`\n(default `[\"meetings\"]`):\n\n| Module | Books | Object | Rail |\n|---|---|---|---|\n| `meetings` | classic calendars: personal, round robin, class, collective, event, and the v1 **Service menu** type (`service_booking`, now labelled \"Service calendars (v1)\") | a calendar | **public** (`calendars-v3__*`) |\n| `services` | a **service**: duration, price, staff, a catalog product, retail add-on products, an attached form | a service (`industryType: \"service\"`) | internal |\n| `rentals` | a **listing** by day\u002Ftime with fees, add-ons, deposits, partial payments | a service (`industryType: \"rental\"`) | internal |\n\n🔴 **\"Service calendar\" is ambiguous.** A v1 `service_booking` calendar is a meetings calendar; the Services product\nis a different object on a different route family. Ask, or read the module config, before building either. Never\nbuild a classic Service-menu calendar when the user wants the 2026 Services product, or the reverse.\n\n**Read the module config first** (raw_request, backend host):\n`GET \u002Fcalendars\u002Fconfiguration\u002Flocation\u002F{locationId}` → `{subAccountConfig: {modules, isRentalsEnabled},\nisMigrationCompleted}`. If `services` or `rentals` is missing, those screens and routes do not exist on that account.\nTurning a module on is an **account-level change the operator makes** (agency view → Sub-accounts → Setup Calendars)\n— do not do it yourself. If they ask you to: it is a PUT of the same path; 🔴 **services appears asynchronously** —\nthe PUT echoes it, an immediate re-read lacks it, it lands ~30 s later with `isMigrationCompleted: true`. And the\nmigration has side effects: it copies every v1 service calendar into a Service plus a product (originals untouched),\ncreates a staff record for every user, and turns on staff e-mails for every booking (below).\n\n## Classic calendars and appointments — public rail\n\n`search_actions` → `calendars-v3__create-calendar`, `calendars-v3__update-calendar`, `calendars-v3__get-calendar-events`,\n`calendars-v3__create-appointment`, `calendars-v3__edit-appointment`, the event-calendar schedule ops. Traps:\n\n- 🔴 **The calendar PUT replaces.** A body naming only slot fields reset `openHours` to `{}`; the calendar then still\n  read active and rendered its widget while offering **no slots**. GET the calendar, change the whole document, send it\n  back, then check a field you did NOT send (corpus `40-rules\u002Fcalendar-put-replaces-it-does-not-merge.md`).\n- 🔴 **`startTime`\u002F`endTime` on the events read are epoch MILLISECONDS.** An ISO string answers 200 with no events — a\n  booked day looks free.\n- 🔴 **`toNotify: false` is not silent.** The calendar's notification settings decide; a confirmation went out with it.\n  To stop e-mails, change the calendar's notifications, not the flag.\n- **Read status by `appoinmentStatus ?? appointmentStatus`** (GHL's typo; the contact route carries only the typo), and\n  never by `isCancelled` — it read `false` on a cancelled appointment.\n- `autoConfirm` decides the status an appointment is BORN with; a `status == new` trigger never sees an auto-confirmed\n  booking.\n- **Stored settings the public calendar update accepts** (verified on a test calendar, each read back on a separate GET and\n  restored): the booking form (form id, submit type, redirect URL, thank-you message), `autoConfirm`, guest type and the\n  consent label. A changed value shows on the public widget payload (thank-you message, guest type and consent label do).\n- 🔴 **A partial calendar PUT is refused on a collective calendar** (the server answers that the primary team member flag is required). Send the team\n  members, form id, submit type and thank-you message from a fresh GET together with the change, then check that no\n  other field moved.\n- **Keys outside the public update schema** (enable guests, guest collection mode, enable consent check, show seats per\n  slot, reserve-service, price id) are writable only with a raw PUT to the same calendar route; the public tool does not\n  accept them. The seats-per-slot flag shows on the public payload.\n- **Raw keys on the same calendar PUT** (`PUT \u002Fcalendars\u002F{calendarId}`, the whole document: send the team members and form id too, then read back on a separate GET and restore): look busy is the nested `lookBusyConfig` `{enabled, lookBusyPercentage}` (the flat `lookBusyEnabled` and `lookBusyPercentage` keys are refused 422 \"should not exist\"); the redirect after booking is `formSubmitType` `RedirectURL` together with `formSubmitRedirectURL` (capital R in URL), since the lower-case form is refused and the read-back key is `formSubmitRedirectUrl`; guests are `enableGuests` with `guestType` (set and restored on a TEST collective calendar). Evidence for each is cited in the knowledge calendars sniffs.\n\n**Calendar fields a raw_request PUT \u002Fcalendars\u002F{calendarId} sets** (the route is in the plugin catalogue on both hosts; send the required keys with the change, read back on a separate GET, restore):\n\n| Field (stored key) | What it controls | Live proof (knowledge sniff) |\n|---|---|---|\n| `enableOfficeHours` | the availability office-hours switch | live-f4s-b1-editor-set.json |\n| `showSeatsPerSlot` | the seats-per-slot display flag on event capacity | live-cal2-stored-seats.json |\n| `stripe.amount` | accept payments on a meetings calendar (a positive amount) | live-cal.payments.b.json |\n| `stripe.deposit` and `stripe.depositType` | a meeting deposit as an amount or a percentage | live-cal.payments.b.json |\n| `enableChargeGuests` with `enableGuests` and a `stripe` amount | charge per attendee | live-cal.payments.b.json |\n| `stripe.deposit` and `stripe.depositType` (percentage) | booking deposit | live-log.jsonl |\n| `preBuffer` | the pre-buffer time before a booking (Booking rules) | live-f4s-b1-editor-set.json |\n| `slotBuffer` (with `slotBufferUnit`) | the post-buffer time after a booking (Booking rules) | live-log.jsonl |\n| `allowBookingAfter` (with `allowBookingAfterUnit`) | how far ahead a booking may be made, in hours (allow booking after). Clearing it needs both keys sent as explicit `null`: a PUT that omits them returns 200 and leaves the value (a restore without them did not take) | live-log.jsonl |\n| `teamMembers[].locationConfigurations[].kind` (the meeting location, sent in the team members of the calendar PUT) | the meeting location: `custom`, `inbound_call` (phone) or `physical` (address). `phone` and `address` are refused with 422, so send the stored kinds | live-log.jsonl |\n| `allowCancellation` | whether a booker may cancel from the public page | live-cal2-bulk-d-scrubbed.json |\n| `allowReschedule` | whether a booker may reschedule from the public page | live-cal2-bulk-d-scrubbed.json |\n| `stickyContact` | sticky contact on the booking | live-log.jsonl |\n- Creating a calendar in the UI also rewrites the assignee's default availability schedule with `calendarIds:\n  [\u003Cnew id>]` only. Whether that unbinds an earlier calendar is untested — read the schedule after.\n\n## Appointment statuses (2026-10)\n\nEvery appointment now carries **`statusId`** (an id from its module's status set) and **`state`** (`pending`,\n`active`, `completed`, `noshow`, `cancelled`, `invalid`), beside the old string. With the Lab\n`calendars.customStatuses` (🔴 **irreversible** — never flip it without the operator's explicit yes) the operator can add\nstatuses under each state (Settings → Calendars → Preferences → Appointment status; `GET\u002FPOST\n\u002Fcalendars\u002Fstatuses\u002F{module}[\u002F{state}]` on the services host). 🔴 **Status ids are per module** (`meeting`, `service`): a\n\"Confirmed\" id from meetings does not match a service booking. What the old `appointmentStatus` string reads after an\nappointment is set to a *custom* status is **unproven** — do not promise a workflow filter on the old strings will\ncatch custom statuses.\n\n**Rename a custom status** (proven live on the production services host: one rename and one restore, each read back on a separate GET): `PATCH \u002Fcalendars\u002Fstatuses\u002Frename\u002F{statusId}` with body `{locationId, status: \"\u003Cnew label>\"}`. Only the rename route is covered here. Reorder, archive and restore are not proven, and custom statuses exist only with the Lab flag on.\n\n## Recurring appointments\n\nThe in-app Custom → Recurring create adds `isCustomRecurring: true` and an RFC 5545 `rrule`; each occurrence's id is\n`\u003CmasterId>_\u003CepochMs>_\u003CdurationSec>`. A series sends ONE confirmation with the recurrence text in the date. Changing\none occurrence takes `recurringEventUpdateType` (`this_event` proven). 🔴 **Cancelling one occurrence detaches it into\na NEW appointment** (new id, its own status) and the contact's activity logs \"New appointment created\" — expect\nappointment-created automations to see it.\n\n## Services (internal, services host unless noted)\n\n- **Create a service**: `POST \u002Fcalendars\u002Fservices` — a catalog product is created with it; a new service has no\n  `calendarId`. The service PUT is **whole-document** (like the calendar PUT).\n- **Book one**: the proven path is the app's own **multipart** `POST \u002Fcalendars\u002Fbookings\u002Fcreate` (backend host) with\n  parts `bookingData`, `formId`, `formData`. The public rail also lists `calendars-v3__create-service-booking` — never\n  executed here; prefer it only after proving it on a test account.\n  - custom price per appointment: `selectedSlotInfo.services[].custom.price` + `orderDetails.products[].overridePrice`.\n    🔴 A **negative** price saves as **$0** — validate before sending.\n  - retail products: `retailProducts[]` + `orderDetails.products[]` with `skipPriceLookup`; stock is decremented, the\n    catalog price is not changed.\n  - 🔴 `paymentMeta.paymentStatus` reads `\"completed\"` even with `processPayment: false` — do not report it as paid.\n- 🔴 **A service appointment's `calendarId` is the SERVICE id** (`serviceId`) and its `groupId` the service category.\n  A workflow trigger filtered to a calendar, or any pre-flight keyed on a calendar id, **misses every service\n  booking**. Filter on the service id, or not by calendar at all.\n- **Staff**: `\u002Fcalendars\u002Fservice-users`. Assigning a role badge (`\u002Fcalendars\u002Fcalendar-badges`, label ≤ 30 chars) from\n  the staff editor also writes a default availability onto the staff record — read it back.\n- 🔴 **Notifications**: enabling Services stores defaults that e-mail the **contact AND the assigned staff member** on\n  booked and confirmation. Ask before leaving staff e-mails on. Toggle with `PUT \u002Fcalendars\u002Fevent-notifications\u002Fbulk-update`\n  `{_id, isActive, altId: \u003ClocationId>, altType: \"location\"}` (the UI's body, on the services host); a bare `{_id, isActive}` sent to the backend host answered **500** — send the UI's body.\n\n## Rentals (internal, services host)\n\nA listing is `POST \u002Fcalendars\u002Fservices` with `industryType: \"rental\"`, `bookingUnit`, `pricingRule`. Fees are\n`\u002Fcalendars\u002Fservice-entities` (`entityType: \"additionalFee\"`, flat or percentage); add-ons are\n`\u002Fcalendars\u002Fservice-addons`. 🔴 The same idea is spelled `perBookingUnit` on fees and `per_booking` on add-ons. Attaching a\nfee is a whole-document listing PUT (`serviceEntities[]`). Partial payments, deposits and the self-serve cancellation\nwindow are Global settings; a rental booking needs a connected payment provider and has **not** been executed here.\n\n## Notifications (meetings)\n\nTurning a calendar's e-mail channel on **auto-saves with every receiver active** (contact, assigned user, extra\ne-mails) until each is unticked; send the receiver set in one write if scripting it. The defaults are stored as literal\ntext in the business's language at the moment of enabling and are not re-translated later.\n\n## \"Why is this slot not bookable?\"\n\nThe calendar setup assistant's Troubleshoot mode reads the troubleshoot-free-slots grid: per slot `status` and\n`conflicts` (`past`, `duration` with `blockingEventIds`, `blocked_slot`). Only in-hours slots exist in it, so \"why not\n7 AM\" outside working hours gets no clean answer — check the availability schedule and `openHours` first. The\nassistant's troubleshoot state sticks across turns: start a new chat per question.\n\n## The booking-page view (UI only)\n\nThe booking-pages list and the View booking page tab are a rendered view. The calendar object and the public widget payload carry no page-view key, so there is no API setting to read back or set. Open it in the app at `app.gohighlevel.com\u002Fv2\u002Flocation\u002F{locationId}\u002Fsettings\u002Fcalendars` (the settings tab, then the booking pages list). Do not send a write for the view itself.\n\n## Raw-route rows for calendar fields (proven by set and restore)\n\nEach row names a catalogued route, the body shape the proof sent, and what to read back. Every set is followed by a restore to the prior value and a separate read-back. Ids are left out.\n\n- **Editor Basic details, description:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document (teamMembers, formId, formSubmitType, formSubmitThanksMessage) and the one changed field. A partial body is refused on a collective calendar. Read back on a separate GET.\n- **Editor Staff and location, custom meeting location label:** `PUT \u002Fcalendars\u002F{calendarId}` with teamMembers, the custom label changed on one team member and the rest of the member kept. Read back on a separate GET; the label goes back to the original.\n- **Services create:** `POST \u002Fcalendars\u002Fservices` returns 201 for one service. Then `PUT \u002Fcalendars\u002Fservices\u002F{serviceId}` with the full document and one changed field, read back, and the original document restored.\n- **Payments, recurring meetings:** `PUT \u002Fcalendars\u002F{calendarId}` with enableRecurring and stripe.recurringAppointmentsPaymentType, set and restored to false and {}. No checkout, no provider call.\n- **Payments, coupon on the payment page:** `PUT \u002Fcalendars\u002F{calendarId}` with stripe.isCouponEnabled, set and restored.\n- **Service setup, reserve service:** `PUT \u002Fcalendars\u002F{calendarId}` with reserveService, set and restored. The price id and the wizard step are not sent.\n- **Class seats per class:** `PUT \u002Fcalendars\u002F{calendarId}` with appointmentPerSlot. The key is proven on a class calendar; the UI label \"Seats per class\" is not yet confirmed to save to it.\n- **Round robin event type and distribution:** `PUT \u002Fcalendars\u002F{calendarId}` with eventType, set between `RoundRobin_OptimizeForAvailability` and `RoundRobin_OptimizeForEqualDistribution` and restored to the prior value; read back on a separate GET. The calendar type is set at create and read back.\n- **Round robin staff priority:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole teamMembers array, one member's priority changed (1 to 0.5) and the rest of the array unchanged. Read back on a separate GET; the array is restored to the exact prior value.\n- **Round robin max bookings per slot per user:** `PUT \u002Fcalendars\u002F{calendarId}` with appoinmentPerSlot (2) on the round-robin calendar. Read back on a separate GET; restored to absent, which reads back absent.\n- **Booking date range:** `PUT \u002Fcalendars\u002F{calendarId}` with allowBookingFor (60) and allowBookingForUnit (days), set and read back on a separate GET; restored with both keys null, which GHL drops, so the keys read back absent. Effect check: free-slots beyond day 60 go to zero after the set.\n- **Calendar groups:** `POST \u002Fcalendars\u002Fgroups` creates a group (201). `PUT \u002Fcalendars\u002Fgroups\u002F{groupId}` with name and slug only (a body that carries locationId is refused 422) renames it, read back on a separate GET, then restored. `PUT \u002Fcalendars\u002Fgroups\u002F{groupId}\u002Fstatus` with isActive set false, read back, then restored to true.\n- **Activity log (audit feed):** `GET \u002Faudit\u002Fsearch\u002Fv2` (services host; query page, pageSize, startAt, endAt, locationId). After a calendar PUT, the newest entries show a calendar UPDATED entry naming the changed field. The feed does not record every PUT, so the restore may not appear in it; read the calendar object to confirm the restore.\n- **User default meeting location:** `PUT \u002Fusers\u002F{userId}` with locationWiseMeetingLocation for the location. Restored to null; the prior absence of the location key is not reproduced.\n- **Account language and week start:** `PUT \u002Flocations\u002F{locationId}` with appStartDayOfWeek and the language, set and restored.\n- **Booking page, client portal booking:** `PUT \u002Fcalendars\u002F{calendarId}` with the stored key enableClientPortalBooking (false, then true, then restored), read back on a separate GET. The other keys on the booking-page screen are page copy and are not stored settings.\n- **Calendar view, view mode and week:** UI only. The view is kept in the browser (a local key, set and read back after a reload), and no server route stores it. There is no raw route to name, so the calendar setup and this view are a UI step.\n- **Module gate (read only):** `GET \u002Fcalendars\u002Fconfiguration\u002Flocation\u002F{locationId}` returns subAccountConfig modules. No sub-account write route is captured, so the modules are read, not set.\n- **Recurring meeting settings (the recurring object):** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document, enableRecurring true and `recurring` set to the object (freq, interval, count, weekDays, bookingOption, bookingOverlapDefaultStatus). Each sub-field is set and read back on a separate GET. The restore sets `recurring` back to its prior value; a recurring object that was absent before reads back as an empty object after the restore. Proven live 2026-11-11 on a TEST class calendar.\n- **Collective owner:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole teamMembers array. The owner flag moves to a second team member, read back on a separate GET, then the exact prior team is restored. The second member must already exist in the location; the availability change on that member is left as residue. Proven live 2026-11-11 on a TEST collective calendar.\n- **Collective video, custom link:** `PUT \u002Fcalendars\u002F{calendarId}` with teamMembers, the owner member's locationConfigurations[0] set to a custom link (kind custom), read back on a separate GET, then the prior team restored. Proven live 2026-11-11 on the same TEST collective calendar. The integration kinds (Zoom, Google Meet, Microsoft Teams, LC meet) are not tested here: they need connected outside accounts.\n- **Event notifications (WhatsApp, SMS and email rows):** `PUT \u002Fcalendars\u002Fevent-notifications\u002Fbulk-update` with a one-element array holding the row as read from `GET \u002Fcalendars\u002Fevent-notifications\u002Flist`, with one field changed (the body text, the additional phone, the subject or the additional email IDs). Read back on a separate list GET, then the prior row is sent the same way. Proven live 2026-11-10 on a TEST calendar. Do not create a row to test: the create path can revive a deleted row. A recipient-name list on a contact-type row is not stored by this write; the write is accepted and dropped.\n- **Slot duration and interval:** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document and slotDuration and slotInterval changed in one PUT (30 to 45 and 30 to 15), read back on a separate GET, then both restored. Proven live 2026-11-11 on a TEST class calendar.\n- **Event share link (slug):** `PUT \u002Fcalendars\u002F{calendarId}` with the whole document and slug set to a probe value, read back on a separate GET, then the original slug restored and read back equal. Proven live 2026-11-09 on a TEST calendar.\n- **Rooms and equipment:** `POST \u002Fcalendars\u002Fresources\u002F{type}`, with type `rooms` (name, capacity, locationId) or `equipments` (name, quantity, locationId). A create returns 201 and the new item reads back on a separate GET. Proven live 2026-11-09 on the sandbox with a TEST-CONF name. The TEST item is left in place; no delete route is in the catalogue for it.\n\n### UI-only units (no raw route to name)\n\nThese units are a rendered view, a browser-side setting, or a page the calendar object does not store. Use the app for them; do not send a write for them.\n\n- **Calendar list: service calendars (v1), calendar troubleshoot, calendar export, manage view, timezone release:** no catalogued write route was found for a stored value. The app is the only path named here.\n- **Appointment list view and settings modal:** the saved view and timezone keys go through a user-settings features route that is not in the catalogue. Read it in the app; no raw route is named.\n- **Booking page view:** blocked on the booking-page view; see the booking-page view section above.\n\n## Side effects to tell the operator about\n\nA booking on a calendar whose user has Google\u002FOutlook connected is written to that external calendar. A calendar create\nrewrites the assignee's default schedule. Enabling Services creates staff records, products and staff e-mails.\n",{"name":5,"description":7},"main","35d05921ecd17673183702dca9c1bb7d2c961f71","plugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-calendars",5,"https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory","https:\u002F\u002Fgithub.com\u002Fuxieee","2026-11-13 05:11:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add uxieee\u002Fuxie-ghl-factory --skill ghl-calendars",{"tool":37,"command":38},"bunx","bunx skills add uxieee\u002Fuxie-ghl-factory --skill ghl-calendars",{"tool":40,"command":41},"pnpm","pnpm dlx skills add uxieee\u002Fuxie-ghl-factory --skill ghl-calendars","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-calendars\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M78F5XMBPT6K5KN5H7JWWYRH","ghl-workflow-specialist","Senior GoHighLevel workflow architect — designs automations (nurture, speed-to-lead, no-show recovery, internal ops, data hygiene, routing) grounded in the full trigger\u002Faction catalog and known anti-patterns, and reviews or fixes live workflows. Use when the user asks what automation to set up for X, wants a workflow designed, or asks why a live workflow is not getting through, is failing, or whether an A\u002FB test is done. Recons + reads the client brief before proposing anything. Once approved, the build itself goes to create-ghl-workflow.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-workflow-specialist\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M78F5PXJXRMGCK95MAPVBHAJ","ghl-workflow-fast-forward","Fast-forward contacts parked at a GoHighLevel \u002F HighLevel workflow WAIT step to the next step — the builder's \"Action statistics → move to next step\" control, driven via the internal API. Use to accelerate end-to-end workflow testing (drive a multi-day wait ladder to completion in minutes instead of waiting real time), to unstick contacts stranded at a wait, or when the user says \"fast-forward this wait\", \"skip the wait\", \"move parked\u002Fstuck contacts to the next step\", \"requeue stuck contacts\", \"test this long delay without waiting days\", or gives an app.gohighlevel.com workflow URL and asks to push contacts past a wait. This MUTATES live enrollments (it fires whatever steps come next, i.e. real SMS\u002Femail to real people) — it is a WRITE skill and follows the plugin's write-rails. It is the mutating counterpart to the read-only get-ghl-workflow-logs.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-workflow-fast-forward\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78F5GZERF2S6CMHXWQYQEHZ","ghl-voice-ai","Build and configure GoHighLevel Voice AI phone agents — the prompt, the voice, the actions (appointment booking, call\u002Fagent transfer, contact-field extraction, SMS, workflows, custom API), knowledge bases, MCP servers, working hours, and outbound consent. Use when the user says 'set up a voice agent', 'build a phone agent', 'my AI should answer calls', 'book appointments over the phone', 'outbound calling', 'the agent isn't transferring calls', 'change the voice', or names a Voice AI agent. Internal API — the public rail exposes only how the agent sounds, not what it does.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-voice-ai\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78F5A7S9450G94K3Z7P0HWK","ghl-system-conventions","House conventions for building GoHighLevel systems — workflow naming and structure, tag\u002Ffield\u002Fcustom-value discipline, pipeline and opportunity decisions, copy rules, and the pre-build approval document the operator signs off before anything gets created. Account-agnostic, for ANY GHL sub-account. Use whenever designing, building, editing, reviewing, or discussing GHL workflows, automations, pipelines, stages, opportunities, tags, custom fields, custom values, calendars, or AI agents — even if the user never says \"conventions\" or \"standards\". Load it BEFORE proposing a design or creating any GHL object, so the proposal already looks the way the operator wants it.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-system-conventions\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78F54ZQZ21VS3JQJ21QVGWS","ghl-snapshots","GoHighLevel snapshots — capturing a sub-account's assets into a reusable snapshot, refreshing one, curating what it carries, and checking load conflicts. Use when a task involves creating or updating a snapshot, deciding what an account template should include, asking why a snapshot came out empty or is stuck processing, or planning a rollout onto other sub-accounts. Read it BEFORE calling any \u002Fsnapshots path by raw_request — two of the write endpoints silently do the wrong thing.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-snapshots\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78F4Y7ZHHJ1DMV11TC1CPVW","ghl-reverse-engineering","Map a GoHighLevel internal surface exhaustively — enumerate every screen, panel, control and save path a feature has, capture the real request behind each one, prove what each field does by differential, and write the result into the corpus. Use when the user wants to understand how a GHL feature works under the hood, extend an engine to an object the public API can't reach, re-sweep a surface that already has partial coverage, or asks to reverse-engineer \u002F sniff \u002F capture \u002F trace anything internal. GHL permits inspecting your own account's traffic. This is a MAPPING skill, not a lookup: it finishes when the surface is exhausted, not when the first endpoint is found.","https:\u002F\u002Fgithub.com\u002Fuxieee\u002Fuxie-ghl-factory\u002Fblob\u002Fmain\u002Fplugins\u002Fuxie-ghl-factory\u002Fskills\u002Fghl-reverse-engineering\u002FSKILL.md",[],[]]