tool-rename-deprecation

Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

Quality

85%

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

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

An actionable, well-structured skill body with executable examples, a decision table, explicit validation checkpoints, and real PR/file references. The main gap is mild repetition of the stable-id rule and a single-file layout that is slightly long for its scope.

Suggestions

Consolidate the stable-id/name rule into a single canonical statement (e.g., in Step 1) and reference it from the Regression Check and Anti-patterns instead of restating it three times.

Move Real Examples and the longer Anti-patterns into a references/ file, leaving SKILL.md as a tighter overview that links out, to improve both conciseness and progressive_disclosure.

Consider adding a one-line automated check command (e.g., a grep/ripgrep snippet) to the Regression Check so the verification is directly runnable rather than described.

Dimension	Reasoning	Score
Conciseness	Dense and assumption-respecting (exact field names, source-file paths, PR numbers, no concept padding); held back from 5 by repeated restatements of the stable-id/name rule across Step 2, Regression Check, and Anti-patterns.	4 / 5
Actionability	Provides copy-paste-ready TypeScript and jsonc examples, a concrete decision table mapping entity to registration/name field/legacy array/stable ID, and real example renames and PRs covering the common cases.	5 / 5
Workflow Clarity	Clear 4-step procedure plus a separate numbered Regression Check with explicit validation checkpoints ('Verify the old toolReferenceName value appears...', 'Don't assume — check the actual array', confirm checks 1-3), appropriate for a registry-affecting skill.	5 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in one well-organized ~145-line file with clear sections, a table, and external PR/source links; not a 5 because some detail (Real Examples, expanded Anti-patterns) could be split into a reference file and the file runs a bit long for a single-page skill.	4 / 5
	Total	18 / 20 Passed

Description

85%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 specific, well-scoped description that explicitly covers both what the skill does and when to run it, with concrete identifiers and natural trigger terms. Its only limitation is that the 'what' is essentially one action repeated across contexts, keeping specificity just below maximal.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete items (legacyToolReferenceFullNames, legacyFullNames, toolReferenceName, referenceName) tied to one core action (preserve backward compatibility); not a full 5 because the action set is essentially a single preserve-via-legacy-array operation rather than multiple distinct actions.	4 / 5
Completeness	Explicitly answers both 'what' (ensure renamed tool references preserve backward compatibility; covers legacyToolReferenceFullNames and legacyFullNames) and 'when' ('Use when renaming...', 'Run on ANY change to tool registration code') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural developer trigger phrases ('renaming a toolReferenceName', 'tool set referenceName', 'ANY change to tool registration code'); good coverage but a few synonymous phrasings a user might say are absent.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche (tool-rename backward compat in a codebase) with distinct, narrow triggers; minimal risk of firing for an unrelated skill.	5 / 5
	Total	18 / 20 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: posit-dev/positron
Path: .github/skills/tool-rename-deprecation/SKILL.md
Commit: 990dde5

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.