CtrlK
BlogDocsLog inGet started
Tessl Logo

version

The version of Remotion we are working on.

37

Quality

34%

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/version/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 lean and context-appropriate but provides only a file pointer and a high-level instruction without executable steps or validation. As a simple skill it is adequately organized, though it lacks any section structure.

Suggestions

Add concrete steps: how to read the current version from version.ts, how to compute the next patch version, and how to find/update version references in the docs.

Include a validation checkpoint (e.g. grep the docs for the old version string and confirm none remain) so the task has a feedback loop.

Add a brief section header such as "## Updating the version" to give the minimal body a touch of structure.

DimensionReasoningScore

Conciseness

The four short sentences assume Claude knows Remotion and avoid concept padding, with only minor redundancy in the repeated phrase "next version" that could be trimmed, fitting the efficient-with-minor-trims anchor rather than the fully-lean anchor at 5.

4 / 5

Actionability

It provides one concrete pointer (`packages/core/src/version.ts`) but no specific steps or commands for how to bump the version or locate and update the docs, matching the minimal-concrete-guidance anchor rather than the some-concrete-but-incomplete anchor at 3.

2 / 5

Workflow Clarity

An implicit sequence (locate current version → next is a patch → update docs) and a clear single goal are present, but no explicit steps or validation checkpoints are given; this is not a destructive/batch op so no cap applies, fitting the steps-implied-but-checkpoints-missing anchor.

3 / 5

Progressive Disclosure

The skill is short and self-contained with no need for external references, but it lacks section headers or any structure, so it lands below the well-organized-sections anchor at 5 and at the good-structure-with-minor-gaps anchor.

4 / 5

Total

13

/

20

Passed

Description

15%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 a bare noun phrase that identifies the project context but fails to state what the skill does or when to invoke it. It lacks action verbs, trigger guidance, and a clear what/when structure.

Suggestions

Rewrite as a third-person action statement, e.g. "Bumps the Remotion version and ensures docs reference the correct next version."

Add an explicit trigger clause: "Use when updating Remotion's version number or when docs need to reflect a new release."

Replace the generic "version" with concrete trigger terms like "version bump", "release", or "Remotion version.ts".

DimensionReasoningScore

Specificity

The description is a noun phrase ("The version of Remotion we are working on.") with no action verbs at all — it identifies a fact rather than naming concrete actions the skill performs, falling below the anchor-2 example which at least has an action verb.

1 / 5

Completeness

It states neither what the skill does (no action) nor when to use it (no "Use when..." clause); both the what and when are effectively missing, matching the missing-both anchor rather than the vague-what anchor at 2.

1 / 5

Trigger Term Quality

"Remotion" is a recognizable project name and "version" is a generic keyword, but there are no natural trigger phrases a user would actually say when they need this skill, matching the one-or-two-generic-keywords anchor.

2 / 5

Distinctiveness Conflict Risk

"Remotion" gives it a specific niche, but the vague purpose means it could overlap with other Remotion-related skills, fitting the somewhat-specific-but-could-overlap anchor rather than the mostly-distinct anchor at 4.

3 / 5

Total

7

/

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.

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.