AC preact-docs-v10-29-7
Documentation reference for Preact v10.29.7. Use to look up the correct syntax, hooks, components, and API behavior for Preact. Not a coding tutor — only a reference lookup. Example triggers: "How does useState() work in Preact?", "What props does render() accept?", "What's the difference between preact and preact/compat?"
Documentation reference for Preact v10.29.7. Use to look up the correct syntax, hooks, components, and API behavior for Preact. Not a coding tutor — only a…
As a process C 58/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 324 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "required_commands" - note
frontmatter-keyunknown frontmatter key "required_environment_variables" - note
frontmatter-keyunknown frontmatter key "required_privileges"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Steps. 42 steps, 4 vague phrases
- 60Consistency. The Hermes dialect needs category and tags
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1909 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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 324: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.