Point ReelMint at your project's README and get a script grounded in what the project actually does — then editable scenes: the install command as an animated terminal, the API example as a code card, the architecture as a diagram.

The README is already the script outline — ReelMint does the rest.
A Short that looks like your project, because it is your project.
Scripts draw on your knowledge base — README, API docs, past scripts — so the Short says what the repo actually says.
No stock footage of hands typing. Your install command animates in a terminal component; your usage example renders as a real code card.
Scenes stay editable. When the install flag changes or the API is renamed, edit the scene text and re-render — no re-recording.
Publish straight to YouTube or schedule the Short to go live with the release.
Claude Code or Cursor can drive the pipeline through ReelMint's MCP server — useful when a Short per release is the goal.
Bring your own Gemini, OpenAI, or ElevenLabs keys, encrypted at rest, billed by the provider. The pilot itself is free.
No. The README grounds the script; the AI writes a Short-length narrative from it — a hook, the problem, the install, the payoff — and you edit every line before scenes are made.
They become syntax-highlighted code card scenes, sized for a phone screen. Commands become typed terminal animations. Both stay editable afterwards.
No. Scenes are layered objects, not baked pixels. Update the command or snippet in the scene and re-render the reel.
ReelMint ships an MCP server, so an agent like Claude Code can script, compose, render, and publish with a scoped workspace token — you review the result on your channel.
The pilot is free with no credit card and no watermarks. AI usage runs on your own keys with zero markup.
Paste the README, edit the script, publish the Short — free during the pilot.
Start free — no credit card