CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

studio-mode

Understand the capabilities and restrictions of each Remotion Studio mode. Use when implementing or reviewing Studio actions, permissions, availability, or UI across interactive, detached, deployed, and browser-based Studios.

Quality

90%

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.

An exemplary lean reference skill: a compact four-mode capability matrix of non-obvious, project-specific facts capped by a clear decision rule. The only gap is the absence of any guidance for programmatically detecting the current mode, which an implementer would need to act on the rule.

Suggestions

Add a brief note on how to detect the active mode in code (e.g. checking previewServerConnected or a browser/deployed flag), since the decision rule depends on knowing the current mode.

Optionally enumerate which server-backed actions are affected (codemods, package installs, 'Open in') per mode in a compact table so the hide/disable decision is fully mechanical.

DimensionReasoningScore

Conciseness

The body is lean and assumption-respecting: no explanation of what Remotion is, and every line carries project-specific facts Claude would not know ('previewServerConnected is false', 'Deployed at remotion.new', 'GitHub is the only supported "Open in" action'). This matches anchor 5's 'every token earns its place'.

5 / 5

Actionability

Concrete, instruction-only guidance: per-mode capability constraints plus the directive 'determine which modes support it and hide or disable it everywhere else' and 'Hide or disable actions that require a server'. It stops short of fully executable guidance because it never says how to detect which mode the Studio is running in (e.g. how to check previewServerConnected or detect the browser Studio), fitting anchor 4's 'minor gaps' rather than anchor 5.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (under 50 lines, one decision procedure) and the single action is unambiguous: determine mode support from the enumerated capabilities, then hide or disable the action elsewhere. Per the simple-skill exception this matches a 5; the operation is also non-destructive, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ directories exist), and the numbered mode list is well organized. This fits the guideline that such skills score 5 with just well-organized sections.

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 well-crafted description with an explicit and specific 'Use when' trigger clause and a clearly delineated niche. Its only weakness is that the 'what' is phrased as a single generic action ('Understand...') rather than enumerating the concrete capabilities it confers.

Suggestions

Replace or supplement the generic 'Understand the capabilities and restrictions' with 1-2 concrete actions, e.g. 'Determine which Studio actions to hide or disable per mode' alongside the understanding claim.

Add a few natural trigger synonyms users might say, such as 'read-only Studio', 'preview server', or 'remotion.new', to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('capabilities and restrictions of each Remotion Studio mode') with one generic action verb ('Understand'), matching the anchor for domain plus 1-2 non-comprehensive actions. It does not list several concrete actions (e.g. hide/disable server-backed actions), so it falls short of anchor 4, but the enumerated modes and scope terms lift it above anchor 2's bare domain label.

3 / 5

Completeness

It explicitly answers both questions: 'what' ('Understand the capabilities and restrictions of each Remotion Studio mode') and 'when' with concrete trigger phrases ('Use when implementing or reviewing Studio actions, permissions, availability, or UI'). This matches anchor 5; anchor 4's example has a noticeably vaguer 'when' clause.

5 / 5

Trigger Term Quality

'Studio actions', 'permissions', 'availability', 'UI', and the mode adjectives 'interactive, detached, deployed, and browser-based' are natural phrases a Remotion developer would say. A few natural variants are missing (e.g. 'read-only', 'preview server', 'remotion.new'), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Remotion Studio' is a clear niche with distinct, product-specific triggers (Studio modes, preview server, codemods), giving minimal conflict risk with other skills. It clearly matches anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

remotion-dev/remotion

Path

.agents/skills/studio-mode/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.