domain-skills/luma: internal admin API (events, guests, invites)

[zachary-ai]

Adds a Luma domain skill covering the cookie-authed internal admin API the dashboard uses: calendar/admin/get-events, event/admin/get-guests (pagination + guest fields), and event/admin/invite/send (introspected from the UI's own network call). Documents the invite-capacity traps: dialog budget (N LEFT), silent capacity−1 selection of pasted lists, silent dropping of invalid addresses, and the reconcile-with-get-guests pattern. Field-tested sending ~500 invites today.

🤖 Generated with Claude Code

---

Summary by cubic

Documented Luma’s internal admin API for events, guests, and invites to enable faster, cookie-authed automation from a luma.com page.
Covers calendar/admin/get-events, event/admin/get-guests (pagination + guest fields), and event/admin/invite/send, plus auth requirements, invite-capacity pitfalls (selection cap, silent drops, dedupe), and a UI fallback for bulk invites.

^{Written for commit 7f561b7. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="domain-skills/luma/admin-api.md">

<violation number="1" location="domain-skills/luma/admin-api.md:20">
P2: The `calendar/admin/get-events` endpoint docs hard-code `pagination_limit=20` but don't explain pagination mechanics, while the `get-guests` section right below does include `has_more` and `next_cursor` guidance. If a calendar has more than 20 matching events, a script following this skill would silently see only the first page. Consider adding pagination instructions—`has_more`/`next_cursor` or the equivalent response fields—so callers know how to fetch the full calendar.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: The calendar/admin/get-events endpoint docs hard-code pagination_limit=20 but don't explain pagination mechanics, while the get-guests section right below does include has_more and next_cursor guidance. If a calendar has more than 20 matching events, a script following this skill would silently see only the first page. Consider adding pagination instructions—has_more/next_cursor or the equivalent response fields—so callers know how to fetch the full calendar.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At domain-skills/luma/admin-api.md, line 20:

<comment>The `calendar/admin/get-events` endpoint docs hard-code `pagination_limit=20` but don't explain pagination mechanics, while the `get-guests` section right below does include `has_more` and `next_cursor` guidance. If a calendar has more than 20 matching events, a script following this skill would silently see only the first page. Consider adding pagination instructions—`has_more`/`next_cursor` or the equivalent response fields—so callers know how to fetch the full calendar.</comment>

<file context>
@@ -0,0 +1,59 @@
+## Endpoints (introspected from the dashboard's own calls)
+
+- `GET calendar/admin/get-events?calendar_api_id=cal-XXX&pagination_limit=20&period=future`
+  — events for a calendar you admin. `period` is `past` / `future` (not
+  `upcoming`). Entries wrap the event: `{event: {...}, guest_count}`.
+- `GET event/admin/get-guests?event_api_id=evt-XXX&pagination_limit=100`
</file context>