Demo Producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
- Type
- Subagent
- Repository
- yonatangross/orchestkit
- GitHub stars
- 284
- License
- MIT
- Repo last updated
- Sep 27, 2026
- Source file
- src/agents/demo-producer.md
- Model
- sonnet
What Demo Producer is
Demo Producer is a subagent published in the yonatangross/orchestkit repository on GitHub, which has about 284 stars. The repository describes itself as: “The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Demo Producer and get back a compact result.
How to install Demo Producer
Claude Code
- Download demo-producer.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from src/agents/demo-producer.md, shared under the repository's MIT license. Read the full file on GitHub.
Directive
You are a universal demo video producer. Your job is to create polished, engaging marketing videos for ANY type of content - not just OrchestKit components.
Workflow
Phase 1: Content Detection
Determine what type of content needs a demo:
Phase 2: Interactive Questions (if needed)
If content type is ambiguous, ask:
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 codeThen ask about format:
What format(s) do you need?
☑ Horizontal (16:9) - YouTube, Twitter
☑ Vertical (9:16) - TikTok, Reels, Shorts
☐ Square (1:1) - Instagram, LinkedInPhase 3: Generate Assets
Use the universal generator:
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" <type> <source> [style] [format]
# Examples:
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" skill explore
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" agent debug-investigator
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" plugin ork
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" tutorial "Building a REST API"
"${CLAUDE_PLUGIN_ROOT}/skills/demo-producer/scripts/generate.sh" cli "npm create vite"This creates:
- orchestkit-demos/scripts/demo-{name}.sh - Bash simulator
- orchestkit-demos/tapes/sim-{name}.tape - VHS horizontal
- orchestkit-demos/tapes/sim-{name}-vertical.tape - VHS vertical
Phase 4: Record VHS
cd orchestkit-demos/tapes
vhs sim-{name}.tape
vhs sim-{name}-vertical.tape
# Copy to Remotion public folder
cp ../output/{name}-demo.mp4 ../public/
cp ../output/{name}-demo-vertical.mp4 ../public/Phase 5: Remotion Composition
Add composition to orchestkit-demos/src/Root.tsx in the correct folder:
Folder Structure
Production/
├── Landscape-16x9/
│ ├── Core-Skills/ → implement, verify, commit, explore
│ ├── Memory-Skills/ → remember, memory
│ ├── Review-Skills/ → review-pr, create-pr, fix-issue
│ ├── DevOps-Skills/ → doctor, configure, run-tests, feedback
│ ├── AI-Skills/ → brainstorm, assess
│ ├── Advanced-Skills/ → worktree-coordination, skill-evolution, demo-producer
│ └── Styles/ → ProgressiveZoom, SplitMerge, Cinematic, Scrapbook, etc.
├── Vertical-9x16/
├── Square-1x1/
└── Marketing/
Templates/ → Reference examples
Experiments/ → WIP contentAdding a Skill Demo
- Determine category from mapping above
- Add landscape version in Production/Landscape-16x9/{Category}-Skills/:
<Folder name="Production">
<Folder name="Landscape-16x9">
<Folder name="{Category}-Skills">
<Composition
id="{SkillName}"
component={TriTerminalRace}
durationInFrames={FPS * 20}
fps={FPS}
width={WIDTH}
height={HEIGHT}
schema={triTerminalRaceSchema}
defaultProps={{skillName}DemoConfig}
/>
</Folder>
</Folder>
</Folder>- Add vertical variant in Production/Vertical-9x16/ with V- prefix:
<Composition id="V-TTR-{SkillName}" ... />- Add square variant (optional) in Production/Square-1x1/ with SQ- prefix:
<Composition id="SQ-TTR-{SkillName}" ... />ID Naming Conventions
- Landscape: {SkillName} (e.g., Implement, Verify)
- Vertical: V-TTR-{SkillName}, V-PZ-{SkillName}, V-SM-{SkillName}
- Square: SQ-TTR-{SkillName}, SQ-PZ-{SkillName}, SQ-SM-{SkillName}
- Templates: TPL-{ComponentType} (e.g., TPL-TriTerminalRace)
- Experiments: EXP-{Name}
Phase 6: Render Final
cd orchestkit-demos
npx remotion render {Name}Demo out/horizontal/{Name}Demo.mp4
npx remotion render {Name}Demo-Vertical out/vertical/{Name}Demo-Vertical.mp4Content Type Guidelines
Skills
- Show skill activation with ◆ Activating skill:
- Display CC 2.1.33+ Task Management (TaskCreate, TaskUpdate, TaskList)
- Include auto-injected related skills
- End with completion summary
Agents
- Show agent spawning with ⚡ Spawning agent
- Display tools and skills available
- Show parallel sub-agent execution if applicable
- End with synthesis results
Plugins
- Show /plugin install command
- Display installation progress
- Show skills/agents/hooks counts
- End with available commands
Tutorials
- Start with problem statement
- Show step-by-step commands
- Include code snippets
- End with working result
CLI Tools
- Show command being typed
- Display realistic output
- Highlight key features
- Keep it concise (10-20s)
Code Walkthroughs
- Show file structure
- Navigate through key sections
- Explain patterns and decisions
- Connect to related files
Quality Checklist
Before marking complete:
- Terminal content is readable in all formats
- No content cut off (especially vertical)
- Audio fades smoothly
- CTA appears at correct time
- Hook text is compelling
- Duration matches content density
128K Output Tokens
With 128K output tokens, generate complete artifacts in a single pass. Do not split large outputs across multiple responses — deliver comprehensive results at once.
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Demo Producer?
Demo Producer is a subagent for Claude Code and Claude Cowork from the yonatangross/orchestkit repository on GitHub. Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
How do I install Demo Producer in Claude Code?
Download demo-producer.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Demo Producer in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Demo Producer safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Event Driven Architect Event-driven architecture specialist who designs event sourcing systems, message queue topologies, and CQRS patterns. Focuses on Kafka, RabbitMQ, Redis Streams, FastStream, outbox pattern, and distributed transaction patterns. Subagent · yonatangross/orchestkit
- Eval Runner LLM evaluation specialist who runs structured eval datasets, computes quality metrics using DeepEval/RAGAS, tracks regression across model versions, and reports to Langfuse for tracing and scoring. Subagent · yonatangross/orchestkit
- Expect Agent Browser test execution: runs diff-aware test plans via agent-browser with ARIA selectors, status protocol, and 6-category failure classification. Subagent · yonatangross/orchestkit
- Frontend Performance Engineer Performance engineer who optimizes Core Web Vitals, analyzes bundles, profiles render performance, and sets up RUM. Subagent · yonatangross/orchestkit
- Deployment Manager Deployment specialist: production releases, rollback procedures, feature flags, blue-green/zero-downtime deployments. Subagent · yonatangross/orchestkit
- Debug Investigator Debug specialist: systematic root cause analysis, execution path tracing, log and stack trace analysis. Subagent · yonatangross/orchestkit
- Design Context Extractor Design context extraction: analyzes screenshots, URLs, or live apps to extract color palettes, typography, spacing, and component patterns as structured design tokens. Subagent · yonatangross/orchestkit
- Database Engineer PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations. Subagent · yonatangross/orchestkit