菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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).
| name | organizations |
| version | 1.0.0 |
| description | 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. |
Multi-calendar operations. An organization owns one or more calendars; this resource is the only way to list calendars across the org or move an event between them.
The bound API key must belong to an org admin for write actions.
CLI prefix: node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations <action>.
| Endpoint | Action |
|---|---|
GET /v1/organizations/admins/list | organizations admins-list |
GET /v1/organizations/calendars/list | organizations calendars-list |
POST /v1/organizations/calendars/create | organizations calendars-create --name ... |
GET /v1/organizations/events/list | organizations events-list |
POST /v1/organizations/events/transfer-calendar | organizations events-transfer-calendar --event-id ... --calendar-id ... |
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations admins-list
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations calendars-list --all
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations calendars-create \
--name "Acme Community Scholars" \
--slug acme-community-scholars \
--description "Talks, demos, and reading groups for the community." \
--avatar-url <https-url-from-images-upload> \
--tint-color "#4F46E5"
slug must be unique across all of lu.ma. Check first via entity lookup --slug ... (returns 404 if available). If avatar-url is omitted, Luma assigns a default.
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations events-list \
--after 2026-01-01T00:00:00Z --before 2026-12-31T23:59:59Z --all
Unlike calendar list-events, this aggregates every calendar the org owns. Useful for cross-cal reporting.
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" organizations events-transfer-calendar \
--event-id evt-XXXX \
--calendar-id cal-YYYY
Both calendars must belong to the same org. Transfer keeps the event ID, guests, tickets, and host assignments. Guests are not notified.
calendars-create is publicly visible immediately at lu.ma/<slug>. Brand-check the name/avatar/tint first.events-transfer-calendar changes which audience sees the event going forward — confirm the destination calendar matches the event's intended audience before running.