AC go-get-uncle-matts-hammerrr
Use only when the user explicitly names go-get-uncle-matts-hammerrr or says Go Get Uncle Matt's HAMMERRR and asks for the HAMMERRR read-only project-truth audit. Audits claims against reachable runtime behavior, config and deployment reality, tests, executable proof, installation, packaging, upgrade, and release paths. Do not use for ordinary PR review, style review, implementation, isolated debugging, generic readiness checks, or generic tech-debt scanning.
Use only when the user explicitly names go-get-uncle-matts-hammerrr or says Go Get Uncle Matt's HAMMERRR and asks for the HAMMERRR read-only project-truth…
As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/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
- 30Running it twice. 10 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 69 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1555 tokens
- 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 462: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 69 items
- +4Reference files are cited in the instructions (6 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.