agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/press-and-media/SKILL.md

press-and-media

Skill0 starsChanged 25 days agoMITView on GitHub

Earns press and podcast coverage for an artist-led athletic event by separating what is verified from what is hoped, clearing artist and participant quotes before use, picking one angle per outlet type (local, music, running, business, national trend), finding each outlet's stated pitch route, and tracking replies instead of sends. Use for "write the press release", "who should we pitch", "can we say this in press", "follow up with reporters", or "press plan for the event".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before any writing, list every claim the release might make and label it.

    line 13
  2. Distinctive:

    Keep a one-line log per outlet: date, route used, source URL for the route, what was sent, reply status, next date.

    line 70
  3. Distinctive:

    Call a calendar listing a feature, or a brief a profile.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Press and Media

Step 1: Build the proof table first

Before any writing, list every claim the release might make and label it.

Claim typeAllowed whenOtherwise write
Signups and finishersOrganizer-recorded counts exist"about N," or leave out
Artist involvementWritten in the deal termsName the album or the inspiration, never say the artist attended or ran
Artist or participant quoteThat person approved the exact wording in writingPlaceholder, or no quote
Partner or sponsorSigned agreement and written OK for press use"supported with in-kind [product] at [event]" or omit
Future eventPermit, venue, and date confirmed in writing"planning a return in [month]"
First-time or demographic statsCollected at registration with consentOmit

Signups, check-ins, and finishers are three numbers. Use the one you can defend.

Step 2: One angle per outlet type

Outlet typeAngleWhat they need
Local newsA neighborhood did a thing; photos; a date people can attendWho, when, where, how to join, one cleared photo
Music pressThe artist's work became a physical experienceA cleared artist quote, the album or project, a link to the artist's own page
Running pressThe format: free, small, permit-approved, who showed upCounts, course, what made it different from a race
Business or tech pressThe producer's model: how it is funded, what it costs, what is reusableEconomics you are willing to publish, the repeatable system
National trendThe counterexample to whatever is being covered this monthA link to the trend story, one sentence on why yours is the other end of it

Pitching a music outlet without a cleared artist quote wastes the first contact. Clear the quote first.

Step 3: Find the outlet's stated route

Fetch the outlet's contact, about, or pitch page and use what it says: a tips inbox, a form, a named desk editor, or "reply to the newsletter." Record the URL you took it from. If a page states no route, pitch a reporter from a recent byline on a similar story. Never guess an address pattern; a bounce is a lost outlet.

Step 4: Write the release and the note

  • Headline is the story, not the organization. "When the album became a 5K" beats "[Org] hosts run."
  • First paragraph: what happened, where, how many, when it happens again.
  • Second: the artist connection and the community, with only cleared quotes.
  • Third: who produced it, what it costs to join, how to join.
  • Boilerplate: one paragraph, one link, one working press contact that has been tested with an external send.
  • The cover note is four sentences, personalized to one recent piece the recipient wrote, and offers one specific thing: a visit, a call, photos, or a date.

Step 5: Send in waves tied to real dates

A wave needs a reason: an event in seven to ten days, a result from the weekend, a confirmed date, or a cleared quote. A release with no new reason is noise. Follow up once, seven days later, with new information. Then stop.

Step 6: Podcasts are a separate channel

Podcast hosts reply more often than reporters. Pitch with one recent episode named, one guest angle, and a second community voice offered. When a host replies with a scheduling question, answer the same day. An unanswered "Zoom or phone?" is a lost recording.

Track replies, not sends

CountMeans
SentActivity. Report it, do not celebrate it.
DeliveredNot bounced. Still activity.
RepliedThe first real signal
ScheduledA recording, call, or visit on the calendar
Published, organization namedCoverage
Published, organization not namedA listing. Do not call it a feature.

Keep a one-line log per outlet: date, route used, source URL for the route, what was sent, reply status, next date. Report counts outside the team; keep contact details inside it.

Do not

  • Invent a founder quote and label it approved.
  • Reuse a quote from your own website as press-cleared. Website presence is not press permission.
  • Call a calendar listing a feature, or a brief a profile.
  • Send the same release to the same outlet twice.
  • Name children in photos, or any participant without consent.

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.