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.

Use the authorized transport already established for the event before selecting a fallback:

• If a resident XChat app or authenticated XChat web session is available, prefer that existing route and verify its underlying send response. A resumed run must preserve the transport used by prior confirmed sends unless the organizer explicitly authorizes a change.
• Do not launch a standalone XChat CLI merely because it is installed. The CLI is not the default transport for this workflow.
• Treat an interactive XChat PIN: prompt as a CLI fallback condition, not as a required step. Only use the CLI PIN flow when the organizer explicitly chooses the CLI or the established transport is unavailable and the fallback is authorized. A PIN prompt alone is never evidence of a send.

Before every XChat Web send or retry, pass the transport state gate: