CD html-ppt-zhangzara-grove
A municipal urban-tree-canopy policy proposal — the public need, the evidence, the options, and the funding decision. Built as a decision-grade policy briefing deck for city council, agency reviewers.
A municipal urban-tree-canopy policy proposal — the public need, the evidence, the options, and the funding decision.
As a process D 47/100 · Unfinished process — References files that are not bundled: LICENSE, assets/deck-stage.js
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: LICENSE - warning
missing-refreference to a missing file: assets/deck-stage.js - note
frontmatter-keyunknown frontmatter key "en_name" - note
frontmatter-keyunknown frontmatter key "zh_name" - note
frontmatter-keyunknown frontmatter key "en_description" - note
frontmatter-keyunknown frontmatter key "zh_description" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "od"
Process rating: all ten parameters 47/100
- 0Tools and files. 2 referenced file(s) missing: LICENSE, assets/deck-stage.js
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 675 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)
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.