deprecated-api-updater
Identify and replace deprecated API usage in source code with modern alternatives. Use when: (1) Modernizing legacy codebases, (2) Upgrading framework versions (React, Django, Spring, etc.), (3) Fixing deprecation warnings in build output, (4) Preparing for major version upgrades, (5) Ensuring code uses current best practices. Supports Python, JavaScript/TypeScript, Java, and other major languages with both AST-based detection and pattern matching for accurate identification and automated replacement with validation.
93
92%
Does it follow best practices?
Impact
90%
1.60xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the key criteria. It provides specific concrete actions, includes a comprehensive 'Use when:' clause with multiple trigger scenarios, uses natural developer terminology, and carves out a distinct niche around deprecation handling and code modernization. The description is thorough without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'identify and replace deprecated API usage', 'AST-based detection', 'pattern matching', 'automated replacement with validation'. Also specifies supported languages and frameworks. | 3 / 3 |
Completeness | Clearly answers both what (identify and replace deprecated API usage with modern alternatives, AST-based detection, pattern matching, automated replacement) AND when (explicit 'Use when:' clause with 5 specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'deprecated', 'legacy codebases', 'upgrading framework versions', 'deprecation warnings', 'version upgrades', 'React, Django, Spring', plus language names. These match how developers naturally describe these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on deprecated API replacement and modernization. The combination of 'deprecated', 'deprecation warnings', 'version upgrades', and 'legacy codebases' creates a distinct trigger profile unlikely to conflict with general code editing or refactoring skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is moderate verbosity - some sections explain concepts Claude already knows (like AST advantages) and could be tightened. The validation steps and feedback loops are particularly strong.
Suggestions
Trim explanatory text about AST vs pattern matching advantages - Claude understands these tradeoffs; just state which method is used when
Condense the 'Best Practices' section which restates workflow steps already covered; consider merging into the main workflow or removing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity, such as explaining what AST-based detection advantages are and detailed explanations of backup file handling that Claude would understand implicitly. | 2 / 3 |
Actionability | Provides fully executable bash commands, concrete Python code examples for customization, and copy-paste ready CI/CD configuration. All examples are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with explicit validation checkpoints (dry run → apply → validate with tests/linters → commit). Includes clear feedback loops for error recovery and numbered steps throughout. | 3 / 3 |
Progressive Disclosure | Well-structured with quick start at top, clear references to language-specific documentation files (python_deprecations.md, etc.), and advanced usage appropriately placed at the end. One-level-deep references are clearly signaled. | 3 / 3 |
Total | 11 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ArabelaTso/Skills-4-SE
- Commit
0f00a4f
- 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.