add-new-package

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

Quality

93%

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

87%

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

A concise, highly actionable checklist with clear sequencing and tidy organization. The only gap is the absence of an explicit build/test validation checkpoint with an error-recovery loop in the multi-file workflow.

Suggestions

Add an explicit verification step after the build (e.g., step 7: run `bun run make` and the test suite, and only proceed if both pass) with a fix→retry loop, to lift workflow_clarity from 2 to 3.

State how to confirm the package is correctly registered (e.g., that it appears in list-of-remotion-packages.ts / package-info.ts and is importable) as a final sanity check.

Note where to run tests for the new package so the validation step is concrete rather than implied.

Dimension	Reasoning	Score
Conciseness	Lean file/config/command lists with no explanatory padding of concepts Claude already knows; every line carries a concrete instruction, matching the 'every token earns its place' anchor rather than the padded anchor at 1 or the mostly-efficient-but-tightenable anchor at 2.	3 / 3
Actionability	Gives exact file paths, concrete config keys/values (moduleResolution: "bundler", target: "ES2022"), and runnable commands (bun i, bun run make, the make script); instruction-only but copy-paste-ready, not the pseudocode/incomplete anchor at 2.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced, but there is no explicit validation/verification checkpoint or fix→retry feedback loop for a multi-file batch operation, which per the rubric caps clarity at 2 rather than the explicit-validation anchor at 3.	2 / 3
Progressive Disclosure	Under ~50 lines with well-organized sections (Steps, Version, Patterns) and a single clearly-signaled one-level cross-skill reference ("See the writing-docs skill"); no bundle files exist to require deeper structure, so it meets the simple-skill allowance for a 3.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 tight, specific description that names concrete actions, gives an explicit natural-language trigger, answers both what and when, and occupies a distinct niche. No weak dimensions; no changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "package scaffolding, monorepo registration, documentation, build scripts, tests, and release checklist updates" — rather than vague language; uses third-person voice with no first/second person to penalize.	3 / 3
Completeness	Explicitly answers both what (the enumerated creation tasks) and when ("Use when creating a new @remotion package"), so it is not capped at 2 for a missing 'Use when' clause.	3 / 3
Trigger Term Quality	"Use when creating a new @remotion package" is exactly the phrase a user would naturally say when needing this skill; matches the natural-term coverage anchor rather than the jargon/generic anchor at 1 or partial-variation anchor at 2.	3 / 3
Distinctiveness Conflict Risk	Scoped narrowly to the Remotion monorepo and @remotion packages, giving it a clear niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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/add-new-package/SKILL.md
Commit: 1b58387

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