CC navigate
Pick the next work in an epic or bead graph; closed is not proven. Use when: asked what is next or whether an epic is done.
Pick the next work in an epic or bead graph; closed is not proven.
As a process C 51/100 · Has gaps — References files that are not bundled: ../plan/SKILL.md, ../orchestrate/SKILL.md, ../rpi/SKILL.md
ProcedureAI and agentsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: agentops
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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
missing-refreference to a missing file: ../plan/SKILL.md - warning
missing-refreference to a missing file: ../orchestrate/SKILL.md - warning
missing-refreference to a missing file: ../rpi/SKILL.md - warning
missing-refreference to a missing file: ../validate/SKILL.md - warning
missing-refreference to a missing file: ../domain/SKILL.md - warning
missing-refreference to a missing file: ../validate/SKILL.md - note
frontmatter-keyunknown frontmatter key "practices" - note
frontmatter-keyunknown frontmatter key "hexagonal_role" - note
frontmatter-keyunknown frontmatter key "consumes" - note
frontmatter-keyunknown frontmatter key "produces" - note
frontmatter-keyunknown frontmatter key "context_rel" - note
frontmatter-keyunknown frontmatter key "skill_api_version" - note
frontmatter-keyunknown frontmatter key "output_contract"
Process rating: all ten parameters 51/100
Will not run. References files that are not bundled: ../plan/SKILL.md, ../orchestrate/SKILL.md, ../rpi/SKILL.md
- 0Tools and files. 6 referenced file(s) missing: ../plan/SKILL.md, ../orchestrate/SKILL.md, ../rpi/SKILL.md
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2304 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 tags): a typed call is more reliable
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 123: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.