CD eol-readiness-advisor
Run a go/no-go assessment for retiring a product or feature, then right-size the effort. Use when someone says "we should probably kill this" and nobody has made the call.
Run a go/no-go assessment for retiring a product or feature, then right-size the effort.
As a process D 45/100 · Unfinished process — References files that are not bundled: ../workshop-facilitation/SKILL.md, ../lifecycle-play-advisor/SKILL.md, ../eol-message/SKILL.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5079 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../workshop-facilitation/SKILL.md - warning
missing-refreference to a missing file: ../lifecycle-play-advisor/SKILL.md - warning
missing-refreference to a missing file: ../eol-message/SKILL.md - warning
missing-refreference to a missing file: ../incoming-request-advisor/SKILL.md - warning
missing-refreference to a missing file: ../stakeholder-map/SKILL.md - warning
missing-refreference to a missing file: ../business-health-diagnostic/SKILL.md - note
frontmatter-keyunknown frontmatter key "intent" - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "theme" - note
frontmatter-keyunknown frontmatter key "best_for" - note
frontmatter-keyunknown frontmatter key "scenarios" - note
frontmatter-keyunknown frontmatter key "estimated_time" - note
edit-residuethe text marks something as outdated (lines 35, 288): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 45/100
- 0Tools and files. 6 referenced file(s) missing: ../workshop-facilitation/SKILL.md, ../lifecycle-play-advisor/SKILL.md, ../eol-message/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 12 mutating operations with no state check
- 65Failures and branches. 3 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5079 tokens
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 171: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.