add-cli-option

Add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.

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 strong, actionable procedural skill with executable code, exact paths, and a well-sequenced workflow. The only gap is the absence of an explicit error-recovery feedback loop in the build/verify step.

Suggestions

Add an explicit feedback loop after Step 7, e.g. 'If `bun run make` fails, read the error, fix the option/config wiring, and re-run the build before proceeding.'

Turn the Step 6 docs checklist into a brief bullet checklist (CLI pages to touch, config.mdx section, id matching cliFlag) so the mandatory docs step is verifiable.

Dimension	Reasoning	Score
Conciseness	Lean and task-specific throughout — exact file paths, a complete option code block, and edge-case notes — with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides a full executable option definition, precise registration locations, and copy-paste-ready build commands, meeting the fully-executable anchor.	3 / 3
Workflow Clarity	A clear 7-step numbered sequence with an explicit 'Build and verify' checkpoint, but it lacks an error-recovery feedback loop (no 'if the build fails, fix and re-run' guidance), so it stops short of the score 3 anchor.	2 / 3
Progressive Disclosure	No bundle directories exist; the body is well-sectioned with a one-level-deep 'Reference files' list and a single signaled sibling-skill link, appropriate for an in-place skill.	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 concise, third-person description that states concrete actions and an explicit 'Use when' trigger for a well-scoped niche. It hits all four anchors at the top level.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation' — matching the multi-action anchor rather than the single-domain score 2.	3 / 3
Completeness	Explicitly answers both what (the four actions) and when via 'Use when adding or converting command-line flags or Remotion options', satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Uses natural terms a user would say — 'command-line flags', 'Remotion options', 'CLI or config option' — with good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Remotion CLI/config options) with distinct triggers, making overlap with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/add-cli-option/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.