AB ar-collections-agent
Accounts Receivable (AR) collections workflow automation for accounting firms and finance teams. Use when you need to: (1) identify overdue invoices and aged AR buckets (30/60/90/120+ days), (2) draft escalating collection emails or call scripts, (3) generate AR aging reports and DSO calculations, (4) prioritize collection targets by balance and risk, (5) track payment promises and follow-up schedules, (6) calculate bad debt reserves or write-off recommendations, or (7) produce client-ready AR health dashboards. Works with QBO exports, CSV invoice data, or direct QBO API. NOT for: initiating legal action or filing liens (escalate to attorney), sending external emails without approval, accessing client QBO accounts without explicit write authorization, or PTIN-backed tax services.
As a process B 72/100 · Nearly there — weak spots: 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Accounts Receivable (AR) collections workflow automation for accou… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 72/100
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 4 mutating operations with no state check
- 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
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 961 tokens
- 100Progress reporting. Reports progress
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 790: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 36 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.