eol-checklist

Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item. Use when the decision to retire is made and you need the operational plan.

Quality

84%

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

81%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.

A well-structured, actionable instruction skill with a clear gated workflow and strong anti-pattern guidance. The main gap is that the inline example references point to files absent from this bundle, weakening progressive disclosure despite otherwise good organization.

Suggestions

Either include the referenced examples/sample.md and examples/sample-industrial.md files in the bundle, or inline a condensed example checklist so the guidance is self-contained.

Trim the 'Why the owner is mandatory' rationale and any Pitfall prose that restates knowledge Claude already has, to tighten conciseness toward a 5.

If the sibling eol-* skills are not co-located in this bundle, note that their links are external references rather than presenting them as resolvable paths.

Dimension	Reasoning	Score
Conciseness	Mostly lean with tight tables and the sticky-note rule, but some rationale prose ('Why the owner is mandatory') and the Pitfalls section restate concepts Claude already grasps and could be trimmed.	4 / 5
Actionability	The 5-step Application, the 4-8-word/verb/owner rule, and the 'four things sunsets strand' list give concrete, executable guidance; as an instruction-only skill no code is required, but the concrete example outputs live in referenced files rather than inline.	4 / 5
Workflow Clarity	A clearly sequenced five-step build with explicit validation signals ('If you can't name an approver, the gate isn't real', 'Never default to Level 3', invented-date warnings) functioning as feedback checkpoints.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep references, but the cited example files (examples/sample.md, examples/sample-industrial.md) and sibling-skill SKILL.md paths are not present in the bundle, so several navigation links resolve to nothing.	4 / 5
	Total	17 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states both the deliverable and the trigger condition, with good natural-language keywords and a distinct niche. It could enumerate a few more discrete actions to reach top specificity, but is otherwise well above the midpoint.

Dimension	Reasoning	Score
Specificity	Names the domain ('phase-gated EOL checklist') and several concrete attributes ('sized to the sunset', 'named owner on every item'), but stops short of an exhaustive multi-verb enumeration that would warrant a 5.	4 / 5
Completeness	Explicitly answers both what ('Build a phase-gated EOL checklist sized to the sunset, with a named owner on every item') and when ('Use when the decision to retire is made and you need the operational plan') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes natural user language ('EOL checklist', 'sunset', 'retire', 'operational plan') that users would plausibly say, with only minor synonym/file-extension breadth missing.	4 / 5
Distinctiveness Conflict Risk	The 'phase-gated EOL checklist with owners' framing carves a clear niche distinct from adjacent EOL skills, with low conflict risk; voice is correctly third person.	5 / 5
	Total	18 / 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: 5 suspicious	Warning

	Total	14 / 16 Passed

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

Reviewed: 1 day 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.