CtrlK
BlogDocsLog inGet started
Tessl Logo

checkout

Checkout a requested branch or ref in the Remotion repo, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An extremely lean body with executable commands and a clear sequence, but the checkout step is stated as a directive rather than a concrete command, leaving one gap in actionability.

Suggestions

Replace the directive 'Checkout the user-provided ref' with an executable command such as `git checkout <ref>` so all steps are copy-paste ready.

Consider naming the expected dependency/runtime (bun) earlier so the workflow is self-contained, though it is already implied by the commands.

DimensionReasoningScore

Conciseness

Six lean lines with no concept explanation or padding; every token earns its place and assumes Claude's competence.

3 / 3

Actionability

Provides executable commands ('bun i', 'bun run build') but the first step ('Checkout the user-provided ref') lacks a copy-paste-ready command such as 'git checkout <ref>'.

2 / 3

Workflow Clarity

The sequence (checkout ref, install, build) is unambiguous and complete for this simple single-purpose skill, which can score 3 per the simple-skills note.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references; the minimal inline content is appropriately organized for a skill of this size.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, well-targeted description that clearly states the skill's actions, repo scope, and explicit use-when trigger. It avoids fluff and is unlikely to be triggered for the wrong skill.

DimensionReasoningScore

Specificity

Lists three concrete actions ('Checkout a requested branch or ref', 'install dependencies', 'build'), matching the anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what ('Checkout ... then install dependencies and build') and when via an explicit 'Use when the user asks to checkout a ref and prepare the workspace' clause.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — 'checkout a ref', 'branch', 'prepare the workspace' — giving good coverage of the relevant vocabulary.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'the Remotion repo' with a distinct prepare-workspace trigger, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.