AC hsa-receipt-vault
Maintains a ledger of HSA-qualified medical expenses paid out of pocket (not reimbursed from the HSA), each with date, amount, provider, description, and a path to the scanned receipt. Tracks the running unreimbursed total — the amount of HSA balance the household can pull tax-free at any future date — and validates each candidate against IRS-qualified-expense categories. Use when a new medical receipt arrives, when totaling future tax-free HSA reimbursements, when planning a deferred reimbursement, or when user mentions HSA receipt vault, qualified medical expenses, or HSA shoebox strategy.
Maintains a ledger of HSA-qualified medical expenses paid out of pocket (not reimbursed from the HSA), each with date, amount, provider, description, and a…
As a process C 64/100 · Has gaps — weak spots: when it triggers, failures and branches, 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: 1. 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 64/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 23 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1934 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 598: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 23 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.