CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

remotion-new-markup

Write or refactor editable Remotion markup with appropriate tracks, shared timing boundaries, and connected compositions.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/remotion-new-markup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 is an efficient, actionable overview that delegates detail to conditionally-signaled reference guides and closes with an explicit verification step. Its main gaps are the prose-only code example, the lack of feedback-loop detail around verification, and reference paths that escape the skill bundle and do not resolve within it. Fixing the reference locations would make the disclosure structure exemplary.

Suggestions

Show the extracted-component pattern as a short copy-paste code block (e.g. a module-scope Soundtrack component reading useCurrentFrame() and returning Audio with volume={interpolate(frame, ...)}).

Expand the final verification step into a concrete checkpoint: what to check in the full composition and standalone views, and what to do when the check fails.

Bundle the referenced guides inside the skill (e.g. under references/) or use paths that resolve from the skill's own directory, since the current ../../../packages/... links do not resolve within the skill bundle.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and assumes Remotion/React competence (e.g. "Call `useCurrentFrame()` in the smallest component that needs the frame to render") without explaining what Remotion or hooks are. Every sentence states a rule or its rationale ("This prevents that animation from re-rendering unrelated clips and scenes on every frame"), with no padding — matching anchor 5.

5 / 5

Actionability

Concrete, specific guidance throughout: "Extract that item into a component defined at module scope", "Keep editable `interpolate()` calls inline on the animated item's props", and a worked pattern where "a `Soundtrack` component can read `useCurrentFrame()` and return an `Audio` with `volume={interpolate(frame, ...)}`". The example is described in prose rather than shown as a copy-paste code block, a minor gap versus fully executable anchor 5.

4 / 5

Workflow Clarity

A coherent sequence is present: read the timeline-structure guide "before choosing components and wrappers", start with what should be edited together, apply the frame-subscription and timing-boundary rules, then "Verify a structural change in the full composition and any standalone views". The explicit verification step satisfies most checkpoints, but there is no feedback-loop detail on what to check or how to recover, keeping it below anchor 5.

4 / 5

Progressive Disclosure

The body is a well-signaled overview with conditional one-level references ("For footage with synchronized captions or overlays, also read..."; "For extracting a group into its own timeline, use..."). However, the referenced paths (../../../packages/skills/skills/remotion-interactivity/timeline-structure.md and siblings) point outside the skill directory and do not resolve in the actual bundle, which has no references/ directory — a navigation gap that falls short of anchor 5's "easy navigation".

4 / 5

Total

17

/

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 is specific and distinctive within the Remotion niche, naming concrete actions and artifacts rather than vague capability claims. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which caps completeness. Adding a trigger clause with a few natural phrases (video timeline, animation) would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. "Use when writing or refactoring Remotion compositions, tracks, or video timelines, or when extracting scenes into connected compositions."

Include a few more natural trigger terms users would actually say, such as "video", "timeline", or "animation", to broaden keyword coverage beyond the framework name.

DimensionReasoningScore

Specificity

"Write or refactor editable Remotion markup" names the domain and two concrete actions, and "appropriate tracks, shared timing boundaries, and connected compositions" enumerates specific artifacts. This is noticeably more informative than the anchor-3 example ("Processes PDF files and extracts content"), but it lacks the several distinct actions of an anchor-5 description.

4 / 5

Completeness

The "what" is clear (write or refactor editable Remotion markup with tracks, timing boundaries, and connected compositions), but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied through the word "Remotion". Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Remotion", "markup", "tracks", "compositions", and "refactor" give good natural keyword coverage anchored by the framework name. A few natural terms a user might say are missing ("video", "timeline", "animation"), so it falls short of the comprehensive synonym-level coverage of anchor 5 while clearly exceeding anchor 3.

4 / 5

Distinctiveness Conflict Risk

"Remotion" is a clear niche with distinct domain triggers, so it would not fire for unrelated skills. However, the body references sibling skills in the same family (remotion-interactivity, remotion-markup), indicating minor overlap risk with closely related skills, which keeps it below 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: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

.agents/skills/remotion-new-markup/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.