deprecation-notice-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill deprecation-notice-generatorDeprecation Notice Generator - Auto-activating skill for Technical Documentation. Triggers on: deprecation notice generator, deprecation notice generator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks any concrete actions, natural user keywords, and explicit usage conditions. The only slight positive is that 'deprecation notice' is a somewhat specific domain term.
Suggestions
Add specific actions the skill performs, e.g., 'Generates deprecation notices for APIs, features, and software versions. Creates migration guides, sunset timelines, and replacement recommendations.'
Include a 'Use when...' clause with natural trigger terms: 'Use when deprecating features, sunsetting APIs, announcing end-of-life, creating EOL notices, or documenting version removals.'
Remove the duplicate trigger term and expand with variations users would naturally say: 'deprecate', 'sunset', 'end of life', 'EOL', 'phase out', 'retiring feature'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Deprecation Notice Generator') without describing any concrete actions. There's no explanation of what it actually does - no verbs describing capabilities like 'generates', 'formats', 'creates templates', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'deprecation notice generator' repeated twice, which is the skill name itself. Missing natural user phrases like 'deprecate', 'sunset', 'end of life', 'EOL', 'deprecated API', 'version removal', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'deprecation notice' is fairly specific to a niche use case, which provides some distinctiveness. However, the vague description could still overlap with general documentation or API documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty placeholder that provides no actual guidance on generating deprecation notices. It consists entirely of generic boilerplate text that could apply to any skill topic. There is no actionable content, no examples, no templates, and no concrete information about what a deprecation notice should contain or how to create one.
Suggestions
Add a concrete deprecation notice template with required fields (deprecated item, deprecation date, removal date, migration path, replacement API/feature)
Include executable code examples showing how to generate notices in common formats (markdown, JSDoc, OpenAPI annotations)
Provide a clear workflow: 1) Identify deprecated item, 2) Determine timeline, 3) Document migration path, 4) Generate notice, 5) Validate completeness
Add example input/output pairs showing what information goes in and what the generated notice looks like
| 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 meaningless filler that waste tokens without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually generate deprecation notices. No code examples, no templates, no specific formats or fields to include. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating a deprecation notice, no validation checkpoints, and no process to follow. The skill claims to provide 'step-by-step guidance' but delivers none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to templates, examples, or related documentation files that would help with actual deprecation notice generation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.