
Docs Demo
- 1.8k installs
- 55.5k repo stars
- Updated August 4, 2026
- remotion-dev/remotion
docs-demo is an agent skill that add an interactive demo to the remotion documentation. use when creating a new <demo> component for docs pages.
About
docs-demo is an agent skill from remotion-dev/remotion that add an interactive demo to the remotion documentation. use when creating a new <demo> component for docs pages. # Adding an Interactive Demo to Docs Interactive demos render a Remotion composition inline in documentation pages using `@remotion/player`. They live in `packages/docs/components/demos/`. Effect demos are separate: use `<EffectsDemo type="effects-..." />` and register them in `packages/docs/components/effects-demos/registry.ts` with the real eff Developers invoke docs-demo during build/frontend work for generative media tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments.
- Adding an Interactive Demo to Docs
- Interactive demos render a Remotion composition inline in documentation pages using `@remotion/player`. They live in `pa
- 2. **Register the demo** in `packages/docs/components/demos/types.ts`:
- Export a `DemoType` object with these fields:
- `id`: unique string used in `<Demo type="..." />`
Docs Demo by the numbers
- 1,768 all-time installs (skills.sh)
- +100 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Ranked #175 of 1,335 Generative Media skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
docs-demo capabilities & compatibility
- Capabilities
- adding an interactive demo to docs · interactive demos render a remotion composition · 2. **register the demo** in `packages/docs/compo · export a `demotype` object with these fields: · `id`: unique string used in `<demo type="..." />
- Use cases
- orchestration
What docs-demo says it does
Interactive demos render a Remotion composition inline in documentation pages using `@remotion/player`. They live in `packages/docs/components/demos/`.
1. **Create a component** in `packages/docs/components/demos/` (e.g. `MyDemo.tsx`). It should be a standard React component using Remotion hooks like `useCurrentFrame()` and `useVideoConfig()`.
2. **Register the demo** in `packages/docs/components/demos/types.ts`:
npx skills add https://github.com/remotion-dev/remotion --skill docs-demoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.8k |
|---|---|
| repo stars | ★ 55.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 4, 2026 |
| Repository | remotion-dev/remotion ↗ |
What it does
Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
Who is it for?
Developers working on generative media during build tasks.
Skip if: Tasks outside Generative Media scope described in SKILL.md.
When should I use this skill?
Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
What you get
Completed generative media workflow aligned with SKILL.md steps.
- Demo.tsx in packages/docs/components/demos
- EffectsDemo registry entry when applicable
Files
Adding an Interactive Demo to Docs
Interactive demos render a Remotion composition inline in documentation pages using @remotion/player. They live in packages/docs/components/demos/.
Effect demos are separate: use <EffectsDemo type="effects-..." /> and register them in packages/docs/components/effects-demos/registry.ts with the real effect schema, not the generic <Demo> options array.
Steps
1. Create a component in packages/docs/components/demos/ (e.g. MyDemo.tsx). It should be a standard React component using Remotion hooks like useCurrentFrame() and useVideoConfig().
2. Register the demo in packages/docs/components/demos/types.ts:
- Import the component
- Export a
DemoTypeobject with these fields: id: unique string used in<Demo type="..." />comp: the React componentcompWidth/compHeight: canvas dimensions (e.g. 1280x720)fps: frame rate (typically 30)durationInFrames: animation lengthautoPlay: whether it plays automaticallyoptions: array of interactive controls (can be empty[])
3. Add to the demos array in packages/docs/components/demos/index.tsx:
- Import the demo constant from
./types - Add it to the
demosarray
4. Use in MDX with <Demo type="your-id" />
Options
Options add interactive controls below the player. Each option needs name and optional ('no', 'default-enabled', or 'default-disabled').
Supported types:
type: 'numeric'— slider withmin,max,step,defaulttype: 'boolean'— checkbox withdefaulttype: 'enum'— dropdown withvaluesarray anddefaulttype: 'string'— text input withdefault
Option values are passed to the component as inputProps. Access them as regular React props.
Example registration
export const myDemo: DemoType = {
comp: MyDemoComp,
compHeight: 720,
compWidth: 1280,
durationInFrames: 150,
fps: 30,
id: 'my-demo',
autoPlay: true,
options: [],
};Related skills
How it compares
Use docs-demo for Remotion's internal docs Demo pattern; use a general React docs skill for non-Remotion component playgrounds.
FAQ
What does docs-demo do?
Add an interactive demo to the Remotion documentation. Use when creating a new <Demo> component for docs pages.
When should I use docs-demo?
During build frontend work for generative media.
Is docs-demo safe to install?
Review the Security Audits panel on this listing before production use.