agentleFS
nickmerichnickmerich/artist-led-events-skills/skills/content-capture-and-rights/SKILL.md

content-capture-and-rights

Skill0 starsChanged 25 days agoMITView on GitHub

Plans photo and video capture for an artist-led athletic event, including shot list, crew, consent, minors, artist approvals, music rights in published video, partner deliverables, and delivery timelines. Use for "what should we shoot", "build the shot list", "can we post this video with the song", "do we need releases", or "what content does the sponsor get".

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:

    Start from the concept line.

    line 13
  2. Distinctive:

    Must-get list (adapt per sport):

    line 15
  3. Distinctive:

    Every level taking part, especially the open-door group

    line 18

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

Content Capture and Rights

Step 1: Shot list from the story

Start from the concept line. Capture the moments that prove it: the open door, strangers becoming a crew, the artist doing the hard thing alongside people, the shared total.

Must-get list (adapt per sport):

  • Arrival and check-in, faces not just backs
  • Welcome briefing, the crowd from the front
  • Every level taking part, especially the open-door group
  • The artist moment
  • The connection moment (people talking, partners counting reps, groups at the turnaround)
  • The finish or the collective number
  • Partner deliverables as listed in signed agreements
  • The hang after

Step 2: Consent

  • Photo/video consent is a separate opt-in at registration. Give non-consenting participants a visible marker (colored wristband or sticker) and brief the crew to avoid featuring them.
  • Minors: guardian consent, and avoid identifying minors in published content unless guardians explicitly agree.
  • Close-up features of a person in published content: confirm with that person before posting.
  • Medical incidents: never captured or posted.

Step 3: Artist approvals

Posts featuring the artist follow the approval terms in the artist term sheet. Send selects in one batch with a response window.

Step 4: Music in video

Posting video with a song needs sync rights for the composition and the recording, not just the event's performance license. Options: the artist's own music with written permission from whoever owns the publishing and master, platform-licensed music used inside the platform's own tools (follow the platform's terms; this doesn't cover partner ads), or licensed production music. Partner paid ads need their own clearance.

Step 5: Delivery

Agree in advance: number of selects, edits, formats, delivery dates, and usage window. Partners get exactly what the agreement says. Track in assets/shot-list.md.

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.