AF client-dashboard
Generates a client-facing executive KPI dashboard from QuickBooks Online data. Produces an Excel workbook with traffic-light scoring, 6-month trend sparklines, client-specific watch items, and a CDC log tracking KPI changes month-over-month. Use after monthly close to deliver the final executive summary deliverable to clients. NOT a substitute for P&L variance analysis, not for mid-month snapshots, and not for clients without QBO integration.
As a process F 67/100 · Will not run — References files that are not bundled: scripts/pipelines/client-dashboard.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
missing-refreference to a missing file: scripts/pipelines/client-dashboard.py - note
frontmatter-keyunknown frontmatter key "updated"
Process rating: all ten parameters 67/100
- 0Tools and files. 1 referenced file(s) missing: scripts/pipelines/client-dashboard.py
- 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. 12 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1578 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 14 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 446: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 12 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.