CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visual-mode

Guidance for working on Remotion Studio Visual Mode, sequence identity, node paths, symbolicated stacks, override IDs, and hot reload behavior. Use when implementing or debugging visual editing of Sequences.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/visual-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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 body captures genuinely non-obvious domain knowledge in a token-efficient way, but it reads as raw engineering notes rather than a skill: observations are not shaped into a usable workflow, key directives are garbled or buried, and no concrete implementation/debugging steps are given. The remotion.new route-tracking section is the one fully actionable piece.

Suggestions

Restructure the field observations into a sequenced workflow for the skill's stated purpose — e.g., ordered steps for tracking sequence identity via nodePath + index across hot reloads, with an explicit validation checkpoint for the expanded-state end goal.

Add concrete executable guidance: the actual API/code for fetching a nodePath once per symbolicated stack, and a specific debugging procedure for identity/remount mismatches instead of inference from raw observations.

Fix garbled sentences ("needs to be calculated asyn", "overrideId works change") and move the loose prose after the Fields list under clear section headers so every rule is scannable rather than buried in paragraph notes.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence with no padding or explanations of known concepts, but the stack/nodePath/overrideId identity relationships are restated across several loose sentences ("Once nodePath is mapped to overrideId...", "If the same stack is found...", "multiple sequences can share the same stack...") and some garbled phrasing ("overrideId works change") forces re-reading, so it is not fully tight.

4 / 5

Actionability

Concrete knowledge is present (field-by-field identity semantics like "overrideId -> does keep the identity the same... even if the file / line / column changes", and the explicit remotion.new checklist rule), but there is no executable guidance for the stated purpose — no code, commands, or API details for fetching a nodePath "for every stack once" or for debugging identity mismatches.

3 / 5

Workflow Clarity

The body is a collection of observations with no sequenced process or checkpoints for implementing/debugging visual editing; only the remotion.new route rule is a coherent, unambiguous directive. It sits between 'steps missing or incoherent' and 'rough sequence present but many gaps', closer to the latter only because the route rule and the nodePath+index design intent give rough direction.

2 / 5

Progressive Disclosure

Two section headers exist ("## Fields", "## remotion.new route tracking") and the skill is short enough to need no external files, but a block of unstructured, unheaded prose follows the Fields list and mixes design rules with observations — organization gaps beyond the 'minor' level of the next anchor.

3 / 5

Total

12

/

20

Passed

Description

73%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 focused, appropriately triggered description for a narrow domain, with an explicit 'Use when' clause and strong natural trigger terms. Its main weakness is that 'Guidance for working on...' lists topics rather than stating concrete capabilities. Voice is correctly third person.

DimensionReasoningScore

Specificity

"Guidance for working on Remotion Studio Visual Mode, sequence identity, node paths..." names the domain clearly and the trigger clause names two actions ("implementing or debugging"), but the capability statement itself is generic topic-listing rather than several concrete actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Both parts are present: a 'what' (guidance on Visual Mode, sequence identity, node paths, etc.) and an explicit 'when' ("Use when implementing or debugging visual editing of Sequences"). Not a 5 because the 'what' is a topical listing without concrete capability phrases; not a 3 because the 'Use when' clause is explicit.

4 / 5

Trigger Term Quality

Terms a user in this domain would naturally say are well covered ("Remotion Studio", "Visual Mode", "hot reload", "Sequences", "override IDs", "symbolicated stacks"), but there are no synonyms or phrasing variations beyond the core vocabulary, so it falls just short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Remotion Studio Visual Mode, override IDs, symbolicated stacks) with triggers that would not plausibly fire for any other skill, giving minimal conflict risk.

5 / 5

Total

16

/

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/visual-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.