elnora-luma

Luma read-only reporting + unattended automation — revenue/sales summaries, accounting/CRM roster exports, change digests (diff), capacity/approval-queue checks, and Luma↔Stripe payment reconciliation, plus the scheduling recipes (cron / launchd / Windows Task Scheduler / GitHub Actions) that run them hands-free. Sub-skill of `luma:`. Load only after the parent `luma` skill has matched (user explicitly said "luma" / "lu.ma") and the task is reporting, revenue/accounting, exports, digests, reconciliation, or scheduled/unattended Luma jobs.

Luma API CLI — every endpoint at public-api.luma.com (61 actions across events, guests, ticket types, coupons, hosts, tags, memberships, webhooks, organizations). Match ONLY when the user explicitly says "luma" / "lu.ma" / "luma.com" — never on bare "event", "RSVP", "guest list", "webhook", "ticket type", "coupon", "tag", or "membership" alone, since those are claimed by other tools (Calendar, Stripe, Slack, Vanta, etc.). TRIGGERS (all Luma-bound, none generic): "luma", "lu.ma", "luma.com", "luma event", "luma events", "luma calendar", "luma rsvp", "luma rsvps", "luma guests", "guests on luma", "guest list on luma", "registrations on luma", "approve luma guests", "luma ticket", "luma tickets", "luma ticket type", "luma ticket types", "luma coupon", "luma coupons", "luma webhook", "luma webhooks", "luma host", "luma hosts", "luma membership", "luma memberships", "luma tier", "luma tiers", "luma tag", "luma tags", "luma person tag", "luma event tag", "luma organization", "luma api", "luma openapi", "create even

Luma calendar — config, list-events, list-people, lookup-event, submissions (add/approve/reject), import-people, admins. Sub-skill of `luma:`. Load only after the parent `luma` skill has matched (user said "luma" / "lu.ma") and the task is calendar-scoped (not a single event).

Luma event lifecycle — create, get, update, cancel a Luma event, and manage hosts on it. Sub-skill of `luma:`. Load only when the parent `luma` skill has already matched (user explicitly said "luma" / "lu.ma") and the task is event lifecycle, not RSVPs (→ `luma:guests`) or pricing (→ `luma:ticketing`).

Luma guests / RSVPs — list, get, add, approve, decline, waitlist, and send invites for a Luma event. Sub-skill of `luma:`. Load only after the parent `luma` skill has matched (user explicitly said "luma" / "lu.ma") and the task is RSVPs / guest list management.

Luma paid calendar memberships — list tiers, add a member, approve/decline a pending member. Sub-skill of `luma:`. Load only after parent `luma` skill matched (user said "luma" / "lu.ma") and the task is Luma membership management (NOT subscriptions in Stripe or generic SaaS memberships).

Luma organizations — list org admins, list/create calendars in an org, list events across org, transfer an event between calendars. Sub-skill of `luma:`. Load only after parent `luma` skill matched (user said "luma" / "lu.ma") and the task is multi-calendar / organization-level Luma operations.

Luma event tags and person tags — create / update / delete / list, apply / unapply to events or people. Sub-skill of `luma:`. Load only after parent `luma` skill matched (user said "luma" / "lu.ma") and the task is Luma tagging (event tags for filtering events, or person tags for segmenting people).

Luma ticket types + coupons (event-level and calendar-level). Sub-skill of `luma:`. Load only after the parent `luma` skill has matched (user explicitly said "luma" / "lu.ma") and the task touches paid tickets, ticket type CRUD, or discount coupons.

Luma webhooks — CRUD + the complete event-type catalog and payload shapes for all 9 webhook events. Sub-skill of `luma:`. Load only after parent `luma` skill matched (user said "luma" / "lu.ma") and the task is Luma webhook subscriptions or consuming Luma webhook payloads (NOT Stripe / GitHub / generic webhook setup).