broll-pick
Skill2 starsChanged 5 months agoNo licenceView on GitHub
Claude picks CONTEXTUAL/scene-level anchors from a clip transcript (literal objects, establishing shots, evocative concept footage matched to the story's tone — not just keyword nouns) and sources full-bleed B-roll cutaways via keyless yt-dlp YouTube search + mcptube frame-sampling + Claude vision verify. The verify step gets the spoken context and rejects literal-but-wrong matches (e.g. a cat laser toy for a tense "red dot" beat). Aims dense (8-12 windows, targeting cutaway footage on ~60%+ of the runtime; emits cutaway_coverage in the plan and WARNs below BROLL_MIN_COVER, default 0.6). Emits broll_plan.json with per-cutaway placement [t0,t1] and source metadata; clip files are namespaced per-clip. Windows snap to whole chunk-captions boundaries; vision calls capped by BROLL_VISION_CAP (default 16).
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analytics-feedbackSkill
- bg-musicSkill
- bookend-trimSkill
- brand-overlaysSkill
- broll-cleanupSkill
- broll-compositeSkill
- burn-subtitlesSkill
- chunk-captionsSkill
- cut-clipSkill
- cut-fillerSkill
- derive-thesisSkill
- director-passSkill
- end-cardSkill
- fill-verticalSkill
- first-span-feedbackSkill
- fix-cold-openSkill
- generate-titleSkill
- grade-clipSkill
- ingestSkill
- jump-cutSkill
- like-subscribe-overlaySkill
- loudnormSkill
- name-shortSkill
- pick-moodSkill
- pick-segmentsSkill
- profile-clipSkill
- qc-clipSkill
- reap-sourceSkill
- save-localSkill
- schedule-dripSkill
- scout-sourcesSkill
- segment-topicsSkill
- selection-reportSkill
- sfx-beatsSkill
- source-creditSkill
- sources-ledgerSkill
- speed-upSkill
- style-corpusSkill
- style-gateSkill
- switch-facesSkill
- tighten-paceSkill
- title-transitionSkill
- transcribeSkill
- trim-fillerSkill
- verify-bookendsSkill
- verify-coherenceSkill
- verify-completenessSkill
- visual-cadenceSkill
- watermarkSkill
- zoom-punchSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 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.
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.

