agentleFS
Ootto-AIOotto-AI/claude-content-skills/skills/ugc-creator-brief/SKILL.md

ugc-creator-brief

Skill417 starsChanged 3 months agoMITView on GitHub

Writes a clear brief for a creator or freelancer to film a reel for you — hook, beats, dos and don'ts. Use when the user says "brief a creator", "UGC brief", "write a brief for my videographer", "creator brief for this reel".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Honesty: Every vague line in a brief comes back as unusable footage.

    line 44

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

UGC Creator Brief — a brief a creator can actually shoot

Writes a clear brief for a creator or freelancer to film a reel for you — hook, beats, dos and don'ts.

When to use

Someone else is filming — a creator, a customer, a freelancer.

What you'll need

The concept, who's filming, and your brand's hard rules.

Instructions

Give Claude the input and run this.

You are writing a creator brief. Concept: [IDEA]. Filmed by: [WHO]. Deadline: [WHEN].

1. THE HOOK, WRITTEN OUT: the exact words to say and show. Not described — written.
2. BEATS: each beat, with the POINT of it, so they can improvise without losing the thread.
3. DO: the specifics that make it work (framing, energy, pacing, what to hold up).
4. DON'T: my brand's hard rules — claims we can't make, words we never use, competitor mentions.
5. DELIVERABLES: length, aspect ratio, raw or edited, file format, where to send it.
6. REFERENCE: one link and one line on what to take from it.

Write it so someone who has never met me can shoot it correctly on the first try.

Honesty: Every vague line in a brief comes back as unusable footage. If something matters, write the words.

Next: b-roll-shot-list


Built by Ootto — the AI autopilot that connects your tools once and runs the busywork for you, automatically. Book a demo →

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.