video-ideas
Skill0 starsChanged 7 months agoMITView on GitHub
Capture video content ideas into the user's Notion Video Ideas database. Track from Draft to Ready to Published. Use when the user mentions a video idea, content concept, or says "video idea", "add to video ideas", "content idea", "I should film", "that would make a good video".
In this repository57 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- knowledge/CLAUDE.mdCLAUDE.md
- agent-harness-constructionSkill
- agentic-engineeringSkill
- ai-first-engineeringSkill
- api-designSkill
- backend-patternsSkill
- blueprintSkill
- bookmarkSkill
- brain-dumpSkill
- building-explainerSkill
- calendar-managerSkill
- code-engineerSkill
- compileSkill
- continuous-agent-loopSkill
- continuous-learningSkill
- copywriterSkill
- cost-aware-llm-pipelineSkill
- councilSkill
- database-migrationsSkill
- day-plannerSkill
- debriefSkill
- deep-researchSkill
- deployment-patternsSkill
- docker-patternsSkill
- e2e-testingSkill
- claude-apiSkill
- coding-standardsSkill
- eng-inboxSkill
- updateSkill
- enterprise-agent-opsSkill
- eval-harnessSkill
- frontend-patternsSkill
- humanizerSkill
- iterative-retrievalSkill
- log-expenseSkill
- memory-auditSkill
- migrateSkill
- minimalist-uiSkill
- onboardSkill
- full-output-enforcementSkill
- postgres-patternsSkill
- redesign-existing-projectsSkill
- regex-vs-llm-structured-textSkill
- researchSkill
- search-firstSkill
- security-reviewSkill
- security-scanSkill
- self-upgradeSkill
- high-end-visual-designSkill
- spending-summarySkill
- design-taste-frontendSkill
- tdd-workflowSkill
- transcribeSkill
- verification-loopSkill
- weekly-reviewSkill
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
- Distinctive: line 25
If not present, ask the user to set it up or suggest running the onboard skill.
- Distinctive: line 41
Write a clear, compelling title for the Name field (how it would read in a content calendar).
- Distinctive: line 42
If the user shared a URL that inspired the idea, capture it in Source URL.
- Distinctive: line 44
If the user provides extra context (hook, angle, target audience, key points), add it as page body content.
- Very specific: line 45
Create the entry via mcp__notion__notion-create-pages.
- Distinctive: line 50
Default Status is "Draft" unless the user says it is ready to film.
- Distinctive: line 52
If the idea connects to an existing content series or goal, note that in the page body.
- Distinctive: line 54
If the user brainstorms multiple ideas at once, save each as a separate entry.
≈ “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
Skill: Video Ideas
When to Use
- User mentions a video idea, content concept, or filming plan
- User says "video idea", "add to video ideas", "content idea", "I should film", "that would make a good video"
- User shares a link that inspires a video concept
- During day planning or content brainstorms
Prerequisites
Writes to a Notion database. The user must have configured in personal/notion-databases.md:
video_ideas_database_id: <user's Notion database ID>
video_ideas_data_source: collection://<data source id>
video_ideas_parent_page: <parent page id>If not present, ask the user to set it up or suggest running the onboard skill.
Expected Notion Schema
| Property | Type | Options |
| Name | title | The video concept |
| Date | date | Auto-set to today |
| Source URL | url | Optional — inspiration link |
| Status | select | Draft, Ready, Published, Skipped |
Adapt to the user's actual property names if they differ.
Steps
- Extract the video concept from the user's message.
- Write a clear, compelling title for the Name field (how it would read in a content calendar).
- If the user shared a URL that inspired the idea, capture it in Source URL.
- Set Date to today. Set Status to "Draft".
- If the user provides extra context (hook, angle, target audience, key points), add it as page body content.
- Create the entry via
mcp__notion__notion-create-pages. - Confirm back with the saved title.
Rules
- Default Status is "Draft" unless the user says it is ready to film.
- Titles should be punchy and descriptive. Think YouTube/Short titles, not internal notes.
- If the idea connects to an existing content series or goal, note that in the page body.
- Green tier — save first, confirm after.
- If the user brainstorms multiple ideas at once, save each as a separate entry.
Output Format
Saved to Video Ideas:
- [Name] (Status)One line per entry. If a Source URL was captured, append "(from [domain])".
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.

