@remotion/skills: Add remotion-export-otio skill

[krishnachitanyapidugu-sys]

Related to #10235.

That issue asks for a way to hand a Remotion edit over to DaVinci Resolve or Premiere. This PR proposes the smallest useful step in that direction: an agent skill that teaches an agent to produce a valid OpenTimelineIO (.otio) file from a composition. No new package, no runtime code, no changes to shipped behaviour.

I went with a skill rather than an exporter because a Remotion composition is React code, so there is no deterministic mapping from a component tree to a timeline. Deciding which elements are clips, where they sit, and what has to be dropped is a judgement call, which is the kind of thing a skill handles better than an API. If you would rather see this as a real exporter in a package, say so and I will close this and work on that instead.

What is in the PR

• packages/skills/skills/remotion-export-otio/SKILL.md — the skill
• agents/openai.yaml and assets/remotion-icon.png, matching what every other public skill ships
• The registrations a new public skill requires: remotion-skill-names.ts, the npx skills update list in remotion-upgrade, a router entry in remotion-best-practices, and the docs page (packages/skills/README.md is generated from it)
• The symlinks created by bun run syncskills

What the skill does and does not claim

It maps <Video>, <OffthreadVideo> and <Audio> with a real src into OTIO clips, uses <Sequence from> for placement, trimBefore for the source in-point, and Gap.1 for everything with no media behind it.

It explicitly does not try to map text, captions, shapes, animations, effects or transitions. Those are React and have no media file, so no timeline format can carry them. The skill is written to leave them out and to tell the user exactly what it skipped, rather than pretend the export is lossless.

Testing

An exported timeline was imported into DaVinci Resolve and came in as expected.

The rest was validated against the reference implementation (OpenTimelineIO 0.18.1) rather than by eye:

• A composition with a title card, a trimmed video, captions and a music bed exports to a file that parses, round-trips through otio_json, and converts to FCP7 XML for the Premiere path
• otiostat: 2 tracks of equal length, 3 clips, 00:00:16:00, matching durationInFrames={480} at 30fps
• Every media reference resolves on disk, and every source_range fits inside the real file length as reported by ffprobe
• Conforming the timeline with ffmpeg reproduces the edit: the frame at timeline 5s matches the source at 6s at 52.7 dB PSNR, against 14.6 dB for a deliberately one-second-off control, which confirms trimBefore is honoured
• Four deliberately broken exports (ignored trimBefore, missing gap, missing available_range, captions emitted as clips) are each caught, so the passing result means something

Repo checks: bun run checkskills passes, the four skill-related test files in packages/cli pass (5 tests), the codex-plugin, claude-code-plugin and kimi-code-plugin test suites pass, and so do lint and formatting for the affected packages.

Two details the testing corrected in the skill text: the FCP XML adapter is no longer bundled with OpenTimelineIO and needs otio-fcp-adapter plus -O fcp_xml, and that converter fails on any media reference without an available_range, so the skill tells the agent to fill it in from npx remotion ffprobe.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview	Aug 16, 2026 4:30am
remotion	Ready	Preview	Aug 16, 2026 4:30am

[pullfrog]

Important

The new remotion-export-otio public skill is missing its agents/openai.yaml registration, which every other public skill ships. The @remotion/codex-plugin test skill display names match their slash commands reads agents/openai.yaml for every skill it packages, so the next build-and-test of the affected downstream packages will throw ENOENT on the missing file. The check list in the PR (checkskills + the four packages/cli tests) never exercises this path, which is why it slipped through.

Reviewed changes

• New public skill remotion-export-otio — packages/skills/skills/remotion-export-otio/SKILL.md (230 lines) teaches an agent to translate a composition's <Video>/<Audio>/<OffthreadVideo>/optional <Img> into a track-per-kind OpenTimelineIO (.otio) timeline: RationalTime/TimeRange idioms, Gap.1 insertion for non-media spans, trimBefore → source_range.start_time, and available_range filled from npx remotion ffprobe.
• Skill registration wiring — added remotion-export-otio to the (sorted) remotionSkillNames list in packages/studio-server, the npx skills update ... --yes list in remotion-upgrade, a router section + symlink in remotion-best-practices, and a # /remotion-export-otio entry in the docs skills.mdx plus the generated README.md.
• Agent symlinks — .agents/skills/remotion-export-otio → ../../packages/skills/skills/remotion-export-otio, surfaced through the .claude/skills directory link; the remotion-best-practices/remotion-export-otio router symlink is present too.

⚠️ Missing agents/openai.yaml for the new public skill

Every public skill under packages/skills/skills/ ships an agents/openai.yaml — remotion-export-otio is the only one without it. @remotion/codex-plugin's test script (bun build.mts && SKILLS_ROOT=... validate-links.ts && bun test test) copies every skill directory into its packaged output, and the skill display names match their slash commands test then readFileSyncs agents/openai.yaml for each directory, so the build-and-test of the affected downstream packages fails with ENOENT once this skill is included. The author stated checks (checkskills and the four packages/cli skill tests) don't cover this packaging path, so it will surface only in the plugin tests.

Technical details

# Add agents/openai.yaml to remotion-export-otio

## Affected sites
- packages/skills/skills/remotion-export-otio/agents/openai.yaml — missing (only the SKILL.md is added in this PR)
- packages/codex-plugin/test/plugin.test.ts:195-203 — `readFileSync(generatedSkillsRoot/skillName/agents/openai.yaml)` for every packaged top-level skill; throws ENOENT without the file

## Required outcome
- Add packages/skills/skills/remotion-export-otio/agents/openai.yaml so the packaged skill exposes an OpenAI agent interface and the codex-plugin test passes.
- Verify with the codex-plugin (and cursor-plugin) build + test, which the current check list omits.

## Suggested approach
Mirror the other skills exactly (see packages/skills/skills/remotion-render/agents/openai.yaml):

interface:
  display_name: '/remotion-export-otio'
  short_description: 'Export a Remotion composition as an OpenTimelineIO (OTIO) timeline for DaVinci Resolve or Premiere Pro'
  icon_small: './assets/remotion-icon.png'
  icon_large: './assets/remotion-icon.png'
  brand_color: '#0B84F3'
  default_prompt: '$remotion-export-otio: Export this composition for DaVinci Resolve'

The openai.yaml references ./assets/remotion-icon.png, which every other public skill also carries under <skill>/assets/ — the new skill currently contains only SKILL.md, so copy that icon in alongside.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using DeepSeek Flash (free via Pullfrog for OSS) ｜ 𝕏}