BC infer-completion-criteria
Infer measurable completion criteria for an agent-loop task from project docs, code, and AIWG standards when the user has not supplied --completion explicitly
Infer measurable completion criteria for an agent-loop task from project docs, code, and AIWG standards when the user has not supplied --completion explicitly
As a process C 66/100 · Has gaps — References files that are not bundled: ../../docs/hitl-authorization.md
The same skill appears in 1 more place: aiwg
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../docs/hitl-authorization.md - note
frontmatter-keyunknown frontmatter key "namespace" - note
frontmatter-keyunknown frontmatter key "aliases" - note
frontmatter-keyunknown frontmatter key "commandHint" - note
edit-residuethe text marks something as outdated (lines 19, 222, 318): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 66/100
- 0Tools and files. 1 referenced file(s) missing: ../../docs/hitl-authorization.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4174 tokens
- 100Steps. 34 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +1No license
- +2Single-language instructions
- +3Description length 158: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.