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
Quality
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The repeated trigger term and boilerplate category mention add no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates deprecation notices with migration paths, sunset timelines, and alternative recommendations for APIs, features, or libraries.'
Include a 'Use when...' clause with natural trigger terms: 'Use when deprecating features, sunsetting APIs, writing EOL notices, or creating migration guides.'
Add variations of trigger terms users might naturally say: 'deprecate', 'sunset', 'end of life', 'EOL', 'phase out', 'migration notice', 'breaking change announcement'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Deprecation Notice Generator') without describing any concrete actions. There are no verbs explaining what the skill actually does - no mention of creating, formatting, writing, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('deprecation notice generator, deprecation notice generator'). This is redundant and misses natural variations users might say like 'deprecate', 'sunset', 'end of life', 'EOL notice', or 'migration warning'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'deprecation notice' is fairly specific to a particular documentation task, which provides some distinctiveness. However, the lack of detail about what distinguishes this from general documentation skills creates potential overlap. | 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 a placeholder with no actual instructional content. It describes what a deprecation notice generator skill would do without providing any concrete guidance, templates, examples, or workflows for actually creating deprecation notices. The entire content could be replaced with a single actionable template and would be more useful.
Suggestions
Add a concrete deprecation notice template with required fields (deprecated feature, deprecation date, removal date, migration path, replacement API/feature)
Include 2-3 executable examples showing different deprecation scenarios (API endpoint, library method, configuration option)
Define a clear workflow: 1) Identify deprecated item, 2) Determine timeline, 3) Write migration guide, 4) Generate notice using template, 5) Validate completeness
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual actionable instructions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about deprecation notices. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that waste tokens without adding value. | 1 / 3 |
Actionability | No concrete guidance whatsoever - no code examples, no templates, no specific format for deprecation notices. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for creating deprecation notices, no validation checkpoints, and no process to follow. The content is entirely meta-description without any actual procedure. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or templates. There's nothing to progressively disclose because there's no substantive content. | 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
0c08951
- 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.