reelme

Turn your repo into launch videos for social platforms — rendered on your machine with Remotion. No accounts, no API keys, nothing uploaded.

reelme is the rendering engine behind the reelme agent skill. The skill does the thinking (it reads your repo, interviews you, and writes a reelme.json brief at your repo root); this CLI does the work: it scaffolds a Remotion project in a global cache and renders one video variant per publishing platform.

Install & use

No install needed:

npx reelme render

Run it in a repo that has a reelme.json. To create one, use the agent skill in Claude Code, Cursor, Gemini CLI, or any Agent Skills-compatible agent:

npx skills add RubenGlez/reelme

Commands

| Command | What it does | |---|---| | npx reelme render | Renders every platform selected in reelme.json to ./reelme-out/ | | npx reelme studio | Opens Remotion Studio against the cached project, for previewing and tweaking | | npx reelme validate | Checks reelme.json (schema, platforms, scene types and fields) without rendering | | npx reelme clean | Removes this project's cache (add --all to wipe every project's cache in ~/.reelme/cache) |

How it works

• Your repo keeps only two things: reelme.json (the brief — commit it, it's your video's source of truth across releases) and reelme-out/ (rendered videos; add it to .gitignore).
• The heavy Remotion project lives in ~/.reelme/cache/<project-hash>/, scaffolded on first render and reused afterwards. Re-renders don't reinstall anything; upgrading the CLI (or changing the template's dependencies) rebuilds the scaffold automatically.
• Each platform you select (X, LinkedIn, YouTube, TikTok, Instagram Reel/Story/Feed, GitHub README) maps to a preset that resolves dimensions, duration ceilings, and safe areas internally — you never deal with aspect ratios. GitHub README outputs a GIF; everything else is MP4. Briefs with a teaser cut also get a short <platform>-teaser.mp4 per social platform.

Requirements

• Node.js >= 18
• pnpm (used to install render dependencies inside the cache)

The first render needs network access: it installs the Remotion project into the cache (npm registry), downloads a headless Chrome build (hundreds of MB, once), and fetches the on-screen fonts from Google Fonts. After the first successful render most of this is cached, but font loading still runs per render — nothing you author is ever uploaded.

License

MIT