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

How to let Claude Code build a deck from a brief with Awesome HTML Scrolline Deck

Install the repo as a Claude Code skill so an agent can go from a brief to a deck and an MP4.

  • Content
  • Advanced
  • 1 hour
  • From the README
  • Claude Code

Who it is forA developer or analyst who already uses Claude Code and wants the agent to draft the deck, run a smoke test and produce the video from a written brief.

The problemTurning a brief into a concept choice, a deck.yaml file, a test run and an export takes many manual steps that are easy to lose track of.

The outcomeA deck built from a brief, with an MP4 export, where the agent has followed the skill's steps from concept to smoke run.

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. git clone https://github.com/gongnyang/awesome-html-scrolline-deck.git
  2. cd awesome-html-scrolline-deck
  3. git checkout v2
  4. npm install
  5. ln -s "$PWD" ~/.claude/skills/scrolline-deck
  6. Ask Claude Code to use the scrolline-deck skill with your brief and the target deck name.

Prompt for your agent

Use the scrolline-deck skill in the awesome-html-scrolline-deck repo to turn <brief-file> into a deck named <deck-id>. Choose a concept, write decks/<deck-id>/deck.yaml, run `npm run deck -- plan <deck-id>`, then `npm run export -- <deck-id>`. Report the concept you chose and the path of the MP4, and verify that out/export/<deck-id>.mp4 exists.

Caveat. The README names the skill and its steps but does not say how the agent chooses between concepts, so review the chosen concept before you accept 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