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.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/add-new-package/SKILL.md

Quality

Content

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

A tight, project-specific skill that is nearly all signal — exact paths, field values, and commands with zero padding. Its one real weakness is the absence of any validation or error-recovery checkpoint in a workflow that batch-edits many files across the monorepo, which caps workflow clarity despite the otherwise excellent sequencing.

Suggestions

Add a verification step after the build, e.g. 'Verify: bun run build in packages/docs should typecheck the new package; if it fails, re-check tsconfig references and dependency versions' — this adds the feedback loop the workflow currently lacks.

Flesh out the 'src/index.ts — exports' step with a one-line convention (e.g. what a typical public entry point exports and how it maps to dist/index.d.ts).

State the failure path for the build step (what to check when tsgo or the bundle fails), completing the validate → fix → retry loop expected for batch operations.

Dimension	Reasoning	Score
Conciseness	The body is a lean checklist of file paths, exact field values, and commands ('tsconfig.json — extends ../tsconfig.settings.json, uses tsgo with emitDeclarationOnly: true...') with no concept explanation and no padding. Every token carries project-specific information Claude could not infer, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Guidance is mostly executable: exact commands ('cd packages/<name> && bun run make', 'tsgo && bun --env-file=../.env.bundle bundle.ts'), exact registration files, and concrete tsconfig values. It stops short of anchor 5 because there is no verbatim copy-paste-ready example (e.g. a package.json snippet) and one step ('src/index.ts — exports') is underspecified.	4 / 5
Workflow Clarity	The six steps are clearly numbered and correctly ordered (create files → register → docs → example → bun i → build), but there is no validation or verification checkpoint and no error-recovery loop for a multi-file batch edit across the monorepo. This matches the 'steps listed but validation gaps' anchor, and the batch-operation cap applies since no verification step exists.	3 / 5
Progressive Disclosure	The 54-line body is appropriately self-contained: well-organized sections (Steps, Version, Patterns), all detail correctly placed inline, and the single external pointer ('See the writing-docs skill for details on writing documentation.') is one level deep and clearly signaled. No bundle files exist, so there is nothing misstructured to penalize.	5 / 5
	Total	17 / 20 Passed

Description

71%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, well-scoped description: it clearly states what the skill does with a concrete enumeration of scope areas, and includes an explicit 'Use when' clause tied to a distinct niche. The main weakness is trigger coverage — a single trigger phrase with no natural synonyms or variations, which limits both discoverability and completeness.

Suggestions

Broaden the trigger clause with natural variations, e.g. 'Use when creating, adding, or scaffolding a new @remotion package or when the user asks to add a package to the Remotion monorepo.'

Consider mentioning '@remotion/<name>' package naming in the what-clause so searches for the scoped package name match.

Dimension	Reasoning	Score
Specificity	The description lists several concrete action areas — 'package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates' — which matches the 'several specific actions; minor gaps in coverage' anchor. It falls short of a 5 because the actions are named as scope areas rather than fully comprehensive concrete verbs.	4 / 5
Completeness	Both parts are explicitly present: a clear what ('Add a new package to the Remotion monorepo, including...') and an explicit when ('Use when creating a new @remotion package.'). It is not a 5 because the when clause is a single trigger phrase rather than the comprehensive concrete trigger phrases of the top anchor.	4 / 5
Trigger Term Quality	The only trigger phrase is 'Use when creating a new @remotion package' — one relevant keyword set with common variations and synonyms missing ('add a package', 'scaffold a package', 'new package'). It matches the 'some relevant keywords but missing common variations or synonyms' anchor, below anchor 4's 'good keyword coverage; a few natural terms missing'.	3 / 5
Distinctiveness Conflict Risk	'Remotion monorepo' and '@remotion package' establish a clear niche with distinct triggers that would not naturally collide with other skills. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor exactly.	5 / 5
	Total	16 / 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/add-new-package/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.