deprecation-notice-generator
Deprecation Notice Generator - Auto-activating skill for Technical Documentation. Triggers on: deprecation notice generator, deprecation notice generator Part of the Technical Documentation skill category.
35
3%
Does it follow best practices?
Impact
93%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/deprecation-notice-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a placeholder that provides almost no useful information beyond the skill's name. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention suggest auto-generated content with no human refinement.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates deprecation notices for APIs, libraries, and features, including sunset timelines, migration paths, and replacement recommendations.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user needs to write a deprecation notice, sunset announcement, end-of-life (EOL) communication, breaking change notification, or migration guide.'
Include varied natural keywords users might say, such as 'deprecate', 'sunset', 'EOL', 'end of life', 'breaking change', 'removal notice', 'migration path'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Deprecation Notice Generator') and its category ('Technical Documentation') but does not describe any concrete actions like 'generates deprecation notices for APIs', 'creates migration guides', or 'formats sunset timelines'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title and completely lacks a 'when should Claude use it' clause with explicit triggers. There is no 'Use when...' guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('deprecation notice generator'). It lacks natural user phrases like 'deprecate', 'sunset', 'end-of-life', 'EOL', 'migration notice', 'breaking change announcement', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'deprecation notice' is somewhat niche and unlikely to conflict with many other skills, but the lack of specificity about what exactly it generates (API deprecation? library deprecation? feature deprecation?) and the generic 'Technical Documentation' category reduce its distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell—a boilerplate template that describes what a deprecation notice generator skill would do without actually providing any content. It contains no executable code, no deprecation notice templates, no formatting guidelines, and no concrete instructions. It fails on every dimension because it is purely self-referential meta-content with no actionable substance.
Suggestions
Add a concrete deprecation notice template with examples (e.g., a markdown template showing version, sunset date, migration path, and replacement API)
Include executable code or a step-by-step workflow for generating deprecation notices, such as a script that takes API endpoint details and outputs a formatted notice
Provide at least 2-3 real input/output examples showing different deprecation scenarios (e.g., API endpoint removal, library version sunset, feature deprecation)
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actual instructional content that teaches how to create deprecation notices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill supposedly does without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information about 'deprecation notice generator' without adding substance. | 1 / 3 |
Actionability | There is zero actionable content—no code, no templates, no examples of deprecation notices, no commands, no concrete steps. The skill describes itself rather than instructing Claude on how to generate deprecation notices. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The 'Capabilities' section vaguely mentions 'step-by-step guidance' but none is actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no meaningful structure. There are no references to detailed files, no examples section, and no navigation to deeper content. The sections that exist are all superficial and redundant. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
4dee593
- 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.