eol-message

Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan without creating avoidable confusion.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced messaging skill whose inline templates and examples make it directly usable. Its weaknesses are verbosity from duplicated sections and broken bundle references that point to files not present in the skill directory.

Suggestions

Consolidate redundancy: the Key Concepts 9-part framework is re-expanded in Application Steps 1-7, and the Anti-Patterns and Common Pitfalls sections overlap (business-centric rationale, vague timeline, defensive tone appear in both) — merge each pair into a single treatment.

Resolve progressive disclosure: either ship template.md and examples/sample.md in the bundle so the "Use template.md" / "See examples/sample.md" references resolve, or remove those references and keep the already-inline templates as the canonical source.

Trim explanatory prose Claude already knows (the Why-This-Works bullets, crisis-communication best practices, and the verbatim repeat of the intent in the Purpose section) to reduce token cost without losing the actionable templates.

Dimension	Reasoning	Score
Conciseness	The ~360-line body carries real redundancy: the Purpose repeats the intent verbatim, the Key Concepts 9-part framework is re-expanded across Application Steps 1-7, and the Anti-Patterns and Common Pitfalls sections overlap heavily, so it could be tightened despite being accurate and structured.	2 / 3
Actionability	Each step provides a fill-in template with bracketed placeholders plus a concrete worked example (Company Context, Announcement, Rationale, Customer Impact, Transition Solution, Support, Timeline, CTA), giving copy-paste-ready guidance for an instruction-only skill.	3 / 3
Workflow Clarity	Steps 1-7 are explicitly numbered and sequenced, with a context-gathering gate ("Don't send the message until you have a complete transition plan") and timeline quality checks serving as checkpoints; this non-destructive drafting workflow is clearly ordered.	3 / 3
Progressive Disclosure	References to template.md and examples/sample.md are signaled but the bundle directories (references/, scripts/, assets/) are absent, so those paths dangle; the full templates are instead inline, fitting the references-present-but-not-resolving / content-inline anchor.	2 / 3
	Total	10 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states the skill's purpose and gives an explicit "Use when" trigger for a well-scoped niche. Its main weakness is trigger-term coverage, which leans on "EOL" and "retiring" while omitting frequent synonyms like sunset, deprecate, and discontinue.

Dimension	Reasoning	Score
Specificity	"Write a clear, empathetic EOL announcement with rationale, customer impact, and next steps" names the domain plus multiple concrete deliverable components, matching the multiple-specific-actions anchor rather than the single-domain score-2 example.	3 / 3
Completeness	It states what ("Write a clear, empathetic EOL announcement...") and an explicit when ("Use when retiring a product, feature, or plan..."), clearly answering both with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes "EOL" and "retiring a product, feature, or plan", but omits common natural variations users also say (sunset, deprecate, discontinue, end-of-life), fitting the some-keywords-but-missing-variations anchor.	2 / 3
Distinctiveness Conflict Risk	The EOL/sunset niche with "retiring a product, feature, or plan" triggers is a clear, narrow scope unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/eol-message/SKILL.md
Commit: 9971018

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.