show-day-close
Skill0 starsChanged 4 months agoMITView on GitHub
Close out a FreeTicket show day with the FreeTicket MCP tools — live attendance, the access-close record, attendance vs. capacity, sales and revenue of the date, stuck payments, attendee export and settlement status. Use when the user asks for the end-of-night/show-day report, the "cierre" or "acta de cierre de acceso" of an event date, or how a show went.
In this repository6 other files it gives its agents.
- .agents/skills/zod/AGENTS.mdAGENTS.md
- typescript-advanced-typesSkill
- zodSkill
- community-moderationSkill
- course-builderSkill
- publish-eventSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read-only unless the human asks for an action.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Show-day close
Read-only unless the human asks for an action. Ask for the event (or find it
with events_list + q) and the date (event_dates_list).
- Live door. While the show is on,
reports_live_attendancelists the dates happening right now withsold,validatedandvalidatedPct(scope: "own"drops hosted shows). Fine to poll, not faster than ~20 s. - Access-close record.
event_dates_access_close_statuswith the date id:live.issued,live.checkins(what a signature would freeze now) and, if already closed,closedCheckinsand who signed. Report it; do not sign on your own initiative.event_dates_access_close_signis irreversible, emails the record to the workspace and needs ADMIN: call it only when the human explicitly asks to sign the record for that date, after showing them the currentlive.checkins. It opens 2 hours after the start (409ACCESS_CLOSE_NOT_SIGNABLE_YETgivessignableFrom); 409ACCESS_ALREADY_CLOSEDmeans it is done — do not retry. - Capacity and sold.
reports_inventorywitheventDateId(groupBy: "ticketType"): capacity, sold, reserved, available. - Revenue.
reports_by_eventwithfrom/toaround the date, andreports_timeseries(interval: "day",event) for the sales curve. - Stuck payments.
sales_payment_intentswitheventandeventDate(onlyAbandoned: truefor journeys that picked seats and never paid):funnelgives the drop-off, each journey itsstageandoutcome(REJECTEDcarries the gatewayreason). For a specific PENDING sale,sales_listwitheventDateandstatus: "PENDING", thensales_attemptsexplains what the gateway did. Releasing the stock of a PENDING sale whose payment never started issales_abandon; cancelling or refunding a confirmed one issales_cancel/sales_refund. All three are irreversible: only on explicit request. - Door, one ticket.
tickets_accesswith its QR code (read-only). Admitting someone istickets_checkin— only on request. - Attendees.
reports_export_attendeeswitheventDate(one row per ticket). It contains personal data: summarize, do not paste it whole unless asked. The same goes for names and emails insales_payment_intents. - Money.
reports_financialswithevent(gross, fees, net to settle per date) andsettlements_listwitheventfor the payout status.settlements_documentreturns a 5-minute signed link, not the file.
Close with a short summary: validated / sold / capacity (%), access-close status (open, or signed with the frozen count), gross and net, abandoned or failed payments needing attention, and the settlement status.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

