tool-rename-deprecation Skill
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. Published by microsoft in vscode.
Decision snapshot
Is this a fit?
Developers using vscode, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is tool-rename-deprecation Skill?
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. Published by microsoft in vscode. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using vscode
Declared skill metadata
- Source file: .github/skills/tool-rename-deprecation/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use tool-rename-deprecation Skill
- Use it for developers using vscode.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/tool-rename-deprecation/SKILL.md
What it does
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.
Skill instructions
Tool Rename Deprecation When a tool or tool set reference name is changed, the old name must always be added to the deprecated/legacy array so that existing prompt files, tool configurations, and saved references continue to resolve correctly. When to Use Run this skill on any change to built-in tool or tool set registration code to catch regressions: - Renaming a tool's toolReferenceName - Renaming a tool set's referenceName - Moving a tool from one tool set to another (the old toolSet/toolName path becomes a legacy name) - Reviewing a PR that modifies tool registration — verify no legacy names were dropped Procedure Step 1 — Identify What Changed Determine whether you are renaming a tool or a tool set, and where it is registered: | Entity | Registration | Name field to rename | Legacy array | Stable ID (NEVER change) | |--------|-------------|---------------------|-------------|-------------------------| | Tool (IToolData) | TypeScript | toolReferenceName | legacyToolReferenceFullNam
Verified compatibility and discovery
Frequently asked questions
What is tool-rename-deprecation?
tool-rename-deprecation is a open-source AI agent skill with Copy skill directory. Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier.
Who is tool-rename-deprecation best for?
tool-rename-deprecation is best for reusing agent instructions, scripts, and references.
How do I install tool-rename-deprecation?
Install or run tool-rename-deprecation using Copy skill directory. Check tool-rename-deprecation for the latest setup command.
Is tool-rename-deprecation actively maintained?
tool-rename-deprecation may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
