skill-locations

Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%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 exemplary lean governance skill: concrete paths and commands, no token waste, and a clear internal-vs-public structure. The only gap is the absence of an explicit local validation feedback loop for the public-skill workflow.

Dimension	Reasoning	Score
Conciseness	Roughly eight lines with no padding or explanation of concepts Claude already knows; every line carries actionable placement, symlink, or command guidance.	5 / 5
Actionability	Provides exact paths (`.agents/skills/<skill-name>/SKILL.md`, `packages/skills/skills/<skill-name>/SKILL.md`) and copy-paste-ready commands (`bun run syncskills`, `bun run checkskills`) covering the common cases.	5 / 5
Workflow Clarity	The public-skill sequence (place, symlink, sync, CI verify) is clear with a verification step, but there is no explicit local validate-fix-retry feedback loop; the operation is non-destructive so the 3-cap does not apply.	4 / 5
Progressive Disclosure	Under 50 lines, single-purpose, no external references needed, and cleanly organized into the internal vs public cases plus a doubt-resolution note, satisfying the simple-skill exception.	5 / 5
	Total	19 / 20 Passed

Description

87%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 well-constructed description that clearly pairs a concrete 'what' with an explicit 'Use when' trigger and a narrow, low-conflict niche. Minor headroom remains in synonym coverage and enumerating the placement criteria.

Dimension	Reasoning	Score
Specificity	Names the domain ('Remotion skill placement') and several concrete actions ('adding, moving, or editing') plus two exact target roots, but stops short of comprehensive coverage of what distinguishes the two cases.	4 / 5
Completeness	Explicitly states both the 'what' ('Document Remotion skill placement') and a concrete 'when' ('Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills ... or packages/skills ...').	5 / 5
Trigger Term Quality	Natural trigger verbs ('adding, moving, or editing') and the 'internal' vs 'public' framing match what a user would say, though a few synonyms (e.g. 'where to put', 'organize') are absent.	4 / 5
Distinctiveness Conflict Risk	The Remotion-specific placement niche and the internal-vs-public decision are highly targeted, with minimal overlap risk against other skills.	5 / 5
	Total	18 / 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/skill-locations/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.