Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

skill-video-studio Skill

Repository ↗

by aaitor★ 3971 skills

Install

What it does

Claude Code skill for product videos: real browser capture, branded composition, and local mastering.

  • Connects Instruction files the AI reads
  • Account or key Not confirmed yet (README not read yet)
  • Category Coding
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/aaitor-skill-video-studio.svg)](https://mcp.popnx.com/en/skills/aaitor-skill-video-studio)

Use together with

MCP servers that connect the AI to services for the same work

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

by morlutoWidely used↓ 388.7K/wk★ 464.1KUpdated 6 days ago

MCP · Connects a serviceRuns on your computer

Fallow

Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.

by fallow-rsWidely used↓ 2.4M/wk★ 5.4KUpdated yesterday

MCP · Connects a serviceRuns on your computer

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 740.3K/wk★ 10.3KUpdated 6 days ago

MCP · Connects a serviceRuns on your computer

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
skill-video-studio
reaandrej-karpathy-skillsgraphifyMoneyPrinterTurbo
Makeraaitormorlutomultica-aiGraphify-Labsharry0703
Skills11111
GitHub stars397465,460233,910149,364144,149
Last code changeNov 5, 2026Nov 17, 2026Apr 20, 2026Nov 17, 2026Nov 17, 2026
LicenseMITMIT–Apache-2.0MIT

1 skills (instruction sets) by aaitor that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude Code

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account aaitor (person), 14 years old

  • Use and upkeep

    ★ 397 stars, few users so far · code last changed Nov 5, 2026

  • Any scripts?

    17 scripts that can run on a computer: scripts/avatar.sh, scripts/brand-extract.sh, scripts/capture-terminal.sh, scripts/capture.sh and 13 more

  • Uses the internet?

    Scripts that go online: scripts/tts.sh, scripts/capture-terminal.sh

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 6241305 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (296). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /devrel-video or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Claude Code, then type /devrel-video or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the devrel-video folder at ~/.agents/skills/devrel-video

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick devrel-video

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    Checking the commands · copy buttons appear once they pass

  3. In Cursor’s Agent chat, type / and pick devrel-video

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

The AI install prompt is hidden · the destination does not match the app’s official docs · Commands hidden because they did not pass our check · install from the maker’s GitHub page instead

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: devrel-video
description: Produce a silent DevRel-style product walkthrough video from a web URL. Playwright records the live flow, HyperFrames composes title/frame/chapters/CTA, FFmpeg masters. Use when asked to record, make, or update a product demo, feature walkthrough, catalog tour, or promo video from a web product.
---

# DevRel Video Studio — `/devrel-video`

A **thin orchestrator**. It does not reimplement capture or composition — it drives:

- **playwright-cli** (`page.screencast`) for live interaction capture,
- **HyperFrames** for composition + deterministic MP4 render,
- **FFmpeg / ffprobe** for convert, master, and QA.

Read `references/production-notes.md` first for environment gotchas (sandbox flags, `init` flags, CDN vendoring, determinism) and the production steps for **music, narration, avatar, subtitles, and multi-environment (terminal ⇄ browser)** (all supported — steps 5.4–5.8; the template and manifest carry seams for each).

For studio installation and prerequisites, see the repository-root `docs/installation.md`. The quick repository demo in `examples/README.md` demonstrates intake only; use the production workflow below for actual videos.

## When to use

- "record / make / produce a walkthrough, demo, catalog tour, or promo of `<web product / URL>`"
- "update / re-render an existing devrel-video project"

## Inputs — gather, never guess

- **URL** (+ start command if the product is local).
- **Flow**: the 2–4 beats to show (e.g. browse → filter → open a detail).
- **Brand**: reuse `brands/<name>/`, or extract from the URL (step 3).
- **Output**: format(s) + duration target. Default: **silent 16:9, ~25–40 s**.
- **Environments (optional)** — a demo can switch between the **browser** and **Claude Code (terminal)**. Name the order in the prompt ("prompt in Claude Code → the catalog in the browser → back to Claude Code") → `environments:` in `brief.yaml`. Terminal beats are captured with VHS (step 5.8); a pure-browser video is the default.
- **Audio / avatar (optional, all prompt-selectable)** — set any of these straight from the prompt, and write them into `brief.yaml`:
  - **voice**: the narration voice — male `leo`/`dan`/`zac`, female `leah`/`tara`/`jess`/`mia`/`zoe` (**match the presenter**; offer samples if unsure). "…narrated with voice `dan`" → `narration: dan`. Regenerating with a different voice makes a new variant (see 5.4).
  - **music** on/off, **subtitles** languages, **avatar** at intro/CTA (+ its private `avatar_plate` path).
- **Approved claims**: numbers/names allowed on screen — pull from the captured page, never invent (guide §7/§8).

## Workflow

### 1 · Intake → `projects/<slug>/brief.yaml`
Copy `templates/brief.example.yaml`. Confirm the audience, the one message, the CTA, and the beats.

### 2 · Explore (before recording)
Open the URL headless; snapshot + screenshot. Confirm: no login wall, **no PII / keys / wallets on screen**, and stable selectors for each beat. Prefer exact `a[href="…"]` and `getByRole` locators; always add a fallback selector so one missing element can't abort the capture.

### 3 · Brand → `brands/<name>/`
`scripts/brand-extract.sh <url> <name>` → `tokens.json` (real palette + fonts) + `logo.svg`. Use these in the composition. **Never invent a palette.** Reuse an existing `brands/<name>/` if you already have one for the product (`brands/acme/` is the default placeholder brand).

### 4 · Capture → `projects/<slug>/capture.mp4`
Copy `templates/hero-script.js` → `capture.js`; edit the beats (eased `scrollTo`, real locators, deliberate pauses, **all-forward navigation** so `page.screencast` survives route changes). Then:
`scripts/capture.sh projects/<slug>/capture.js "<start-url>"` → records `capture.webm`, converts to `capture.mp4`. Contact-sheet it; re-record on layout shift, PII, or a mis-click.

### 5 · Compose → `projects/<slug>/index.html`
Copy `templates/composition.html` to `projects/<slug>/index.html` and fill it from the brief + tokens (skip `hyperframes init`: it refuses a folder that already holds the capture, and the render only needs `index.html`):
title card (real claims) → footage in a browser frame → chapter lower-thirds synced to the capture beats (+ the title-card offset) → CTA. Give **every animated element a stable `id`** (GSAP and lint both require it).

### 5.4 · Narration (optional — drives the timeline)
For a narrated cut the **voice sets the timing.** Write ~1 line per beat (clean text: no parens/version numbers, em-dash → comma). Synth each with Orpheus in a **voice that matches the presenter** — male `leo`/`dan`/`zac`, female `leah`/`tara`/`jess`/`mia`/`zoe` (offer samples if unsure): `scripts/tts.sh "<line>" vo1.wav <voice>` (set `ORPHEUS_URL`/`ORPHEUS_KEY` — see `scripts/_env.sh`; reference TTS is `orpheus-tts`). Then adapt `projects/<slug>/narrate.py` (copy the template — footage length, beat times, `SPOKEN` lines, captions) — it measures the lines, computes scene/chapter times, and writes `voice.wav`, re-timed `captions.<lang>.srt`, and **`timing.json`**. Apply that timing to the composition with **`scripts/retime.py projects/<slug>`** (idempotent — rewrites every `data-start`/`data-duration` + GSAP position by id, so total tracks the voice), then mix (next step), render. **Swapping the voice later is one command:** `scripts/variant.sh projects/<slug> <voice>` runs the whole chain — re-TTS → narrate → retime → mix → re-lip-sync the avatar bubbles (if any) → render → `renders/out-<voice>.mp4` (add `--no-avatar` to skip the GPU step). `narrated-devrel` mode.

### 5.5 · Music (optional)
Local, license-clean bed — no auth, no model:
`python3 .claude/skills/devrel-video/scripts/gen-bgm.py bed.wav && ffmpeg -i bed.wav -b:a 192k projects/<slug>/bgm.mp3`,
then add the `<audio id="bgm" class="clip" src="bgm.mp3" … data-track-index="9" data-volume="0.85">` seam to the
composition (lower the volume under narration). For a produced track: `/media-use resolve --type bgm`
(HeyGen catalog — needs `heygen` sign-in) or `--local-only` (MusicGen), dropped into the same seam. **With narration**, don't stack two audio clips — pre-mix: `scripts/mix-audio.sh bgm.wav voice.wav narration-mix.mp3` ducks the bed under the voice and masters to −16 LUFS; use that one file in the seam at `data-volume="1"`.

### 5.6 · Subtitles (optional)
Author caption cues timed to the beats → `projects/<slug>/captions.<lang>.srt` — soft, toggleable, platform-standard; **one file per language** covers "alternative subtitles". Ship the `.srt` next to the video (YouTube/LinkedIn read it). For autoplay-muted social, burn a hard cut: `scripts/subtitles.sh projects/<slug> captions.en.srt`. When narration exists, derive the cues from its transcript (WhisperX via `/media-use`) instead of authoring.

### 5.7 · Avatar (optional — face-only presenter)
A **face-only circular bubble**, lip-synced, shown ONLY at intro / one transition / CTA (product stays the hero — a full-time presenter reads as a webinar). Depends on narration. Trim the exact line the mouth should say from `narration-mix.mp3` so lips match what's heard: `ffmpeg -ss <t0> -to <t1> -i projects/<slug>/narration-mix.mp3 -ar 16000 -ac 1 line.wav`. Then `scripts/avatar.sh <plate> line.wav projects/<slug>/avatar-face.mp4` — runs **LatentSync (256) on your own GPU host over SSH** (set `AVATAR_HOST`/`LS_DIR` — see `scripts/_env.sh`; reference is an AMD ROCm box), lip-syncs, then **pins the face** (per-frame face-tracking via `track_crop.py` — follows the face every frame at constant size, so the head stays put in the small circle instead of drifting; vidstab alone can't fix a *moving subject*). Add a `<video class="clip face-bubble" src="…" data-start data-duration data-track-index="11">` element with a shared `.face-bubble` CSS class (`border-radius:50%` = the circle) + a GSAP pop-in / fade-out over that window (`data-duration` = the line's length). **For a bubble at more than one moment** (e.g. intro *and* CTA), run avatar.sh once per line and

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
397
Maker
aaitor
License
MIT
Last code change
Nov 5, 2026
SKILL.md files in the repo (including translated copies and templates)
1
Topics
agent-skills, agents, claude-code, devrel, ffmpeg, harness, playwright, video