agentleFS
Sign inStart free
AppFreeticketAppFreeticket/freeticket-mcp/skills/publish-event/SKILL.md

publish-event

Skill0 starsChanged 4 months agoMITView on GitHub

Publish a FreeTicket event end to end with the FreeTicket MCP tools — venue, event, dates, ticket types, optional member presale and lineup, then publish now or schedule it. Use when the user wants to create, set up, launch or put on sale a show/event in FreeTicket.

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
  1. Very specific:

    If the workspace has reusable templates (ticket_templates_list), prefer ticket_templates_instantiate with eventDateId (override name, price …

    line 25

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publish an event end to end

Work in ONE workspace (writes are never global). If the session reaches several, ask which one and confirm with whoami.

  1. Venue. venues_list; if it does not exist, venues_create (name, address, city, country ISO-2).
  2. Event (draft). events_create with name, a unique slug, venueId and at least one date (startsAt ISO 8601, timezone, default America/Bogota). It is born as DRAFT.
  3. More dates. event_dates_create per extra show. Use maxPerCustomer for a per-buyer cap and doorsOpenAt if known.
  4. Classification and images. events_update: genre (+ subgenre or genreOther when genre is otro), audience, coverImageUrl, squareImageUrl, storyImageUrl. Performing arts above 400 capacity per date need pulepCode (422 PULEP_REQUIRED).
  5. Ticket types. event_dates_list to get the date ids, then ticket_types_create per date (price in COP, capacity, maxPerOrder, isVisible, organizerAbsorbsFee; saleStartsAt/saleEndsAt optional). If the workspace has reusable templates (ticket_templates_list), prefer ticket_templates_instantiate with eventDateId (override name, price or capacity if needed): it copies price, discount, members-only gate and buyer form in one call.
  6. Member presale (optional). plans_list → presale_windows_create on each ticket type (planId, presaleStartsAt, presaleEndsAt in UTC …Z, optional presaleCapacity). Check with presale_windows_list.
  7. Lineup (optional). artists_search (q ≥ 2 chars) → events_artists_set with the FULL ordered list of ids; artists without an account go in inviteEmails. This sends emails: confirm first. Pending invites: event_artist_invitations_list.
  8. Go live — pick one, after the human confirms:
    • now: events_publish;
    • later: events_schedule with publishAt (auto-publish) or saleStartsAt (publish now, open sales later). Undo a publishAt with events_unschedule.
  9. Verify. events_get (status) and reports_inventory with eventId (capacity per date and type). Report what was created, with ids.

Rules: never invent ids — read them from the previous tool's result. Surface API errors (error.code) to the human as-is instead of retrying blindly.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free