CtrlK
BlogDocsLog inGet started
Tessl Logo

studio

Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, executable, well-sequenced runbook that adds only the non-obvious operational gotchas Claude would not already know. It is among the better-written skill bodies for its scope.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives only the non-obvious operational details (use bunx not npx, always --no-open, don't probe the port) with no padding or concept re-explanation.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands ("bun i && bun run build", "cd packages/example && bunx remotion studio --no-open") plus concrete guidance on reading the URL and opening it via tool_search.

3 / 3

Workflow Clarity

A clearly numbered sequence with explicit checkpoints (read CLI output for the URL, use the exact printed URL, verify only after the CLI identifies it); the operation is non-destructive so the missing-retry cap does not apply.

3 / 3

Progressive Disclosure

At well under 50 lines with a single focused task and no need for external reference files, the well-organized Overview/Workflow sections meet the simple-skills threshold for full progressive-disclosure credit.

3 / 3

Total

12

/

12

Passed

Description

100%

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

The description is concise, third-person, and clearly states both what the skill does and when to invoke it with concrete triggers. It avoids fluff and over-claims entirely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Start Remotion Studio from packages/example and open it in the Codex browser" — rather than vague language, matching the anchor for listing several specific actions.

3 / 3

Completeness

Explicitly answers both what (start Studio, open in Codex browser) and when ("Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally").

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — "/studio", "$studio", "asks to launch the example Studio", "wants the Remotion Studio dev UI available locally" — giving good trigger coverage.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and trigger-specific (Remotion example Studio launched via Codex browser), with distinct slash/keyword triggers unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
Reviewed

Table of Contents

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.