AA statute-guide
First-pass framework for reading, interpreting, and structuring statutory analysis of US federal, state, and local law. Produces draft analysis for attorney review — not legal advice. Use this skill whenever the user references a specific US statute, regulation, ordinance, or rule by citation, asks "what does [statute X] require," asks for compliance scoping, applicability thresholds, requirement extraction, exemption analysis, definitional analysis, federal preemption analysis, or multi-state comparison — even if they don't explicitly ask for "statutory analysis." Halts and asks for missing inputs rather than guessing. Out of scope for non-US law.
First-pass framework for reading, interpreting, and structuring statutory analysis of US federal, state, and local law.
As a process A 80/100 · Runs to the end — weak spots: consistency, running it twice, progress reporting
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6327 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "jurisdiction"
Process rating: all ten parameters 80/100
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (statute-guide) differs from the folder (statute-analyzer-rafal-fryc)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6327 tokens
- 100Tools and files. No external tools needed
- 100Steps. 77 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- low 24 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 656: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 77 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.