setup-boring-video-skills
Skill191 starsChanged 7 days agoMITView on GitHub
Use when installing, validating, or repairing the Boring Video planning skill set before its first use.
In this repository10 other files it gives its agents.
- boring-videoSkill
- develop-topicSkill
- record-terminalSkill
- to-articleSkill
- to-narrationSkill
- to-scenesSkill
- to-spec-beatsSkill
- to-storyboardSkill
- to-videoSkill
- verysmallwoods-videoSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 8
Verify that the complete planning suite and its production dependency are available.
- Distinctive: line 31
If suite skills are missing, offer this complete install command.
≈ “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
Setup Boring Video skills
Verify that the complete planning suite and its production dependency are available. This skill validates the toolchain; it does not create a video project.
Required suite
The following skills must be discoverable by name:
boring-video
develop-topic
to-article
to-spec-beats
to-narration
to-scenes
to-storyboard
to-video
record-terminal
setup-boring-video-skillsSetup
- Inspect the available skills and compare them with the required suite above.
- Report missing or duplicate skill names. A grouped source path is valid: installation must expose each directory containing
SKILL.mdas a flat skill named by its frontmatter. If suite skills are missing, offer this complete install command. Run it only when the user asks you to install or repair the installation:
npx skills add sugarforever/boring-video-studio \ --skill setup-boring-video-skills boring-video develop-topic to-article to-spec-beats to-narration to-scenes to-storyboard to-video record-terminal- Confirm that the
hyperframesskill is available, then runnpx hyperframes doctor. HyperFrames owns production and is a hard dependency for the later stages. - Report optional voice support separately. ListenHub is needed only when the user chooses that voice branch.
Setup is complete only when all required suite names are discoverable, HyperFrames is discoverable, and npx hyperframes doctor passes. Preserve the diagnostic output when a check fails and give the smallest corrective action; do not claim readiness from file presence alone.
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.