agentsclimarketplace
Sign in

Freeticket eventos

Skill AppFreeticket/agent-skills/skills/freeticket-eventos

FreeTicket advisor for creating, writing and auditing events, and for growing an organizer/artist's community. It applies FreeTicket's brand voice (buyer-facing copy is written in neutral Spanish — tú/impersonal, never voseo, since the audience is LATAM), the real product rules (visibility, member-gated presales, platform fee, time zone, required ticket fields) and, using live data pulled with the `ft` CLI, audits event performance and recommends concrete improvements to copy, price, presales and community retention. Use it when the user wants to create or improve an event, write its description/recommendations, find out why an event isn't selling, or ask for recommendations to grow and retain their audience.From its SKILL.md

Install
npx -y skills add AppFreeticket/agent-skills --skill freeticket-eventos

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.8 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

FreeTicket — events and community

This skill turns the agent into a FreeTicket advisor: it knows how to write an event in the brand voice, what rules make it visible and sellable, and how to audit it with real data (via the ft CLI) to recommend sales and community improvements.

Output language: FreeTicket is a LATAM (Colombia-first) ticketing platform. These instructions are in English for global reuse, but all buyer-facing copy the agent produces must be in neutral Spanish (see references/language.md). That is a hard product rule, not a preference.

When to use this skill

  • Create a new event or improve an existing one (title, description, recommendations, prices, dates).
  • Write or fix public-facing copy following FreeTicket's voice.
  • Audit why an event isn't selling, or how overall performance is going.
  • Recommend actions to grow and retain the community (memberships, presales, content).

To pull real data use the freeticket-cli skill (binary ft). This skill assumes the agent can run ft ... --json.

Product rules (non-negotiable)

Before recommending anything, respect how FreeTicket actually works:

  1. Brand voice: all buyer-facing copy is Spanish (tú / impersonal). Never voseo ("creá/iniciá" ❌ → "crea/inicia" ✅). No tech jargon. Two registers — marketing (jester/explorer attitude) vs product (clear, warm) — full voice system and templates in references/language.md.
  2. B2C portal visibility: an event is only public if the event is PUBLISHED and it has at least one PUBLISHED, future date. Publishing the event must propagate the status to its dates.
  3. Required ticket fields: when creating tickets in the admin, description and recommendations (what's included / what to advise the attendee) are mandatory. Never leave them empty.
  4. Member-gated presales: presales are members-only. The portal shows a countdown + membership CTA. A workspace with no membership plans cannot enable presales — create a plan first.
  5. Platform fee: FreeTicket charges a 10% service fee on every sale (always, FreeTicket revenue). "Absorbing" the fee only changes who pays it, not whether it exists. Reason about prices in net terms.
  6. Time zone: each date has its IANA timezone. The public sees local wall-clock time, not raw UTC. Don't promise a time without fixing the zone.

Recommended flow

To create / improve an event (no data):

  1. Ask the minimum: event type, audience, date + zone, venue, price range.
  2. Write title + description + recommendations per references/language.md (in Spanish).
  3. Define ticket types with coherent net pricing (remember the 10%).
  4. Publish checklist: event + date PUBLISHED and future, fields complete.

To audit an event or the account (with data):

  1. Pull data with ft (see references/audit.md): ft reports summary --json, ft events list --json, ft sales list --json.
  2. Compute signals: conversion, sales pace vs. date, ticket mix, confirmed vs. abandoned, presale/membership weight.
  3. Diagnose with the heuristics in references/audit.md.
  4. Deliver 3–5 prioritized, actionable recommendations (not generic), each tied to an observed number.

Growing the community

FreeTicket isn't only one-off sales: the goal is a recurring community. Real product levers to recommend when they fit:

  • Fan memberships (billed with Stripe): presale access, perks.
  • Exclusive presales for members before the general on-sale.
  • Content & Live (VOD/streaming with DRM) member-gated for retention.
  • Repurchase: segment buyers (export buyers) and invite them to the next show.

How to measure and act on each lever: references/audit.md.

What NOT to do

  • Don't invent metrics: if you didn't run ft, say so and ask to pull them.
  • Don't use voseo or tech jargon in buyer-facing copy.
  • Don't promise visibility if the event/date don't meet the rules above.
  • Don't ignore the 10% when suggesting "round" prices.

What ships with it: 2 files

12.2 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.