Agent skill · Media & Video

edit-timeline-studio

Create, edit, caption, voice, assemble, validate, and export editable video timelines with Timeline Studio. Use for automatic video editing, AI voiceover videos, subtitle generation, image-to-video assembly, short-form video production, deterministic local video rendering, .timeline project automation, or end-to-end editor evaluation in Codex, Claude Code, Copilot, and Gemini CLI.

MartinDelophygithub.com/MartinDelophyGitHub ↗
claude-codecopilotships scriptsMIT
Install
npx skills add MartinDelophy/ai-video-editor --skill edit-timeline-studio --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 7 KB
Bundled scripts: yes
Path: skills/edit-timeline-studio/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 450
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AI Video Editing with Timeline Studio Turn the user's exact editorial request and media into reversible Timeline Studio edits. Keep the editable timeline as the source of truth; never replace it with an opaque one-shot render. ## Choose the execution path 1. Treat `https://video-editor.ai-creator.top/` as the canonical hosted editor. When the user asks to use the website, provides no repository, or expects Browser Use, proactively open this URL and inspect the live editor before planning the edit. 2. When this repository is available and the task concerns local development, unpublished changes, or evaluation, start the local editor and use it instead of the hosted release. Read the actual server URL from the process output; never assume port 5173. 3. Inspect `package.json` for an Agent command script. Do not use `npm run ... --if-present` as capability detection because it can succeed silently. 4. If the command runner exists, read [references/command-contract.md](references/command-contract.md), inspect the project, build a versioned plan, run the structural validator, and use `project.diff` as the authoritative semantic dry run before `project.run`. 5. Otherwise, read [referenc

What's inside
Steps it walks through
  1. Choose the execution path
  2. Workflow
  3. 1. Inspect before editing
  4. 2. Plan at the supported fidelity
  5. 3. Apply safely
  6. 4. Verify the result
  7. Interpret underspecified requests conservatively
  8. Learn from every real run
  9. Capability boundaries
Ships with 15 files
  • .claude-plugin/plugin.json
  • README.md
  • agents/openai.yaml
  • docs/agent-video-editing.md
  • docs/claude-code-video-editing.md
  • docs/codex-video-editing.md
  • docs/command-reference.md
  • docs/comparison.md
  • docs/examples.md
  • docs/gemini-cli-video-editing.md
  • docs/github-copilot-video-editing.md
  • references/browser-workflow.md
  • references/command-contract.md
  • references/current-capabilities.md
  • scripts/validate_edit_plan.mjs
About this skill
What does the edit-timeline-studio skill do?

Create, edit, caption, voice, assemble, validate, and export editable video timelines with Timeline Studio. Use for automatic video editing, AI voiceover videos, subtitle generation, image-to-video assembly, short-form video production, deterministic local video rendering, .timeline project automation, or end-to-end editor evaluation in Codex, Claude Code, Copilot, and Gemini CLI.

How do I install it?

Run `npx skills add MartinDelophy/ai-video-editor --skill edit-timeline-studio --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From MartinDelophy/ai-video-editor, a repository with 450 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going