CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-new-package

Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates. Use when creating a new @remotion package.

70

Quality

88%

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

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

Highly actionable and token-efficient content with excellent structure and appropriate delegation to other skills. The main gap is the absence of validation/verification steps after the build, which leaves the workflow without explicit checkpoints for confirming the new package is correctly wired up.

Suggestions

Add an explicit validation step after 'bun run make', such as verifying dist/index.js and dist/index.d.ts exist and importing the package from the example build to confirm registration worked.

Include a brief error-recovery note for common failure points (e.g., what to check if the build fails or if the new package is missing from the CLI's package list).

Add a final verification checklist confirming each registration touchpoint (root tsconfig, both list-of-remotion-packages.ts files, package-info.ts) was updated.

DimensionReasoningScore

Conciseness

The body is a lean checklist of repo-specific facts (exact files, config values, commands) with no padding and no explanations of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable guidance throughout: exact file paths ('packages/cli/src/list-of-remotion-packages.ts'), concrete config values ('emitDeclarationOnly: true'), and runnable commands ('cd packages/<name> && bun run make').

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with specific commands, but there are no validation checkpoints or error-recovery guidance (e.g., verifying the build output or what to do if 'bun run make' fails), matching the anchor for present sequence with missing checkpoints.

3 / 5

Progressive Disclosure

A self-contained ~53-line body with well-organized sections (Steps, Version, Patterns) that appropriately delegates documentation detail to the separate 'writing-docs' skill; no bundle files are needed.

5 / 5

Total

18

/

20

Passed

Description

83%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 description: specific, third-person, with an explicit 'Use when' trigger and a well-defined niche. The only weakness is a single narrow trigger phrase where synonyms or common variations ('scaffold a package', 'new Remotion package') would broaden natural activation.

DimensionReasoningScore

Specificity

Lists five concrete actions ('package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates') in third person, comprehensively covering the package-creation workflow.

5 / 5

Completeness

Both 'what' (the enumerated actions) and 'when' ('Use when creating a new @remotion package') are explicit, but the 'when' clause is a single narrow trigger rather than the richer set of concrete trigger phrases of the top anchor.

4 / 5

Trigger Term Quality

Natural terms like 'Remotion monorepo' and 'creating a new @remotion package' are present, but coverage stops at a single trigger phrasing without synonyms or variations.

4 / 5

Distinctiveness Conflict Risk

The Remotion/@remotion framing carves out a clear niche with distinct triggers, making conflict with other skills minimal.

5 / 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

Path

.agents/skills/add-new-package/SKILL.md

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.