CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-deprecation-usage

Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools. Use this skill whenever asked to assess removal readiness for deprecated CDS APIs, investigate the blast radius of removing a deprecated component or hook, check Sourcegraph for customer usage of deprecated exports, or help the team decide which deprecated APIs are safe to remove in the next major version. Always invoke when asked to "audit deprecated APIs", "check Sourcegraph for deprecated usage", "find usages of deprecated exports", "analyze deprecation impact", or any similar request involving CDS deprecations and customer adoption.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 body delivers highly concrete, executable guidance — exact script command, exact Sourcegraph regexes, and precise output formats with a worked URL example — and is appropriately lean. However, two truncated instructions break the workflow mid-sentence, the referenced script is missing from the bundle, the heading hierarchy is inconsistent, and there are no validation checkpoints for batch audits.

Suggestions

Complete the two truncated instructions: the dangling "Follow the" sentence after the Objective and "Do not attempt to search if you do not have the information to..." in section 3 — both currently leave the reader with unfinishable steps.

Bundle the referenced scripts/findDeprecations.mjs in the skill's scripts/ directory (or inline the command's expected behavior), and fix the heading hierarchy so sections 1–4 are all H2.

Add validation/verification steps for comprehensive audits: what to do on zero or ambiguous hits, how to sanity-check query results, and when to re-run or report uncertainty before presenting usage counts as decision input.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — exact queries, a script command, and output formats with no tutorials on concepts Claude already knows. Minor trimming is possible: the objective's stakes sentence ("This information should be as accurate... to inform decisions") is soft padding, and the URL-encoding example is verbose, placing it at the 4 anchor rather than a fully token-optimal 5.

4 / 5

Actionability

Mostly executable guidance: the exact command "yarn node scripts/findDeprecations.mjs --json", copy-paste Sourcegraph regexes with NAME_HERE/PROP_HERE substitution, and a concrete output table spec with a fully worked example URL. It falls short of 5 because two instructions are truncated mid-sentence ("Follow the" and "Do not attempt to search if you do not have the information to"), and the referenced scripts/findDeprecations.mjs is not bundled, leaving minor but real execution gaps.

4 / 5

Workflow Clarity

A numbered sequence is present (scope → deprecation type → Sourcegraph search → structured output) with a useful guard ("Only attempt to search for one deprecation at a time"), but checkpoints are missing or implicit: no verification of search results, no handling of zero/ambiguous hits, and one checkpoint instruction is cut off mid-sentence. A comprehensive audit is also a batch operation, and per the rubric cap, missing validation steps in batch workflows cap this at 3.

3 / 5

Progressive Disclosure

The four sections give the body some structure, but organization is inconsistent (section 2 uses an H3 nested under section 1's H2, and a dangling "Follow the" sentence sits between sections), and the body references paths that are not part of the bundle (scripts/findDeprecations.mjs with no scripts/ directory, plus an external .claude/skills path). References exist but are not clearly signaled against an actual bundle structure, matching the 3 anchor.

3 / 5

Total

14

/

20

Passed

Description

95%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 strong description: third-person, concrete about the mechanism (Sourcegraph MCP search), and rich with explicit quoted trigger phrases covering both the "what" and "when" in plain terms. Its only weakness is that the enumerated capabilities are variations of one core audit task, slightly limiting the breadth implied by the top specificity anchor.

DimensionReasoningScore

Specificity

The description names concrete actions — "Audits how often deprecated CDS exports are actively used", "assess removal readiness", "investigate the blast radius", "check Sourcegraph for customer usage" — all anchored to a specific tool ("Sourcegraph MCP search tools"). It falls just short of the 5 anchor because the listed actions are largely overlapping restatements of a single audit task rather than comprehensive distinct capabilities.

4 / 5

Completeness

Both questions are explicitly answered: "what" via "Audits how often deprecated CDS exports are actively used in customer codebases using Sourcegraph MCP search tools", and "when" via both "Use this skill whenever asked to..." and "Always invoke when asked to..." with concrete trigger phrases. This matches the anchor for clearly and explicitly answering both what and when.

5 / 5

Trigger Term Quality

It explicitly quotes natural trigger phrases users would say — "audit deprecated APIs", "check Sourcegraph for deprecated usage", "find usages of deprecated exports", "analyze deprecation impact" — plus paraphrases like "investigate the blast radius" and "safe to remove in the next major version". Coverage of synonyms and natural phrasings is comprehensive, matching the top anchor; there are no missing common variations evident in this domain.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly delimited by domain-specific terms — CDS deprecations, Sourcegraph, customer codebase usage audits, removal readiness — giving it distinct triggers and minimal conflict risk with generic skills. It does not disambiguate against the sibling deprecate-cds-api skill, but its triggers are all audit/usage-analysis oriented, so overlap risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

coinbase/cds

Path

.claude/skills/research-deprecation-usage/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.