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

How to generate scroll-page imagery and video with a KIE key with Scroll Craft

Add KIE_AI_API_KEY so the agent can generate scroll-page assets instead of using only your own media.

  • Content
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Credentials. The generation route needs a KIE_AI_API_KEY, so keep it in a local env file and never paste it into prompts or commit it.

Who it is forA studio that needs imagery or video for a scroll page and has no existing footage to use.

The problemSome scroll pages need hero visuals and camera-move footage that do not exist yet.

The outcomeGenerated assets for the page, produced through the skill's kie script, with the key kept out of source files.

What you need first

  • Node 18+
  • A full ffmpeg build (scroll-craft notes that some toolchains ship a stripped ffmpeg)
  • playwright-core and Chrome, installed with npm i playwright-core in the build folder
  • Your own photos or footage, or a KIE_AI_API_KEY if you want assets generated

Steps

  1. Copy .env.example to a local env file and add your KIE_AI_API_KEY there
  2. Run node plugins/nateherk-design/skills/scroll-craft/scripts/doctor.mjs to confirm the setup
  3. Run the generation script at scripts/kie.mjs with the asset prompts from your brief (inferred, check the README)
  4. Note that a ten-leg continuous-world flight is a real spend, and check the cost before running a long generation

Prompt for your agent

Using the scroll-craft skill in the nateherkai/scroll-craft repo, generate the hero assets for <target brand> using KIE_AI_API_KEY from the local env file. Expected output: generated image and video files for the page. Verify that the key is read from the environment and never written into HTML or committed files.

Caveat. The README says generated video is not free, so budget for spend before running a long continuous-world flight.

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