CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A lean, highly actionable skill body that gives exact paths and commands with no wasted tokens. It is well organized and short enough that progressive disclosure needs no external references, and the public-skill workflow includes a verification checkpoint.

DimensionReasoningScore

Conciseness

Every line carries actionable information with no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor; it assumes competence throughout.

3 / 3

Actionability

It gives concrete file paths, an explicit symlink instruction, and copy-paste-ready commands ('bun run syncskills', 'bun run checkskills'), fully executable guidance with specific examples.

3 / 3

Workflow Clarity

For this simple single-purpose skill the action is unambiguous, and the public-skill path is sequenced (place -> symlink -> syncskills -> CI checkskills) with an explicit verification step ('CI verifies the symlinks with bun run checkskills').

3 / 3

Progressive Disclosure

The body is well under 50 lines with no need for external references and is cleanly organized under a single header with clearly separated rules, which per the simple-skill guideline earns a 3.

3 / 3

Total

12

/

12

Passed

Description

85%

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 answers both what the skill does and when to use it, with concrete actions and a distinct niche. Trigger-term coverage is the weakest dimension, as it relies on a narrow set of verbs without common user phrasings.

Suggestions

Broaden trigger terms to cover common user phrasings (e.g., 'create', 'organize', 'where to place', 'which root') alongside 'adding, moving, or editing'.

Consider naming the audiences or repo convention keywords a user would naturally invoke when asking about skill placement.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('adding, moving, or editing Remotion skills') and a concrete decision outcome ('whether a skill belongs in .agents/skills ... or packages/skills'), matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly states what the skill does ('Document Remotion skill placement ... decide whether a skill belongs in .agents/skills ... or packages/skills') and an explicit 'Use when' trigger clause, satisfying both the what and the when.

3 / 3

Trigger Term Quality

The 'Use when adding, moving, or editing Remotion skills' trigger provides relevant natural verbs but coverage is narrow, missing common variations a user might say such as 'create a new skill', 'organize', or 'where should I place this skill'.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific — Remotion skill placement between two known roots — with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

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.