shoot-brief
Skill1 starsChanged 2 days agoMITView on GitHub
Writing a short phone-shoot brief when a planned unit lacks footage or a spoken comment. Use at stage 2.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-visualizationSkill
- approval-packSkill
- content-atomizationSkill
- dispatchSkill
- fact-checkSkill
- ffmpeg-skillSkill
- hook-storylineSkill
- idea-diceSkill
- jurySkill
- memory-compactionSkill
- perf-loopSkill
- publish-kitSkill
- seamless-insertSkill
- setupSkill
- sound-designSkill
- source-skeletonSkill
- style-memorySkill
- treg-gatewaySkill
- trend-scoutSkill
- utmSkill
- video-codeSkill
- weekly-cycleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Check media-index/ first: the shot may already exist.
- Distinctive: line 24
No more than 5 items per week unless the client asked for more.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Shoot brief
The human shoots in between other work, so the brief must take 30 seconds to read and 5–10 minutes to shoot.
Format (one message for the whole week)
Shoot for week W44 (≈10 min total):
1. [for R03, Friday] Opening the sliding panel — close-up, 5–7 s, vertical, no music.
2. [for R03] A comment from the founder in the workshop, 15 s: "Why doesn't it draft in winter?" — in their own words.
3. [for C02] Photo of the mounting joint, 2–3 angles in daylight.
Send to the folder "<folder from sources.yaml>" or right here.Rules
- State which unit each shot is for and by when it is needed.
- Describe each shot concretely: what is in frame, shot size (close-up / wide), duration, orientation (9:16 by default).
- For speech — give a question the person answers in their own words. Not a ready-made text.
- Check
media-index/first: the shot may already exist. - No more than 5 items per week unless the client asked for more.
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
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.

