yt-brief
Skill1 starsChanged 11 days agoApache-2.0View on GitHub
Refine a YouTube video idea into a structured production brief with
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ahmedsakri/youtube-agent-protheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ahmedsakri/youtube-agent-pro★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- youtubeSkill
- tiktok-studioSkill
- yt-analyticsSkill
- yt-chaptersSkill
- yt-commentSkill
- yt-ideationSkill
- yt-outlineSkill
- yt-packagingSkill
- yt-researchSkill
- yt-studioSkill
- yt-title-lintSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 36
If the user is coming from the ideation flow, load validated_ideas.json for the full context on the selected idea.
- Distinctive: line 42
Before writing the brief, understand the topic deeply:
- Distinctive: line 79
Value proposition: - After watching, the viewer will be able to [specific outcome]
- Distinctive: line 100
Add/remove key points
- Distinctive: line 103
Start over with a different approach
- Distinctive: line 114
Practical value first: Every key point should contribute to the viewer being able to DO something.
- Distinctive: line 116
Honest about scope: If a topic is too big for one video, say so and suggest splitting it.
- Distinctive: line 135
Document the configuration for team reference
≈ “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
YouTube Brief
You are creating a structured production brief for a YouTube video. The brief is the bridge between an idea and a filmable video - it defines what the video IS.
Before You Start
You need from the user:
- The video idea - Either a validated idea from
/yt-ideate(with title, tier, type, angle) or a raw idea the user wants to develop - Any constraints - Timeline, specific features to include/exclude, target length, team capacity
If the user is coming from the ideation flow, load validated_ideas.json for the full context on the selected idea.
The Briefing Process
Step 1: Research the Topic
Before writing the brief, understand the topic deeply:
- What does this feature/tool actually do? (Use WebSearch if needed)
- What are the common pain points or confusion points?
- What existing content exists? What angle would differentiate this video?
- What's the practical value for the target audience?
Step 2: Define the Video Identity
Work with the user to lock in:
Content Type & Tier:
- Confirm which tier and category this falls under
- This determines the format, length, and production approach
The Angle:
- What's the unique take? Why would someone click THIS video over alternatives?
- The angle should be specific and defensible, not generic
- Good: "How to use MCP integrations to automate your marketing reporting without any code"
- Bad: "MCP tutorial"
Target Audience Segment:
- Who is the primary viewer?
- What's their starting knowledge level for this topic?
Step 3: Write the Brief
The brief must include:
- Title (working) - Will be refined in packaging, but needs a clear working title
- Content tier & type - e.g., Tier 1 / Feature Tutorial
- The angle - 1-2 sentences: what makes this video unique
- Target audience - Who exactly is this for, and what do they already know
- Key points - 5-8 main things the viewer will learn or see demonstrated
- Value proposition - After watching, the viewer will be able to [specific outcome]
- CTA asset - What free asset can be given away? (template, skill, workflow, plugin)
- Prerequisites - What does the viewer need to have set up before watching?
- Demo requirements - What tools, accounts, or setups are needed for filming?
- Estimated length - Target duration based on content type
- Urgency/timing - Is this time-sensitive (update video) or evergreen?
Step 4: Review with User
Present the complete brief and ask:
"Here's the brief for '[title]'. Review it:"
[Full brief in clean markdown format]"What would you like to adjust?"
- Approve - move to packaging
- Adjust the angle
- Add/remove key points
- Change the CTA asset
- Change the target audience
- Start over with a different approach
This is a mandatory human checkpoint. Do NOT proceed without approval.
Step 5: Save the Brief
Save the approved brief as video-brief-yt-brief.md in the working directory.
Key Principles
- The angle is everything. A brief without a clear, differentiated angle will produce a generic video. Push the user to be specific.
- Practical value first. Every key point should contribute to the viewer being able to DO something. No filler sections.
- CTA integration. The CTA asset should feel like a natural extension of the video content, not a bolted-on pitch.
- Honest about scope. If a topic is too big for one video, say so and suggest splitting it. Don't try to cram a Full Tutorial into a Feature Tutorial.
- Team-ready. The brief should contain enough detail that a team member could start demo prep without asking follow-up questions.
Overview
Refine a YouTube video idea into a structured production brief with angle, key points, value proposition, CTA asset, and audience segment.
Prerequisites
- Access to the Yt Brief environment or API
- Required CLI tools installed and authenticated
- Familiarity with Yt Brief concepts and terminology
Instructions
- Assess the current state of the Yt Brief configuration
- Identify the specific requirements and constraints
- Apply the recommended patterns from this skill
- Validate the changes against expected behavior
- Document the configuration for team reference
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
Error Handling
| Error | Cause | Resolution |
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with Yt Brief |
| Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters |
| Resource not found | Referenced resource missing | Verify resource exists and permissions are correct |
Examples
Basic usage: Apply yt brief to a standard project setup with default configuration options.
Advanced scenario: Customize yt brief for production environments with multiple constraints and team-specific requirements.
Resources
- Official Yt Brief documentation
- Community best practices and patterns
- Related skills in this plugin pack
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.

