agentleFS
gitethanwoogitethanwoo/video-editing/skills/find-broll/SKILL.md

find-broll

Skill4 starsChanged 4 months agoMITView on GitHub

Plan, source, vet, and precisely place B-roll for spoken video. Use when the user asks to find B-roll, source cutaways, add receipts or visual evidence over a talking head, illustrate a transcript, create an annotated B-roll plan, or time cutaways to exact spoken words. Handles official footage, product interfaces, public-page receipts, archival material, concept graphics, and user-curated cultural clips while preserving source provenance and final editorial approval.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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
  1. Distinctive:

    Read the whole transcript and state its thesis.

    line 30
  2. Distinctive:

    Treat plan approval as authorization for read-only research and downloading public candidates.

    line 42
  3. Distinctive:

    Receipts: use the authentic post, headline, study, pricing page, review, or metric.

    line 48
  4. Distinctive:

    People and entities: use the official or primary source and match the moment to the claim, not just the name.

    line 49
  5. Distinctive:

    Products and interfaces: prefer the user's own current recording, then the official current demonstration.

    line 50
  6. Distinctive:

    Concepts: create a restrained brand-consistent graphic, or use authoritative real footage when one exists.

    line 51
  7. Distinctive:

    Archival material: prefer canonical archives with explicit provenance and usage terms.

    line 52
  8. Distinctive:

    Cultural or reaction clips: use the user's curated library.

    line 53
  9. Distinctive:

    Write every approved choice to a project-local manifest before rendering.

    line 65
  10. Very specific:

    Use the adjacent video-editing workbench to render a low-resolution candidate first.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Find B-roll

Source cutaways that illustrate what the speaker means, not merely the nearest noun. Prefer a small number of accurate, authoritative assets over broad stock search or decorative coverage.

Set SKILL_DIR to the absolute directory containing this file. Use the adjacent analyze-video-editing skill when the source needs transcription or editorial analysis. Use the adjacent video-editing skill for compositing, audio preservation, rendering, review artifacts, and final validation.

Establish the contract

Inspect the real source before planning. Accept a transcript, a word-timestamp transcript, or local video/audio. If only media is supplied, transcribe once with word timestamps and preserve the raw output.

Capture only preferences that materially change sourcing:

  • delivery aspect ratio and duration;
  • desired coverage density and whether the hook is denser than the body;
  • allowed source types and any explicit bans;
  • whether clip audio is stripped or intentionally mixed;
  • source-credit preference;
  • existing brand tokens or Remotion project for concept graphics;
  • any user-owned library, channels, or must-include assets.

User overrides apply immediately for the rest of the run. Do not infer licensing permission, brand ownership, or consent from availability.

Plan before downloading

Read the whole transcript and state its thesis. Then create an annotated beat plan with:

  1. stable beat ID;
  2. exact narration and anchor word;
  3. one-sentence interpretation of what the line means;
  4. route: receipt, entity, product, concept, archival, or cultural;
  5. proposed source type and why it is authoritative;
  6. intended duration and output placement;
  7. status: planned, sourced, approved, placed, or dropped.

Walk the full palette before dropping a meaningful beat, but never pad. A correct empty space is better than a wrong cutaway. Read references/sourcing-and-routing.md when choosing routes or search strategies.

Treat plan approval as authorization for read-only research and downloading public candidates. Ask separately before paid acquisition, publishing, signing in with new credentials, or sending anything externally.

Source by authority

Cluster the approved beats by source so each page, channel, or film is fetched once. Search metadata first; download only likely winners.

  • Receipts: use the authentic post, headline, study, pricing page, review, or metric.
  • People and entities: use the official or primary source and match the moment to the claim, not just the name.
  • Products and interfaces: prefer the user's own current recording, then the official current demonstration.
  • Concepts: create a restrained brand-consistent graphic, or use authoritative real footage when one exists.
  • Archival material: prefer canonical archives with explicit provenance and usage terms.
  • Cultural or reaction clips: use the user's curated library; do not blind-pick memes.

Inspect real search and metadata payloads before writing parsers or choosing formats. Record the canonical URL, creator, title, publication date, capture/download time, rights or usage note, and exact source interval. Reject watermarks, synthetic stock presented as real, burned-in captions that conflict with the edit, stale product interfaces, and sources whose provenance cannot be explained.

The agent may select one best candidate for an objective route when the evidence is unambiguous. Present choices for subjective or taste-sensitive routes, and preserve the user's final selection in the manifest.

Place on meaning

Anchor a cutaway to the spoken word or phrase it illustrates, usually 0.2–0.5 seconds after the word begins. Never reveal the answer before the narration says it. Bias slightly late when timestamps are uncertain.

Keep source time and output time distinct. Strip external clip audio unless the edit explicitly calls for it. Use full-frame cover crop only when it preserves the subject; use a designed background for partial-frame or portrait material. Static receipts may remain still or use truly sub-pixel motion—never integer-stepped FFmpeg zoompan.

Write every approved choice to a project-local manifest before rendering. Read references/manifest-and-timing.md for the fields and timing checks.

Verify the render

Use the adjacent video-editing workbench to render a low-resolution candidate first. Generate:

  • a midpoint frame for every placed beat;
  • a strip around every B-roll entrance and exit;
  • a contact sheet covering the full sequence;
  • a technical validation report for the final deliverable.

Inspect the actual images. Confirm the source is the intended one, the cut lands after the anchor, the subject survives the crop, no flash of talking head appears between adjacent cutaways, captions and overlays remain readable, audio continuity is intact, and every approved beat appears exactly once.

Deliver the master with the B-roll manifest, source list, approval state, review artifacts, validation report, and checksum. Never redistribute unused source media.

Attribution

This workflow adapts the MIT-licensed B-Roll Finder methodology by Louise De Sadeleer. The implementation is integrated with this repository's existing analysis, rendering, and validation contracts; third-party media retains its own rights and terms.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.