Credentials. Before fetching, you must record the usage conditions of the source yourself, since the skill only records what you state and where each file came from.
Who it is forA video editor who needs real footage of an event named in the script and has no API key set up.
The problemStock libraries show generic footage, and the editor needs the actual event with a record of where it came from.
The outcomeAn approved clip in brolls/clips/ with origin, author and decision recorded in brolls/credits.md.
What you need first
- Python 3.11+
- FFmpeg and ffprobe built with libfreetype (drawtext)
- Node 22+ with npm and npx
- curl and Git
- A project folder where the B-roll files will be kept
Steps
- Run
bash scripts/install.sh --check, thenbash scripts/install.sh, thenpython3 scripts/gb.py doctorin the installed skill folder. - Run
python3 scripts/gb.py search --provider nasa --query "Artemis launch" --limit 3 --intent literal --project /caminho/meu-video. - Run
python3 scripts/gb.py preview --candidate " " --start 0 --end 4 --project /caminho/meu-video, thenpython3 scripts/gb.py review --project /caminho/meu-video. - Run
python3 scripts/gb.py serve --background --project /caminho/meu-video, open the storyboard URL it returns, decide the clips and export the JSON. - Run
python3 scripts/gb.py import-review --by "Seu nome" --project /caminho/meu-video, thenpython3 scripts/gb.py permit --candidate " " --evidence "Condições de uso reais dessa fonte" --project /caminho/meu-video. - Run
python3 scripts/gb.py fetch --candidate " " --project /caminho/meu-videoandpython3 scripts/gb.py verify --project /caminho/meu-video.
Prompt for your agent
Using the get-brolls repo, search NASA for footage matching the line "<script line>" in project folder <project folder>, preview the top candidate, and wait for my approval before running fetch. Expected output: a verified clip in brolls/clips/ and an entry in brolls/credits.md. Verify that verify reports the count of approved clips.
Caveat. The README says the final delivery depends on your decision and on a recorded usage condition for each source, and that a change in the trim or context sends the clip back to review.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page