nullable-new-params

Fix newly added optional parameters, optional React props, and optional type/interface members in Remotion monorepo diffs by converting internal APIs to required nullable values and updating call sites. Use when a PR, review, or user asks to forbid new `foo?: T` / `param?: T` additions except for exported or documented public APIs where requiring the value would be breaking.

Quality

100%

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

100%

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

The body is concise, fully actionable with runnable commands and code, and presents a well-sequenced workflow with explicit verification feedback loops. Its single bundle file is cleanly signaled and one level deep, giving good progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean: it states the convention crisply and uses minimal Before/After TS snippets without explaining concepts Claude already knows (no "what is null vs undefined" padding), matching the score-3 lean-and-efficient anchor over the mostly-efficient score-2.	3 / 3
Actionability	It provides an executable scanner command, copy-paste Before/After TS examples, concrete call-site patterns (`field: null`, `field: maybeValue ?? null`), and a runnable verify command (`bunx turbo run make --filter='...'`), matching the score-3 fully-executable anchor rather than the pseudocode/gap score-2.	3 / 3
Workflow Clarity	The 7-step sequence includes an explicit Verify step with a feedback loop ("Run the scanner again until only intentional public API exceptions remain") plus focused tests/builds, so the batch-operation verification cap does not apply; this matches the score-3 checkpoint-and-recovery anchor over score-2's missing checkpoints.	3 / 3
Progressive Disclosure	Content is organized into Rule / Workflow / Review checklist with one well-signaled, one-level-deep bundle reference (`scripts/find-new-optional-params.ts`) that exists on disk, matching the score-3 clear-overview-with-signaled-references anchor rather than the score-2 poorly-signaled case.	3 / 3
	Total	12 / 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.

The description is specific, action-oriented, and third-person with an explicit "Use when..." trigger covering both what and when. Its distinct Remotion/optional-param niche and pastable syntax triggers keep conflict risk low.

Dimension	Reasoning	Score
Specificity	It enumerates multiple concrete actions across params, React props, and type/interface members ("Fix newly added optional parameters, optional React props, and optional type/interface members... by converting internal APIs to required nullable values and updating call sites"), matching the score-3 anchor for listing several specific concrete actions rather than the narrower score-2.	3 / 3
Completeness	It explicitly answers both what (fix/convert/update call sites) and when via an explicit "Use when..." clause, matching the score-3 anchor and clearly above score-2 where the trigger is missing or only implied.	3 / 3
Trigger Term Quality	Natural trigger phrasing a developer/reviewer would actually say appears directly ("Use when a PR, review, or user asks to forbid new `foo?: T` / `param?: T` additions"), with broad coverage including pasted syntax, matching score-3 over the partial-coverage score-2.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Remotion monorepo diffs, nullable-vs-optional convention) with distinct triggers like `foo?: T`/`param?: T` makes it unlikely to fire for an unrelated skill, matching score-3 rather than the overlapping score-2.	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/nullable-new-params/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.