convert

Start the local @remotion/convert app and open it in the Codex browser. Use when the user invokes /convert or $convert, asks to launch convert.remotion.dev locally, or wants to inspect the Convert package UI.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean skill body: exact commands, a concrete default URL with fallback behavior, and well-organized sections with no token waste. The only gaps are missing validation checkpoints (confirming the dev server is ready, detecting an already-running server) that step 5 implicitly assumes.

Suggestions

Add a brief checkpoint after step 2, e.g. wait for the dev server's ready line in its output before opening the URL.

Add one line to step 5 explaining how to tell a newly started server from an already running one (e.g. check for an existing process or prior session output), since the report requirement currently has no supporting step.

Dimension	Reasoning	Score
Conciseness	The 28-line body is lean with zero padding: a two-line overview and a numbered workflow of commands and one-sentence instructions, with no explanation of concepts Claude already knows.	5 / 5
Actionability	Every step is copy-paste ready — exact commands ("bun i && bun run build", "cd packages/convert && bun run dev"), the expected URL (http://localhost:5173) with a fallback rule for alternate Vite ports, and a concrete fallback (tool_search) for a missing browser tool.	5 / 5
Workflow Clarity	The 5-step sequence is clear and ordered with contingencies for port changes and a missing browser tool, but there is no checkpoint for confirming the build/dev server actually succeeded before opening the URL, and step 5 asks the agent to report whether the server was "newly started or already running" without any instruction for detecting an already-running instance.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed; the Overview and Workflow sections are well-organized and the skill qualifies for the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description with an explicit "Use when" clause and concrete, distinctive trigger phrases covering command, URL, and intent formulations. Its only weakness is that the "what" side is thin relative to the "when" side, listing just two high-level actions.

Dimension	Reasoning	Score
Specificity	The description names the domain (@remotion/convert) and two concrete actions — "Start the local @remotion/convert app" and "open it in the Codex browser" — but does not enumerate the underlying steps (install, build, run dev server), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It explicitly answers both what ("Start the local @remotion/convert app and open it in the Codex browser") and when ("Use when the user invokes /convert or $convert, asks to launch convert.remotion.dev locally, or wants to inspect the Convert package UI") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Triggers are natural and varied — "invokes /convert or $convert", "launch convert.remotion.dev locally", "inspect the Convert package UI" — covering command, URL, and intent phrasings, though a few plausible synonyms (e.g. "run the converter", "Remotion convert") are absent.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific — a named Remotion sub-package, a distinct site URL, and slash-command triggers — making accidental triggering by unrelated skills very unlikely.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/convert/SKILL.md
Commit: 6f4e0d5

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.