CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deprecate-cds-api

Deprecates a CDS component, hook, or other exported symbol with consistent JSDoc, version tags, and docsite metadata across every public export path (web, mobile, common, visualization), not only the original package. Use whenever the user asks to deprecate a CDS component or API, mark something as deprecated, add @deprecated / @deprecationExpectedRemoval, or update deprecation warnings in apps/docs metadata under components or hooks (webMetadata.json / mobileMetadata.json / metadata.json). Also use when replacing a component or hook and sunsetting the old one. Always finish by running `yarn nx run <project>:lint` on modified packages so `internal/deprecated-jsdoc-has-removal-version` passes.

Quality

94%

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

88%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 strong, highly actionable body: complete code templates, exact commands, a sequenced workflow with validation and a feedback loop, and a closing checklist. Its main weakness is repetition of the removal-major policy and the absence of any progressive-disclosure file split for a body of this length.

Suggestions

Consolidate the full-major-undisturbed policy into a single authoritative statement (Step 2) and reference it from Inputs/Step 1 instead of restating it four times.

Move the docsite metadata details (component vs. hook 'warning' wording and examples) into a references/metadata.md file and keep a one-line pointer in SKILL.md.

Trim duplicated version-table commentary ('Never suggest or apply v(M+1)' appears in both Step 2 policy and 'Choosing N') to a single caution.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete templates and no teaching of known concepts, but the full-major-undisturbed policy is restated roughly four times (Inputs, Step 1 rules, Step 2 policy/table, and 'Choosing N' plus repeated 'Do not set v<M+1>' warnings). Consolidating these statements would tighten it.

4 / 5

Actionability

Provides a complete copy-paste-ready JSDoc template with the exact required closing sentence, JSON 'warning' snippets with concrete examples, the exact lint command, and worked version examples (9.14.0 -> v11). A model can execute directly from this.

5 / 5

Workflow Clarity

Clear numbered sequence (Steps 0-6) with an upfront 'Inputs to confirm first', a verification checklist, and an explicit lint validation step with a fix-and-rerun feedback loop ('Fix any reported issues before finishing').

5 / 5

Progressive Disclosure

No bundle files exist; the skill is a single well-organized file with clear section headers and in-repo pointers to live examples. Structure is good, but the ~160-line body inlines detail (e.g., the docsite metadata section) that could be split into a reference file to keep SKILL.md as a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete third-person capabilities, explicit 'Use whenever' triggers with synonyms, named files and commands, and a clearly bounded niche. It is long but every clause carries trigger or capability information rather than padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with third-person voice: applying consistent JSDoc (@deprecated/@deprecationExpectedRemoval), version tags, docsite metadata across named export paths (web, mobile, common, visualization), and finishing with a specific lint command. Coverage is comprehensive with no generic filler.

5 / 5

Completeness

Explicitly answers both what ('Deprecates a CDS component, hook, or other exported symbol with consistent JSDoc, version tags, and docsite metadata') and when ('Use whenever the user asks to deprecate... mark something as deprecated... or update deprecation warnings') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural user phrasings ('deprecate a CDS component or API', 'mark something as deprecated', 'replacing a component or hook and sunsetting the old one') plus exact technical synonyms (tag names, metadata file names). Users would naturally say these when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CDS deprecation workflow) with distinct triggers, specific file paths (webMetadata.json, mobileMetadata.json), and a named lint rule; minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

coinbase/cds

Path

.claude/skills/deprecate-cds-api/SKILL.md

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.