/demo-producer
Universal demo video creator for skills, agents, plugins, tutorials, CLI commands, and code walkthroughs. Generates scripts, storyboards, VHS terminal recordings, and Remotion video compositions with task-tracked production phases. Use when producing video showcases, marketing
$ npx -y skills add yonatangross/orchestkit --skill demo-producer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/demo-producer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Universal demo video creator for skills, agents, plugins, tutorials, CLI commands, and code walkthroughs. Generates scripts, storyboards, VHS terminal recordings, and Remotion video compositions with task-tracked production phases. Use when producing video showcases, marketing
SKILL.md
demo-producer.SKILL.mdname: demo-producer
license: MIT
compatibility: "Claude Code 2.1.220+."
description: "Universal demo video creator for skills, agents, plugins, tutorials, CLI commands, and code walkthroughs. Generates scripts, storyboards, VHS terminal recordings, and Remotion video compositions with task-tracked production phases. Use when producing video showcases, marketing content, or terminal recordings."
argument-hint: "[topic-or-feature]"
user-invocable: false
allowed-tools: [AskUserQuestion, Bash, Read, Write, Edit, Grep, Glob, Agent, TaskCreate, TaskUpdate, PushNotification]
context: inherit
version: 1.1.0
author: OrchestKit
tags: [demo, video, marketing, vhs, remotion, terminal, showcase, tutorial]
targets:
- tool: "vhs"
version: ">=0.11.0"
- library: "remotion"
version: ">=4.0.448"
complexity: low
persuasion-type: collaborative
effort: low
model: haiku
metadata:
category: document-asset-creationDemo Producer
Universal demo video creation for any content type.
> **Tool versions (2026-Q2):** VHS >= 0.11, Remotion >= 4.0.448. VHS 0.11 added: > > - **`Wait` keyword** — supersedes `Sleep N` with a condition-based wait (`Wait "prompt>"` blocks until the given string appears). Use `Wait` over `Sleep` for any prompt that can appear at variable times. > - **`ScrollUp N` / `ScrollDown N`** — explicit scroll steps inside a recorded session; useful for demonstrating TUI apps and long `less`-style output. > > Keep existing `Sleep N` only for fixed visual pacing where no event is available.
Quick Start
/ork:demo-producer # Interactive mode - asks what to create
/ork:demo-producer skill explore # Create demo for a skill
/ork:demo-producer plugin ork # Create demo for a plugin
/ork:demo-producer tutorial "Building a REST API" # Custom tutorial
/ork:demo-producer --live 4 # Live preview via /ork:dev --live (4-hour public funnel)
--live mode (M127 #1565)
`--live N` is a thin wrapper around `/ork:dev --live N`: it boots the dev stack behind `portless --funnel` (publicly exposed via Tailscale Funnel), records an expiry of `N` hours into `.claude/state/live-demos.jsonl`, and prints a public URL plus `<iframe>` snippet for embedding in customer emails or docs pages.
/ork:demo-producer --live 4
# Internally runs:
/ork:dev --live 4
# → public URL: https://app.your-tailnet.ts.net
# iframe: <iframe src="..." />
# expires: 2026-05-03T20:00Z
`/ork:doctor` warns about live demos older than 24 hours so they don't sprawl. Tear down with `/ork:dev stop`. Tailscale CLI must be installed (only required behind `--live` — not for static demo recording modes).
CRITICAL: Task Management is MANDATORY (CC 2.1.16)
**BEFORE doing ANYTHING else, create tasks to track progress:**
# 1. Create main task IMMEDIATELY
TaskCreate(
subject="Demo Producer: {topic}",
description="Creating polished demo video for content showcase",
activeForm="Producing demo for {topic}"
)
# 2. Create subtasks for each production phase
TaskCreate(subject="Content analysis", activeForm="Analyzing content for demo")
TaskCreate(subject="Script & storyboard", activeForm="Generating script and storyboard")
TaskCreate(subject="Record & compose", activeForm="Recording terminal and composing video")
TaskCreate(subject="Final output", activeForm="Rendering final video outputs")
# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])
TaskUpdate(taskId="5", addBlockedBy=["4"])
# 4. Update status as you progress
TaskUpdate(taskId="2", status="in_progress") # When starting
TaskUpdate(taskId="2", status="completed") # When doneSupported Content Types
| Type | Source | Example | |------|--------|---------| | `skill` | skills/{name}/SKILL.md | `/ork:demo-producer skill commit` | | `agent` | agents/{name}.md | `/ork:demo-producer agent debug-investigator` | | `plugin` | plugins/{name}/plugin.json | `/ork:demo-producer plugin ork` | | `marketplace` | Marketplace install flow | `/ork:demo-producer marketplace ork` | | `tutorial` | Custom description | `/ork:demo-producer tutorial "Git workflow"` | | `cli` | Any CLI tool | `/ork:demo-producer cli "npm create vite"` | | `code` | Code walkthrough | `/ork:demo-producer code src/api/auth.ts` |
Interactive Flow
When invoked without arguments, asks 4 questions:
Question 1: Content Type
What type of demo do you want to create?
○ Skill - OrchestKit skill showcase
○ Agent - AI agent demonstration
○ Plugin - Plugin installation/features
○ Tutorial - Custom coding tutorial
○ CLI Tool - Command-line tool demo
○ Code Walkthrough - Explain existing code
Question 2: Format
What format(s) do you need?
☑ Horizontal (16:9) - YouTube, Twitter
☑ Vertical (9:16) - TikTok, Reels, Shorts
☐ Square (1:1) - Instagram, LinkedIn
Question 3: Style
What style fits your content?
○ Quick Demo (6-10s) - Fast showcase, single feature
○ Standard Demo (15-25s) - Full workflow, multiple steps
○ Tutorial (30-60s) - Detailed explanation, code examples
○ Cinematic (60s+) - Story-driven, high polish
○ Scrapbook (15-35s) - Warm paper, fast cuts, social proof collage (Anthropic style)
Question 4: Audio
Audio preferences?
○ Music Only - Subtle ambient background
○ Music + SFX - Background + success sounds
○ Silent - No audio
Pipeline Architecture
> Load details: `Read("${CLAUDE_SKILL_DIR}/references/demo-pipeline.md")` for the full pipeline diagram, generation commands, and output structure.
Content Detector -> Content Analyzer -> Script Generator -> Terminal Script -> VHS Recorder -> Remotion Composer -> Final Outputs (horizontal/vertical/square).
Template System
Four template architectures for different demo styles. Load `Read("${CLAUDE_SKILL_DIR}/references/template-system.md")` for detailed configuration and the SkillDemoConfig interface.
| Template | Use Case | Duration | Key Featu
Read more
name: demo-producer
license: MIT
compatibility: "Claude Code 2.1.220+."
description: "Universal demo video creator for skills, agents, plugins, tutorials, CLI commands, and code walkthroughs. Generates scripts, storyboards, VHS terminal recordings, and Remotion video compositions with task-tracked production phases. Use when producing video showcases, marketing content, or terminal recordings."
argument-hint: "[topic-or-feature]"
user-invocable: false
allowed-tools: [AskUserQuestion, Bash, Read, Write, Edit, Grep, Glob, Agent, TaskCreate, TaskUpdate, PushNotification]
context: inherit
version: 1.1.0
author: OrchestKit
tags: [demo, video, marketing, vhs, remotion, terminal, showcase, tutorial]
targets:
- tool: "vhs"
version: ">=0.11.0"
- library: "remotion"
version: ">=4.0.448"
complexity: low
persuasion-type: collaborative
effort: low
model: haiku
metadata:
category: document-asset-creationDemo Producer
Universal demo video creation for any content type.
> **Tool versions (2026-Q2):** VHS >= 0.11, Remotion >= 4.0.448. VHS 0.11 added: > > - **`Wait` keyword** — supersedes `Sleep N` with a condition-based wait (`Wait "prompt>"` blocks until the given string appears). Use `Wait` over `Sleep` for any prompt that can appear at variable times. > - **`ScrollUp N` / `ScrollDown N`** — explicit scroll steps inside a recorded session; useful for demonstrating TUI apps and long `less`-style output. > > Keep existing `Sleep N` only for fixed visual pacing where no event is available.
Quick Start
/ork:demo-producer # Interactive mode - asks what to create /ork:demo-producer skill explore # Create demo for a skill /ork:demo-producer plugin ork # Create demo for a plugin /ork:demo-producer tutorial "Building a REST API" # Custom tutorial /ork:demo-producer --live 4 # Live preview via /ork:dev --live (4-hour public funnel)
--live mode (M127 #1565)
`--live N` is a thin wrapper around `/ork:dev --live N`: it boots the dev stack behind `portless --funnel` (publicly exposed via Tailscale Funnel), records an expiry of `N` hours into `.claude/state/live-demos.jsonl`, and prints a public URL plus `<iframe>` snippet for embedding in customer emails or docs pages.
/ork:demo-producer --live 4 # Internally runs: /ork:dev --live 4 # → public URL: https://app.your-tailnet.ts.net # iframe: <iframe src="..." /> # expires: 2026-05-03T20:00Z
`/ork:doctor` warns about live demos older than 24 hours so they don't sprawl. Tear down with `/ork:dev stop`. Tailscale CLI must be installed (only required behind `--live` — not for static demo recording modes).
CRITICAL: Task Management is MANDATORY (CC 2.1.16)
**BEFORE doing ANYTHING else, create tasks to track progress:**
# 1. Create main task IMMEDIATELY
TaskCreate(
subject="Demo Producer: {topic}",
description="Creating polished demo video for content showcase",
activeForm="Producing demo for {topic}"
)
# 2. Create subtasks for each production phase
TaskCreate(subject="Content analysis", activeForm="Analyzing content for demo")
TaskCreate(subject="Script & storyboard", activeForm="Generating script and storyboard")
TaskCreate(subject="Record & compose", activeForm="Recording terminal and composing video")
TaskCreate(subject="Final output", activeForm="Rendering final video outputs")
# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])
TaskUpdate(taskId="5", addBlockedBy=["4"])
# 4. Update status as you progress
TaskUpdate(taskId="2", status="in_progress") # When starting
TaskUpdate(taskId="2", status="completed") # When doneSupported Content Types
| Type | Source | Example | |------|--------|---------| | `skill` | skills/{name}/SKILL.md | `/ork:demo-producer skill commit` | | `agent` | agents/{name}.md | `/ork:demo-producer agent debug-investigator` | | `plugin` | plugins/{name}/plugin.json | `/ork:demo-producer plugin ork` | | `marketplace` | Marketplace install flow | `/ork:demo-producer marketplace ork` | | `tutorial` | Custom description | `/ork:demo-producer tutorial "Git workflow"` | | `cli` | Any CLI tool | `/ork:demo-producer cli "npm create vite"` | | `code` | Code walkthrough | `/ork:demo-producer code src/api/auth.ts` |
Interactive Flow
When invoked without arguments, asks 4 questions:
Question 1: Content Type
What type of demo do you want to create? ○ Skill - OrchestKit skill showcase ○ Agent - AI agent demonstration ○ Plugin - Plugin installation/features ○ Tutorial - Custom coding tutorial ○ CLI Tool - Command-line tool demo ○ Code Walkthrough - Explain existing code
Question 2: Format
What format(s) do you need? ☑ Horizontal (16:9) - YouTube, Twitter ☑ Vertical (9:16) - TikTok, Reels, Shorts ☐ Square (1:1) - Instagram, LinkedIn
Question 3: Style
What style fits your content? ○ Quick Demo (6-10s) - Fast showcase, single feature ○ Standard Demo (15-25s) - Full workflow, multiple steps ○ Tutorial (30-60s) - Detailed explanation, code examples ○ Cinematic (60s+) - Story-driven, high polish ○ Scrapbook (15-35s) - Warm paper, fast cuts, social proof collage (Anthropic style)
Question 4: Audio
Audio preferences? ○ Music Only - Subtle ambient background ○ Music + SFX - Background + success sounds ○ Silent - No audio
Pipeline Architecture
> Load details: `Read("${CLAUDE_SKILL_DIR}/references/demo-pipeline.md")` for the full pipeline diagram, generation commands, and output structure.
Content Detector -> Content Analyzer -> Script Generator -> Terminal Script -> VHS Recorder -> Remotion Composer -> Final Outputs (horizontal/vertical/square).
Template System
Four template architectures for different demo styles. Load `Read("${CLAUDE_SKILL_DIR}/references/template-system.md")` for detailed configuration and the SkillDemoConfig interface.
| Template | Use Case | Duration | Key Featu
Showing the first part of this file.
The Complete AI Development Toolkit for Claude Code — 114 skills, 37 agents, 212 hooks. Production-ready patterns for full-stack development.
Repo: yonatangross/orchestkit
Other skills on orchestkit.
- /accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy, and user preference honoring. Use when implementing screen reader support, keyboard navigation, ARIA patterns, focus
Open skill - /agent-orchestration
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
Open skill - /ai-ui-generation
AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system
Open skill - /analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when
Open skill - /animation-motion-design
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
Open skill - /api-design
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs. Use when specifying the wire contract an endpoint exposes, choosing a versioning scheme, or
Open skill

