⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

showtime

@faviovazquez⭐ 25 stars

Use when the user wants a video made, edited or finished: a launch or promo video, product demo, explainer, trailer or teaser, tutorial or walkthrough, a screen recording turned into a demo, social short, reel, TikTok or YouTube Short, photo slideshow, animated chart or data story, motion graphics or animation, an animated logo intro, outro or sting, lower thirds, an audiogram, music video; captions or subtitles for a video; a voice-over or narration; music or sound effects for a video; a video thumbnail or poster frame; footage edits such as cutting the ums, removing silences, tightening a talking head, podcast or interview clips; reframing to vertical; re-voicing or subtitling a video in another language; turning a repo, website, pull request or changelog into a video; or when they type /showtime. Not for editing still images, writing a caption for a photo post, or code unrelated to a video.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 25 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

https://github.com/user-attachments/assets/1132aa71-7fe5-4345-a925-790d80462fda

Quick start

1. Install the two prerequisites (details in Requirements): uv and Node.js 24 or 22 LTS (20 or newer works). Restart your coding agent afterwards so it sees them.

2. Add showtime to your agent. In Claude Code:

/plugin marketplace add FavioVazquez/showtime
/plugin install showtime@showtime

Using Codex, Cursor, Devin, OpenCode or another agent? Works with has the exact install for each, and npx skills add FavioVazquez/showtime covers any agent that supports Agent Skills.

3. Ask for a video:

Make a 20-second launch video for this repo, with a voice-over and upbeat music.

The first time, your agent checks what is missing, tells you the download size and time (about 0.6 to 0.8 GB into ~/.showtime, depending on your system, usually 2 to 6 minutes; nothing outside that folder changes) and runs setup once you say yes. Bigger pieces (the transcription model, Manim, music tracks) come the first time a video needs them, announced with their size. After that, a request in Claude Code looks like this:

Your agent states its assumptions in one line (it asks only when a request is genuinely open), shows you a first look (stills or a fast draft) before the full-quality render, then checks the result with showtime qa. Every request gets its own folder, showtime-out/<name>-<timestamp>/, with final.mp4, poster.jpg, share.txt, exports/ and work/. Nothing is ever overwritten.

[!TIP] Say "show me options first" (or "studio") and your agent opens a local board where you pick a concept, a look, a music bed and a storyboard before anything is built. Say "no crew" to keep the whole job in one session.

What's new in 0.3.0 (the full list is below):

  • A full review on every video, and quieter runs. Each finished video gets looks, qa and a critic round before delivery; say "lean" for a lighter pass. Commands print a short verdict and keep the detail in a file, references are read by the piece (showtime guide), and looks at frames go to a disposable reviewer, so less piles up in your agent's context.
  • Videos that differ from each other. A local look history warns when a video repeats a recent one, and showtime reference learns pace and type scale from a video you like, never its content.
  • Checks for what viewers complain about. A phone check (text you can read at phone size, held long enough), and pairwise review, where a new version ships only if the critic prefers it in both orders.
  • New kinds of video. Repo and paper explainers, release and PR videos (showtime release-video, and a GitHub Action), launches that start from your product's real brand, and showtime adopt for video code you already have.
  • A receipt for every job: your request as typed, the rounds, renders and time, and tokens and cost where your agent reports them.

In my blind vote in benchmark round 4, 0.3.0 in lean mode was preferred to 0.2.0 on 4 of 6 tasks and to plain Claude Code on 7 of 8; the full-review default came after that round and was not part of it.

Works with

showtime is a skill, a command line and an MCP server, so it runs in any coding agent that reads Agent Skills and can run shell commands. MCP adds typed tools on top, and the ten crew agents are an optional speed-up for hosts that have custom sub-agents.

Tested with. A real run passed: the agent installed showtime from this repository and made a 5-second test video ("make a 5-second test video that says hello", empty folder), ending in a `final.mp

// HOW IT'S BUILT

KEY FILES

skills/showtime/SKILL.mdREADME.md

// REPO STATS

25 stars