deprecation-notice-generator

Quick Review

The skill has clear structure and metadata but severely lacks substance. The description is circular and generic, merely repeating 'deprecation notice generator' without explaining what deprecation notices are, what makes a good one, or how this skill generates them. Task knowledge is minimal—no templates, examples, structure guidelines, or best practices for writing deprecation notices (timeline, migration paths, severity levels, etc.). A CLI agent would struggle to invoke this meaningfully beyond the trigger phrase. The skill could be novel if fully implemented (automating standardized deprecation notices across codebases/APIs), but in its current form it's a skeleton. To improve: add deprecation notice templates, fields to collect (deprecated feature, replacement, timeline, migration guide), output formats, and concrete examples.