Event Credit Distribution

Use this skill when an event organizer wants to determine eligible credit recipients from Luma and a Google Form or equivalent sheet, map one credit pair to each recipient, send the organizer's approved message through XChat, and preserve resumable delivery state.

The skill defines a workflow and safety boundary. It does not authorize external messages by itself. Before any send, require explicit user authorization for the recipients and message.

Inputs and outputs

Collect or locate:

• The event's Luma guest-management URL or event ID.
• The form or sheet URL, exact tab title, and the column containing the required X handle or X profile URL.
• A Codex credit inventory and an API credit inventory with a stable row or inventory identifier.
• The approved message template with placeholders such as {{codex_url}} and {{api_code}}.
• Organizer exclusions and any direct organizer-confirmed identity links.

Keep event data in the event workspace, not in this skill. A useful event workspace contains a Luma snapshot, a mapping report, source inventories, and delivery-checklist.md. Preserve existing filenames and local conventions when they already exist.

The final report must distinguish eligible, held, excluded, attempted, confirmed-sent, and unknown records. Link the checklist and mapping report when they are created or updated.