DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to add stock video to a deck beat with your own API key with Awesome HTML Scrolline Deck

Put Pexels or Pixabay footage into a beat that scrubs with scroll or plays in place.

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Any agent

Credentials. Store your Pexels or Pixabay API key only in the git-ignored .env file and never paste it into deck.yaml, a commit or an agent prompt.

Who it is forA presenter whose deck needs real footage for a launch or an industry story and who has a Pexels or Pixabay account.

The problemStock video needs its own key and file handling, and a key committed to git would leak.

The outcomeA deck beat of type video that scrubs with scroll or plays while active, with the key kept out of git.

What you need first

  • Node.js 22 or newer
  • git
  • ffmpeg, only if you cut frame sequences for scrubbed video
  • A Pexels or Pixabay API key in .env, only if you add stock video

Steps

  1. Create your own Pexels or Pixabay API key.
  2. Save the key in a .env file in the repo root. The README says .env is git-ignored.
  3. npm run frames to cut a frame sequence for a scrubbed beat (ffmpeg required).
  4. Set type: video and mode: scrub, or mode: play or loop, in the beat's deck.yaml entry.
  5. npm run check to confirm the key is not in tracked files.

Prompt for your agent

In the awesome-html-scrolline-deck repo, add a video beat to decks/<deck-id>/deck.yaml using <clip-file> and mode scrub. Confirm that the API key is stored only in .env. Run `npm run check` and report whether it passes.

Caveat. Stock footage is credited per deck in decks/<deck-id>/assets/CREDITS.md under the Pexels License, so keep that file with the deck.

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