CtrlK
BlogDocsLog inGet started
Tessl Logo

checkout

Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A lean, mostly executable skill body with clear sequencing and well-handled conditional logic for the Codex environment. The only notable gaps are the missing explicit checkout command and absence of any success verification before reporting completion.

DimensionReasoningScore

Conciseness

The body is ~12 lean lines with no explanation of concepts Claude already knows (no git or bun tutorials); every line is instruction or executable command. This matches the lean 'every token earns its place' anchor, with nothing to trim for score 4 territory.

5 / 5

Actionability

Concrete commands are given for the PR title lookup ('gh pr view --json title --jq .title'), the rename ('set_thread_title'), and the install/build ('bun i', 'bun run build'), but the core checkout step itself has no explicit command (e.g. 'git checkout <ref>'). This is mostly executable with a minor gap, fitting score 4 rather than the fully copy-paste-ready score 5.

4 / 5

Workflow Clarity

The sequence (checkout → conditional title rename → install → build) is clear, with explicit branch handling ('If the ref has no associated PR, leave the task title unchanged'; 'Outside Codex, skip the PR title lookup'). It falls short of score 5 because there is no checkpoint validating that checkout or build succeeded before proceeding; it stays above score 3 since the conditional branches are explicitly stated and no destructive/batch-operation cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and the body is well organized as a short instruction block followed by a runnable command block. Per the simple-skill exception, this matches the top anchor: appropriate content split for its size with nothing that belongs in a separate file.

5 / 5

Total

18

/

20

Passed

Description

88%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 tight, third-person description that names every concrete action and includes an explicit 'Use when' trigger clause. Trigger vocabulary is good but could add natural synonyms like 'switch branches' or 'pull down a PR' to further reduce overlap with generic git-checkout skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Checkout a requested branch or ref', 'rename the current task to the associated PR title', 'install dependencies and build' — with no vague padding, matching the comprehensive-coverage anchor. It does not fit the score-4 anchor because there are no minor gaps: every capability of the skill is named.

5 / 5

Completeness

It explicitly answers both what the skill does (checkout, rename task, install, build) and when to use it via the concrete trigger clause 'Use when the user asks to checkout a ref and prepare the workspace'. The 'when' is explicit with concrete trigger phrases, matching the score-5 anchor rather than the merely-present 'when' of score 4.

5 / 5

Trigger Term Quality

Natural trigger terms like 'checkout', 'ref', 'PR title', 'install dependencies', 'build', and 'prepare the workspace' are present, but common user variations such as 'switch branches' or 'pull down a PR' are missing. It is above the midpoint (good coverage) but short of the synonym-and-extension completeness of the score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to the Remotion repo and Codex-specific behavior, making it mostly distinct, but it could still overlap with a generic git checkout or workspace-setup skill. Minor overlap risk with closely related skills fits the score-4 anchor; it lacks the fully distinct niche of score 5.

4 / 5

Total

18

/

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