CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

studio-dev

Develop or review Remotion Studio features and UI. Apply Studio principles for optimistic updates, agent access through code or WebMCP, iframe-safe hover behavior, design consistency, mode availability, and performance verification.

Quality

82%

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

92%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.

The content is an exemplary apply-when-implementing skill: every section gives concrete, repo-specific instructions with exact helpers, paths, and commands, and verification is an explicit checklist with feedback loops. The only mild criticism is a couple of explanatory passages that restate behavior available from linked sources. Detail is appropriately pushed to clearly signaled sibling-skill references.

DimensionReasoningScore

Conciseness

The body is dense, prescriptive project knowledge (specific helpers, file paths, mode tables, commands) with no teaching of concepts Claude already knows and no padding — matching anchor 5's lean character. A few explanatory sentences could still be trimmed (the hover-bug mechanics paragraph and the .css-reset descendant-rule explanation both restate behavior a reader could get from the linked sources), which places it at anchor 4.

4 / 5

Actionability

Guidance is fully concrete and executable: named helpers ("HOVERABLE_CLASS_NAME and hoverableStyle() from hoverable.ts", "observeHover()"), named components ("ActionTooltip and ClippedTextTooltip"), a named regression test ("clears hover backgrounds even if pointer leave events are lost"), and copy-pasteable commands ("bunx turbo run make --filter='@remotion/studio'", "bunx turbo run lint test --filter='@remotion/studio'"). This matches anchor 5's copy-paste-ready coverage of the common cases.

5 / 5

Workflow Clarity

The "Verify the feature" section is an explicit validation checklist — immediate feedback, persistence after HMR, failure recovery, undo/redo, per-mode availability, hover/focus/cursor/CSS-reset checks — backed by concrete build/lint/test commands and a performance feedback loop ("Capture a baseline... resolve regressions before finishing. Report the measured result"). Checkpoints and error-recovery loops are explicit, matching anchor 5 rather than anchor 4's "most checkpoints present".

5 / 5

Progressive Disclosure

Sections are well-organized and detail is delegated through clearly signaled, one-level-deep references with when-to-read conditions ("Read [studio-mode](../studio-mode/SKILL.md) when deciding availability", "Read [studio-css-reset]... and [no-pointer]... when adding or changing UI", "Follow [writing-tests]..."). No bundle files exist to inline, the body holds only core guidance, and no reference chains nest deeper than one level — matching anchor 5.

5 / 5

Total

19

/

20

Passed

Description

66%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.

The description clearly states what the skill does and enumerates specific capability areas, with strong niche terms like "Remotion Studio" and "WebMCP". Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness and leaves activation guidance only implied. Adding trigger phrasing and Browser Studio/remotion.new synonyms would lift it further.

Suggestions

Add an explicit trigger clause, e.g. "Use when developing, reviewing, or testing Remotion Studio features, the Studio UI, WebMCP tools, or Browser Studio at remotion.new."

Include "Browser Studio" and "remotion.new" as trigger terms so the deployed iframe variant is discoverable by users who mention it.

Name the concrete verification workflow (e.g. "run the Studio build, lint, and tests") to round out capability coverage toward comprehensive.

DimensionReasoningScore

Specificity

"Develop or review Remotion Studio features and UI" plus six named areas ("optimistic updates, agent access through code or WebMCP, iframe-safe hover behavior, design consistency, mode availability, and performance verification") lists several specific actions. It falls short of anchor 5 because these are topic labels rather than a comprehensive set of concrete actions, but it well exceeds the 1-2 actions of anchor 3.

4 / 5

Completeness

The "what" is clear (develop or review Remotion Studio features and UI with the listed principles), but there is no explicit "Use when..." clause or equivalent trigger guidance — usage is only weakly implied by "Develop or review". Per the judging guideline, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user in this repo would say are present: "Remotion Studio", "develop", "review", "features and UI", "WebMCP", "optimistic updates", "hover", "performance". A few natural terms are missing ("Browser Studio", "remotion.new", "Studio UI"), which keeps it at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Remotion Studio" plus "WebMCP" carves out a clear niche with minimal conflict risk against unrelated skills. Minor overlap remains with closely related sibling skills this skill cross-references (studio-perf, studio-mode, studio-css-reset), matching anchor 4 rather than the fully distinct anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 16 suspicious

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

.agents/skills/studio-dev/SKILL.md

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.