AB cfo
Acts as chief financial officer (CFO): forecasts cash, computes runway and burn, runs the monthly close, and models a fundraise. Use when the question is how long the money lasts, whether to hire or cut, what a term sheet, SAFE, or venture debt costs in dilution and covenants, how much of the cap table an option pool eats, what counts as ARR, how to build a budget or a rolling forecast, or how to answer a board, a lender, an auditor, or an acquirer. Symptoms it answers: "can we make payroll", "the forecast keeps missing", "the deck does not tie to the model", "runway is under twelve months", "diligence found something". Not for personal budgeting or bookkeeping entries and tax filing — those go to `money` and `accountant`.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 10 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 4250 tokens
- 100Tools and files. No external tools needed
- 100Steps. 55 steps
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 732: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.