by Leonxlnx
Cinematic launch films and motion design from code, directed by your coding agent.
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM lists this project for discovery and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
# Add to your Claude Code skills
git clone https://github.com/Leonxlnx/cineticGuides for using ai agents skills like cinetic.
Last scanned: 10/6/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-10-06T11:02:36.911Z",
"npmAuditRan": true,
"pipAuditRan": true,
"promptInjectionRan": true
}See how cinetic compares with popular alternatives.
cinetic (cinema + kinetic) is an agent skill that makes your coding agent direct a short film instead of arranging animation components. It is built for the two films a product team makes most: the launch film and the update video ("v2 is out", with the three things that changed).
copy-check.py reads it the way a stranger would and fails vague words, slogans and keyword piles.new-film.sh --template lays down a whole film's structure: an update video, a UI walkthrough, a capability reel, a camera teaser, a prompt run, a social ad or a type explainer. For a film whose idea is its own device, the agent is dealt an art direction instead.logos.mjs fetches the official colour marks of a product's integrations, sources and models from open collections and records source, licence and trademark owner. The kit sets them as app-icon tiles, chips, marks inside a line, walls and rings. Generic glyphs are Phosphor Icons.font-match.mjs picks the free face closest to a brand face that cannot ship.brand.py writes it into the film. Without one, it designs a brand from three personality words. A clip you supply can lend the film its grammar, never its content.It builds with Remotion (React) by default, or HyperFrames (HTML and GSAP).
Quick start · Examples · Start a film · Install · Requirements · Use · How it works · Sound · Look · What's inside · Evaluation
npx skills add Leonxlnx/cinetic
Then ask your agent for a film, for example: "Make a 25-second launch film with music for our database branching tool. Invent the brand." It works with Claude Code, Codex, Cursor and the other agents the skills CLI supports.
Before the first film, check your machine with a first test render. It needs Node 22+, ffmpeg 6+, Python 3.11+ and a headless Chromium, plus earshot 0.4 for the sound; see Requirements.
Every film here was made by an agent with cinetic 1.5 from a one-paragraph brief and cut to a licensed music track. The brands are invented unless the brief supplied one. Clicking a GIF downloads its MP4. The films live on the repo's media branch, so installs stay small.
The agent scaffolds the project itself at intake. These are the commands it runs, and you can run them too (<skill> is where the skill is installed, for example ~/.claude/skills/cinetic):
# a launch film from the starter, for an idea that is its own device
bash <skill>/scripts/new-film.sh films/acme --fps 60 --size 1920x1080
# a film template laid over the starter
bash <skill>/scripts/new-film.sh films/acme-walk --template ui-walkthrough
# an update video in a supplied brand, cut to a track found with music.mjs
bash <skill>/scripts/new-film.sh films/acme-2 --template update --brand ./brand \
--music ./audio/track.mp3 --record ./audio/track.licence.json
new-film.sh copies the starter (and the template), sets the grid, copies every cinetic script into the project so it runs on its own, and installs its dependencies. Other flags: --type calm|bold (the type family), --like <clip> (a clip's grammar), --pace crisp, --engine hyperframes, --font <name> and --link-modules <dir>; --format update is the same as --template update. new-film.sh --help lists them all.
| Template | Length | Use it when |
|---|---|---|
| none (the starter) | 15–45 s | a launch film whose idea is its own device: most films |
update |
15–23 s | "vX is out": 2–4 changes to show, each as a product moment |
ui-walkthrough |
25–40 s | the product's flow is the story: an input goes in, the product does visible work, an output comes out |
capability-reel |
15–25 s | the product's breadth is the story (sources, formats, integrations), or a launch film needs its close |
camera-teaser |
20–25 s | a dark, fast teaser of the product's screens where the camera does the moving |
prompt-run |
18–20 s | the product does work from a request (an agent, an assistant, a generator) and returns it done |
social-ad |
15 s | a short ad for a feed, cut on the product's own pictures |
type-explainer |
20–30 s | the idea is simple to say and the words carry it, on a white page with little product UI |
The test is to say the film in one sentence. "You give it X and get Y" is a walkthrough; "it works with everything and returns anything" is a reel; "here is what changed" is an update; "ask it, it does the steps, here is the result" is a prompt run. When none fits, start from the starter.
A template is the floor, never the film. It carries the structure, shot types, timing, transitions and choreography; the product, the words, the brand and the direction are yours. Its pace, tempo and type family become the film's defaults. Every string on screen comes from one content file whose placeholder marker fails the lint until the product's own words and data are in, and a fresh scaffold passes tsc, grid-check and lint-film with only those markers left. Its acts sit on whole bars, so once the track is in, every act line lands on a downbeat. Templates are for Remotion. Details: references/templates.md.
A film from the starter is dealt, not left to the agent's habits.
The direction deck. In Step 1 the agent runs
python3 scripts/deck.py --brief "a docs map for scattered teams" --format launch --pace calm --options 3
and gets three complete directions from 35, each fitted to the format: its space, light, camera language, cut grammar, type behaviour, story shape, lockup, palette proportions and one signature shot, and for an update film its hook, change and payoff beats. Type-led and graphic directions come up most; the 9 imagery-led ones are dealt only when the film has the product's own photographs or footage (--have photos or --have footage). The agent writes an idea sentence for each, keeps the one a competitor could not claim, and deals the full sheet for it, which becomes the art directi
cinetic is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Leonxlnx. Cinematic launch films and motion design from code, directed by your coding agent. It has 1,287 GitHub stars.
Yes. cinetic passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/Leonxlnx/cinetic" and add it to your Claude Code skills directory (see the Installation section above).
cinetic is primarily written in TypeScript. It is open-source under Leonxlnx on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh cinetic against similar tools.
No comments yet. Be the first to share your thoughts!