deprecate-api

Reference for how deprecation of public Remotion APIs is represented in TypeScript source and documentation. Use when adding, reviewing, or discussing a deprecation of a function, component, hook, type, prop, option, or other public API that remains available.

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

100%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 model of a lean convention/reference skill: concrete copy-paste examples for every representation, a clear in-scope/out-of-scope boundary, and no padding. It fully respects the context window while remaining immediately actionable.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: states the three representation places, gives minimal copy-paste examples, and a tight scope section without explaining what deprecation or Remotion is; every line earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready examples for all three representations (JSDoc @deprecated annotation, double-tilde strikethrough mdx, info admonition) covering both the function and prop/option cases.	5 / 5
Workflow Clarity	Single-purpose convention skill under 50 lines with an unambiguous three-place sequence (numbered 1-2-3) and a clear scope/non-scope boundary; the simple-skill exception applies as there is no destructive or batch operation requiring validation checkpoints.	5 / 5
Progressive Disclosure	Well-organized into clear sections (TypeScript representation, Documentation representation, Scope) with no bundle files needed; for a sub-50-line single-purpose skill this is well-structured and navigable.	5 / 5
	Total	20 / 20 Passed

Description

87%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 tight, third-person description that covers what and when with concrete API-surface enumeration and natural trigger terms. Its only weakness is slightly broad use-action verbs ('adding, reviewing, or discussing') that could name more specific operations.

Suggestions

Consider naming the concrete authoring actions more specifically (e.g. 'annotate with @deprecated, strikethrough the docs heading, add a Deprecated admonition') to raise specificity.

Add a common phrasing synonym like 'mark as deprecated' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (deprecation representation in TypeScript source and documentation) and lists several concrete API surface types ('function, component, hook, type, prop, option, or other public API') plus concrete use actions ('adding, reviewing, or discussing a deprecation'), with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Reference for how deprecation of public Remotion APIs is represented in TypeScript source and documentation') and 'when' ('Use when adding, reviewing, or discussing a deprecation of ... an API that remains available') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keywords ('deprecation', 'deprecate', 'Remotion', 'function, component, hook, type, prop, option') that a user would plausibly say, with good synonym coverage of API surface kinds; a few common phrasings (e.g. 'mark as deprecated') are not present.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Remotion API deprecation representation) with distinct triggers tied to 'remains available' APIs, minimizing overlap with general code-review or migration skills.	5 / 5
	Total	18 / 20 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/deprecate-api/SKILL.md
Commit: eca4063

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.