CtrlK
BlogDocsLog inGet started
Tessl Logo

deprecations

Use when: deprecating Primer React components or hooks. Covers source annotations, docs metadata, changesets, docs page updates, and validation for deprecations.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a concise, well-structured overview with concrete commands and clear file targets that appropriately points to deeper contributor docs. The main gap is the absence of an explicit validation feedback loop and a couple of underspecified action steps.

Suggestions

Add an explicit feedback loop in Validation, e.g., 'If lint or build fails, fix the reported issues and re-run until clean' before proceeding.

Make 'Run targeted tests' and 'Add a changeset' more concrete by giving an example test command and a sample changeset snippet.

Annotate the 'Common files' list with a few-word purpose for each path so Claude knows when to consult them.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven with specific file paths and commands, assumes Claude's competence, and contains no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides copy-paste-ready commands ('npx prettier --write <paths>', 'npx eslint --fix <paths>', 'npm run build:hooks.json -w @primer/react') and concrete file targets, but a few steps remain high-level ('Run targeted tests for the affected API when available', 'Add a changeset') without exact commands or format.

4 / 5

Workflow Clarity

Clear categorized workflow (source, docs metadata, docs content, versioning, validation) with a validation section and a priority order ('Prefer targeted validation first, then broader validation if needed'), but no explicit validate-fix-retry feedback loop or 'only proceed when valid' checkpoint.

4 / 5

Progressive Disclosure

Well-organized into clear sections and points to one-level-deep references (contributor-docs/deprecating-components.md, contributor-docs/versioning.md), but the 'Common files' section is a bare path list without guidance on when to consult each, a minor organization gap.

4 / 5

Total

17

/

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.

The description is well-constructed, explicitly pairing a 'Use when' trigger with a concrete enumeration of the deprecation workflow's coverage areas, and is tightly scoped to Primer React. It could be slightly stronger by using action verbs and adding common synonyms like 'retire' or 'phase out'.

Suggestions

Lead the 'what' clause with action verbs (e.g., 'Annotate source, update docs metadata, add changesets, update docs pages, and run validation') instead of a single 'Covers' verb.

Add natural synonyms such as 'retire' or 'phase out' alongside 'deprecating' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete coverage areas ('source annotations, docs metadata, changesets, docs page updates, and validation'), but these read as a scope enumeration under a single verb ('Covers') rather than distinct action verbs, leaving minor gaps versus a fully action-oriented list.

4 / 5

Completeness

Explicitly answers both 'what' ('Covers source annotations, docs metadata, changesets, docs page updates, and validation') and 'when' ('Use when: deprecating Primer React components or hooks') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ('deprecating Primer React components or hooks', 'deprecations'), but synonyms like 'retire', 'phase out', or 'remove' are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear Primer React-specific niche ('deprecating Primer React components or hooks') with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
primer/react
Reviewed

Table of Contents

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.