AC fractional-cfo-playbook
Complete operational playbook for Fractional CFO engagements. Covers client onboarding financial assessment, monthly close cadence, board-ready reporting packages, cash flow management, strategic financial advisory, and engagement scope templates. Use when setting up or running a Fractional CFO service, onboarding a new client, preparing monthly CFO deliverables, or advising on financial strategy as an outsourced finance executive. NOT for: building financial models from scratch (use startup-financial-model), bookkeeping or transaction recording (use qbo-automation), tax filing preparation (PTIN-required service), or one-time financial analysis without an ongoing advisory context.
Complete operational playbook for Fractional CFO engagements.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 2. 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 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3698 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 689: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.