yt-brief
Skill1 starsChanged 37 days agoMITView on GitHub
Turn a script or an idea into a production brief you can shoot from - the shot list, the b-roll, the on-screen moments, the gear, and a runtime budget that keeps the edit from sprawling. Use for "shot list", "production brief", "how do I film this", "what b-roll do I need", or planning a shoot before recording.
In this repository25 other files it gives its agents.
- openai/AGENTS.mdAGENTS.md
- llms.txtllms.txt
- yt-analyticsSkill
- yt-auditSkill
- yt-chaptersSkill
- yt-collabSkill
- yt-commentSkill
- yt-editSkill
- yt-endscreenSkill
- yt-funnelSkill
- yt-ideaSkill
- yt-packageSkill
- yt-planSkill
- yt-repurposeSkill
- yt-retentionSkill
- yt-scriptSkill
- yt-seoSkill
- yt-seriesSkill
- yt-shortsSkill
- ytSkill
- yt-sponsorSkill
- yt-thumbnailSkill
- yt-trendSkill
- yt-viralSkill
- yt-voiceSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 13
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
- Very specific: line 19
Run it after /youtube-agent-pro:yt-script - it reads the beats the script marked and turns each into a shot.
- Distinctive: line 24
Use the available voice profile or creator context (see the operating guide) for the format: on camera or not, the desk, whether there is …
- Distinctive: line 26
Do not invent gear or locations the creator did not mention.
- Distinctive: line 30
The shot list: Every script beat becomes a shot: what is on camera, the framing (talking head, screen capture, b-roll, overlay), and the …
- Distinctive: line 45
Read the script's beats (or build them from the idea).
≈ “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.
Files
yt-brief
Read the shared operating guide for profile lookup, helper paths, capability limits, and cross-skill routing before using this workflow.
The gap between a good script and a watchable video is production, and production fails at the planning stage, not the editing one. This turns the words into a thing you can point a camera at.
Run it after /youtube-agent-pro:yt-script - it reads the beats the script marked and turns each into a shot. If there is no script yet, it can work from a tight idea, but a script first is far better.
Before you plan
- Use the available voice profile or creator context (see the operating guide) for the format: on camera or not, the desk, whether there is an intro, the usual length. The brief must match what the creator can actually film with what they have.
- Do not invent gear or locations the creator did not mention. Plan the shoot they can do this week.
The brief
- The shot list. Every script beat becomes a shot: what is on camera, the framing (talking head,
screen capture, b-roll, overlay), and the one line said over it. The script already marks
[ON SCREEN: ...]- turn each into a concrete shot, because "a talking head with nothing to look at is a podcast". - The b-roll list. Everything that needs a second visual - pulled out as its own checklist so it gets captured on the day, not improvised in the edit (where it does not exist).
- The on-screen text / graphics. The numbers, the labels, the receipts the hook promised. List them so they are built before the edit, not during.
- The gear and setup. From the creator's format - mic, camera, screen capture, lighting. Minimal, real, what they own.
- The runtime budget. Allocate the target length across the beats at ~150 words/minute so the edit has a target and does not sprawl to 18 minutes of a 9-minute idea.
The move
- Read the script's beats (or build them from the idea).
- Produce the shot list, b-roll checklist, graphics list, gear list and runtime budget.
- Flag any beat that has no visual - that is a retention cliff waiting to happen.
What to hand back
- the shot list, beat by beat, with framing and the line said over each
- the b-roll and on-screen-graphics checklists
- the gear/setup list and the runtime budget
- one line: the beat that will be hardest to film, and the simplest way to cover it
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.