AC tax
Local-first year-round tax memory system for individuals, freelancers, and small businesses. Use when users mention tax documents, receipts, expenses, tax notices, filing preparation, missing forms, accountant meetings, or year-end organization. Captures tax-relevant facts as they happen, tracks what may be missing, and prepares CPA-ready handoff summaries. NEVER provides tax advice, legal interpretations, filing positions, or final tax calculations.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 116 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2168 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 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)
- +4No input/output examples
- -44 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 454: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 116 items
- +3Output format is stated explicitly
- +3All 10 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.