agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/launch-campaign/SKILL.md

launch-campaign

Skill0 starsChanged 24 days agoMITView on GitHub

Plans and drafts the six-week launch for an artist-led athletic event, leading with the artist's own audience, then the club and local partners, with an asset list, posting calendar, claim rules, and approval gates. Use for "plan the announcement", "write the launch posts", "how do we fill this event", "draft the artist's announcement", or "what goes out each week". Drafts only; the artist approves anything with their name, and nothing posts without approval.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 5

    Distinctive

    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. Distinctive:

    Every partner named has signed.

    line 18
  2. Distinctive:

    No invented urgency. "Sold out" only when it's true.

    line 42
  3. Distinctive:

    No unconfirmed names: talent, partners, or special guests.

    line 43
  4. Distinctive:

    No attendance claims beyond verified numbers.

    line 44
  5. Distinctive:

    Avoid wording that encourages impairment, risky behavior, or pushing through pain.

    line 45
  6. Very specific:

    Use assets/launch-checklist.md to track each asset through drafted → approved → scheduled → posted.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Launch Campaign

The artist's audience fills an artist-led event. Your job is to make it easy for the artist to invite them and easy for the people who come to bring a friend.

Before anything goes out

  • Venue path confirmed in writing.
  • Registration tested end to end.
  • Artist approved the announcement copy, title, and visuals in writing.
  • Every partner named has signed.

Six-week calendar (adjust to lead time)

WeekGoalArtistProducer / clubPartners
-6Soft demand testStory poll or "would you come?"Waitlist link
-5AnnounceAnnouncement post + story with linkRepost, email list, club channelsApproved mention
-4Why it mattersThe real reason (from the concept line)First-timer FAQ: "you can walk this"
-3Bring someone"Bring a friend" askPartner-funded spots storyPartner story
-2Proof of the doorwayTraining clip of the artist at their levelReal member clip, with consent
-1LogisticsCountdownFull logistics, weather plan, what to bring
0Day ofLive storiesLive stories
+1RecapThank-you postRecap, photo gallery, next eventPartner recap

Asset list

Announcement graphic (square and vertical), artist announcement copy, first-timer FAQ, logistics post, partner mentions, bring-a-friend share card, day-of story frames, recap template.

Copy rules

  • Visible signup URL as text in captions, not only "link in bio."
  • Lead with the experience and the people, not the partner.
  • Say what the open-door option is in every announcement ("walkers welcome," "every rep counts").
  • No invented urgency. "Sold out" only when it's true. "Limited spots" only with a real cap.
  • No unconfirmed names: talent, partners, or special guests.
  • No attendance claims beyond verified numbers.
  • Avoid wording that encourages impairment, risky behavior, or pushing through pain.

Messages to draft

  • Artist announcement (in the artist's voice, for their approval)
  • Producer announcement
  • Email to club or list
  • Partner-facing launch note
  • DM template the artist's team can send to superfans
  • Bring-a-friend message participants can copy and paste

Use assets/launch-checklist.md to track each asset through drafted → approved → scheduled → posted.

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.