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

91%

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

100%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 exemplarily lean, fully executable skill body: exact paths, commands, a CI verification hook, and an escalation rule, with no wasted tokens. It is a simple single-purpose skill and scores at the top of every content dimension under the rubric's simple-skill provisions.

Dimension	Reasoning	Score
Conciseness	Ten lean lines with zero padding or explanation of concepts Claude already knows; every line is a placement rule, an exact path, or a command.	5 / 5
Actionability	Gives exact paths (`.agents/skills/<skill-name>/SKILL.md`, `packages/skills/skills/<skill-name>/SKILL.md`), the symlink step, and copy-paste-ready commands (`bun run syncskills`, `bun run checkskills`) covering the common cases.	5 / 5
Workflow Clarity	A simple single-purpose skill whose action is unambiguous: place, symlink, run `bun run syncskills`, with CI verification via `bun run checkskills` and an explicit fallback ("ask whether the skill is internal or public") when in doubt.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (no bundle files exist), and the content is well organized under a single clear heading, which the rubric's simple-skill guideline rewards with a top score.	5 / 5
	Total	20 / 20 Passed

Description

82%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 concise, third-person description that clearly states both what it does and when to use it, with a well-niched trigger scope. Keyword coverage is good but misses a few natural phrasings users might use when creating or relocating skills.

Dimension	Reasoning	Score
Specificity	"Document Remotion skill placement" names the domain and the single concrete decision ("whether a skill belongs in .agents/skills ... or packages/skills"), matching the anchor for domain plus 1-2 concrete actions rather than several listed actions.	3 / 5
Completeness	It explicitly answers what ("Document Remotion skill placement ... decide whether a skill belongs in .agents/skills ... or packages/skills") and when ("Use when adding, moving, or editing Remotion skills") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"adding, moving, or editing Remotion skills" are natural phrases a user would say, and "internal skill"/"public skill" are covered, but common variants like "creating a new skill" or "where to put a skill" are missing.	4 / 5
Distinctiveness Conflict Risk	The scope is tightly niched to "Remotion skill placement" with distinct triggers ("adding, moving, or editing Remotion skills"), giving minimal overlap with other skills.	5 / 5
	Total	17 / 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: 6f4e0d5

Reviewed: 5 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.