eol-message

Write a right-sized EOL announcement — brief notice through full phased comms — with rationale, customer impact, and next steps. Use when retiring a product, feature, or plan.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/eol-message/SKILL.md

Quality

Content

60%Weight 40%Scale 1-5

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

The skill delivers strong, actionable EOL-messaging guidance with a clear sequenced workflow and useful sizing framework. Its main weaknesses are verbosity from repeated restatements and a progressive-disclosure gap where referenced files (template.md, examples/) do not exist in the bundle.

Suggestions

Provide the referenced bundle files (template.md, examples/sample.md, examples/sample-industrial.md) so the in-text links resolve, or inline only what is needed and drop the references.

Consolidate the duplicated material — Anti-Patterns/Common Pitfalls and Purpose/Why This Works/Description — into a single concise treatment to reduce token cost.

Add an explicit 'validate the draft against the sticky-note rule, then iterate' checkpoint in the drafting steps to lift workflow clarity into the top anchor.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and adds genuine domain value (gates, transition paths, sizing table), but at ~440 lines it repeats concepts across sections — Purpose restates the description, 'Why This Works' restates the framework, and Common Pitfalls largely restate the Anti-Patterns — which could be tightened.	3 / 5
Actionability	It provides concrete, fill-in templates with worked Fieldlight examples for each section and specific quality checks (lead-time ranges, gate wording, data-export deadlines); minor gaps are that some blocks are template skeletons rather than fully worked guidance.	4 / 5
Workflow Clarity	Steps 1–8 are clearly sequenced with an explicit input-gathering gate and a 'don't send until you have a transition plan' checkpoint, plus a final sticky-note validation and next-step menu; it stops short of a 5 because the drafting steps lack explicit validate-and-iterate loops for the risky case of an incomplete plan.	4 / 5
Progressive Disclosure	No bundle files (references/, scripts/, assets/) are present, yet the body references template.md, examples/sample.md, examples/sample-industrial.md, and two sibling skills — none of which exist in this bundle — so the signaling points at missing material and the bulk of guidance is inlined rather than split out.	2 / 5
	Total	13 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

The description is strong: it pairs concrete, specific capabilities with an explicit 'Use when' trigger and occupies a distinct niche. Its only minor weakness is slightly relying on 'EOL' terminology rather than the full range of layperson synonyms a user might say.

Suggestions

Add a natural-synonym trigger term such as 'sunset' or 'discontinuing' alongside 'retiring' so the description matches the full range of phrasings a user might say.

Consider including the affected scope (e.g. 'retiring a product, feature, plan, or hardware line') to broaden trigger coverage to scenarios named in the body.

Dimension	Reasoning	Score
Specificity	Names the domain (EOL announcement) plus concrete, differentiated actions — 'brief notice through full phased comms,' 'rationale, customer impact, and next steps,' and right-sizing the message — giving comprehensive, specific coverage rather than vague process language.	5 / 5
Completeness	Explicitly answers both 'what' ('Write a right-sized EOL announcement… with rationale, customer impact, and next steps') and 'when' ('Use when retiring a product, feature, or plan') with concrete trigger guidance.	5 / 5
Trigger Term Quality	Includes natural trigger phrasing users would say ('retiring a product, feature, or plan,' 'EOL announcement') with good coverage, though it leans on 'EOL' jargon and lacks a few common layperson synonyms like 'sunset' or 'discontinuing.'	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (end-of-life communications sized to blast radius) with triggers unlikely to fire for adjacent skills, and 'Use when retiring a product, feature, or plan' is distinct from general announcement or positioning skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 6 suspicious	Warning

	Total	14 / 16 Passed

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

Reviewed: 5 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.