AF Tax Package Preparation
Year-end tax package preparation pipeline for QBO-connected clients. Generates a 9-tab Excel workbook: Tax Summary, Income, Expenses, Depreciation, 1099s, State Nexus, Crypto (Form 8949), Checklist, and CDC. Reads client SOP for entity type, crypto wallet, vehicle, home office, and FBAR flags. Maps every line item to IRS form and schedule codes.
As a process F 52/100 · Will not run — References files that are not bundled: scripts/pipelines/tax-package-prep.py
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
missing-refreference to a missing file: scripts/pipelines/tax-package-prep.py - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: scripts/pipelines/tax-package-prep.py
- 0Failures and branches. Linear process with no failure handling
- 40Consistency. Frontmatter name (Tax Package Preparation) differs from the folder (tax-package-prep)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 61 steps
- 100Execution cost. Instruction body is 1892 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 15 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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 347: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.