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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An efficient, actionable body that sequences the workflow clearly with a sensible fallback. Adding an explicit build-verification step and light section headers would round it out.

Suggestions

Add a validation checkpoint after `bun run build` (e.g., confirm the build exited 0 before declaring success) to satisfy the feedback-loop expectation for build operations.

Add minimal section headers (e.g., '## Rename task (Codex only)' and '## Install & build') so the steps are scannable at a glance.

Dimension	Reasoning	Score
Conciseness	Lean prose with no concept explanations Claude already knows; every line instructs a concrete action and the code block is minimal.	5 / 5
Actionability	Provides fully executable commands (`gh pr view --json title --jq .title`, `set_thread_title`, `bun i`, `bun run build`) that are copy-paste ready for the common cases.	5 / 5
Workflow Clarity	Clear sequencing with a conditional branch and an explicit no-PR fallback, but lacks an explicit validation checkpoint confirming the build succeeded.	4 / 5
Progressive Disclosure	Short single-purpose skill with no external references needed and a well-delimited code block, but no section headers to aid scanning; good structure with minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

92%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 strong, specific description that clearly conveys both capability and trigger conditions in third-person voice without padding. Minor room to broaden trigger synonyms, but overall excellent.

Dimension	Reasoning	Score
Specificity	Names the domain (Remotion repo) and lists multiple concrete actions—checkout a ref, rename the task to the PR title, install dependencies, and build—giving comprehensive coverage.	5 / 5
Completeness	Explicitly states what it does (checkout, rename task, install, build) and when to use it with a concrete trigger clause, satisfying both requirements clearly.	5 / 5
Trigger Term Quality	'Use when the user asks to checkout a ref and prepare the workspace' provides natural phrasing a user would say, though synonyms like 'checkout a branch' or 'switch branch' are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped to the Remotion repo and Codex task renaming, giving it a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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/checkout/SKILL.md
Commit: dbb2c0a

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.