AC miao-vision
Create a self-contained Miao Vision artifact when the user explicitly invokes $miao-vision and supplies an article URL or local Markdown/text for an infographic, or local Markdown/text and optional CSV, TSV, XLSX, or JSON data for an HTML/PDF report, single-page data poster, or browser deck. Also validate a user-supplied Miao Vision report or deck spec. Do not trigger from isolated keywords such as chart, report, dashboard, slides, infographic, or PDF.
Create a self-contained Miao Vision artifact when the user explicitly invokes $miao-vision and supplies an article URL or local Markdown/text for an…
As a process C 56/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 87): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (miao-vision) differs from the folder (miao-vision-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 38 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 3292 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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
- -33 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 456: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.