CC eol-internal-enablement
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
As a process C 50/100 · Has gaps — References files that are not bundled: ../eol-message/SKILL.md, ../eol-stakeholder-sequence/SKILL.md, ../eol-checklist/SKILL.md
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../eol-message/SKILL.md - warning
missing-refreference to a missing file: ../eol-stakeholder-sequence/SKILL.md - warning
missing-refreference to a missing file: ../eol-checklist/SKILL.md - warning
missing-refreference to a missing file: ../eol-readiness-advisor/SKILL.md - warning
missing-refreference to a missing file: ../incoming-request-advisor/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 31): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 50/100
- 0Tools and files. 5 referenced file(s) missing: ../eol-message/SKILL.md, ../eol-stakeholder-sequence/SKILL.md, ../eol-checklist/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. 3 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 42 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2817 tokens
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 174: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.