whiteboard-video-ideas
Skill2 starsChanged 51 days agoNo licenceView on GitHub
Produce new whiteboard YouTube video ideas for Zalo Kabche's channel in two stages. Stage 1 picks topics by the locked angle, a business tip first and then AI doing it (from his second brain, his demo data and the owner question research, skipping anything filmed or planned on Linear, so the channel is not only AI receptionist videos) and sends them as ONE Telegram text with Linear Idea cards. Stage 2, only for the ones he picks, writes beats.md, renders a gpt-image-2 board per pick on the photo of his real whiteboard, builds the filming plan PDF ("like last time"), sends it with the boards and moves the cards to Boards ready. Use when Zalo asks for more whiteboard video ideas, picks ideas to shoot, or wants the board or filming plan for a shoot. Not for editing footage (yt-video-edit), thumbnails (yt-thumbnail) or publishing (ship-yt-video).
- Reads credentials
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autopilot-collectSkill
- bu-cold-outreachSkill
- cf-crawlSkill
- commit-with-heredocSkill
- content-video-finishSkill
- create-skillSkill
- dailySkill
- dev-server-restartSkill
- digestSkill
- dub-videoSkill
- frontend-designSkill
- infographicsSkill
- live-test-campaignSkill
- machine-editorial-brollSkill
- repo-initSkill
- schema-snapshotSkill
- seedanceSkill
- seedance-video-prompt-builderSkill
- ship-to-prodSkill
- ship-yt-videoSkill
- telegramSkill
- tenant-triageSkill
- typecheck-and-buildSkill
- voice-agent-forgeSkill
- voice-call-triageSkill
- voice-test-stackSkill
- yt-thumbnailSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.