菜单
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).
用 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 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.
| name | memberships |
| version | 1.0.0 |
| description | 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). |
Paid tier membership for a calendar. Lets people join a tier (free or paid) and gates members-only events.
CLI prefix: node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships <action>.
| Endpoint | Action |
|---|---|
GET /v1/memberships/tiers/list | memberships tiers-list |
POST /v1/memberships/members/add | memberships members-add --email ... --membership-tier-id ... |
POST /v1/memberships/members/update-status | memberships members-update-status --user-id ... --status approved |
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships tiers-list --all
Returns {entries: [{api_id: "memt-...", name, price_cents, currency, ...}]}. Tier IDs (memt-XXX) are needed for members-add.
# Free tier
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships members-add \
--email alice@example.com \
--membership-tier-id memt-XXXX
# Paid tier — payment is handled externally (e.g. Stripe), so set --skip-payment
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships members-add \
--email alice@example.com \
--membership-tier-id memt-XXXX \
--skip-payment true
--skip-payment true is required for paid tiers when the user has paid via Stripe or another channel — without it, Luma will reject the call.
Registration questions (if the tier defines any) go via --body:
{
"email": "alice@example.com",
"membership_tier_id": "memt-XXXX",
"skip_payment": true,
"registration_answers": [
{"question_api_id": "ques-XXXX", "answer": "Drug discovery"},
{"question_api_id": "ques-YYYY", "answer": "Cycle 12"}
]
}
For tiers that require host approval (or for handling chargebacks / fraud):
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships members-update-status \
--user-id alice@example.com --status approved
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" memberships members-update-status \
--user-id usr-XXXX --status declined
--user-id accepts both usr-... and the user's email. --status: approved | declined.
There is no dedicated endpoint — pipe through calendar list-people:
node "${CLAUDE_PLUGIN_ROOT}/bin/luma.js" calendar list-people \
--calendar-membership-tier-id memt-XXXX \
--member-status approved \
--all
--member-status filter values: approved | pending | approved-pending-payment | declined.
members-add and members-update-status approved both email the user a welcome / approval notification. Confirm recipient before running.--skip-payment true — otherwise the user gets a free membership.