DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run a paced batch of social Reel B-rolls with Get Brolls

Queue several Reels, pull the next item at a set pace and close each one when done.

  • Content
  • Advanced
  • 2 hours
  • From the README
  • Any agent

Credentials. Instagram and some platform downloads can depend on your own browser session, so only run batches from accounts and sources you are entitled to use.

Who it is forA social media team producing many short videos in one session that needs to stay within a steady download rhythm.

The problemDownloading many clips at once from YouTube, TikTok or Instagram without pacing risks failed downloads and rate limits.

The outcomeA queue of Reel items that the skill advances one at a time, with status shown for each item.

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

  1. Run python3 scripts/gb.py doctor and confirm summary.missing is empty.
  2. Run python3 scripts/gb.py queue --action add ... for each Reel project to enqueue it. (inferred, check the README)
  3. Run python3 scripts/gb.py queue --action next ... to get the next item at the right pace, then python3 scripts/gb.py queue --action mark ... to close it. (inferred, check the README)
  4. Run python3 scripts/gb.py queue --action status ... to see the state of the batch. (inferred, check the README)
  5. For Instagram pairs, use instagram_pairs with --pace, --max-per-run and --continue-on-error as needed.

Prompt for your agent

Using the get-brolls repo, enqueue the Reel projects listed in <batch file> and process them one at a time with the queue command. Expected output: a queue status showing each item as done or failed. Verify that a failed item does not stop the rest of the batch when --continue-on-error is set.

Caveat. The README says access to each source depends on the URL and, when needed, your browser session, so some items in a batch may fail regardless of pacing.

Share: 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