AC skill-validation
Gunakan skill ini saat: validation" [shape=box];; > "skill-validation" [label="yes"];; > "Editing existing skill?" [label="no"];. Aktif untuk tugas terkait skill-validation."v2.0.0: Align with current ClawHub spec — trigger-style descriptions, single-line metadata JSON, folder=slug rule, progressive disclosure budget, install specs. v1.0.0: Initial checklist
Gunakan skill ini saat: validation" [shape=box];; > "skill-validation" [label="yes"];; > "Editing existing skill?" [label="no"];. Aktif untuk tugas terkait…
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected flow-seq-start at node end at line 2, column 51: description: "Gunakan skill ini saat: validation" [shape=box];; > "skill-valida… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 52/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 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
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1746 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- -214 emoji in the instructions: noise for the model
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 360: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.