BF cash-flow-forecast
Build a 13-week rolling cash flow forecast from QBO data with 3-scenario modeling (base, upside, downside). Pulls Balance Sheet and CF Statement for starting cash and trend baseline. Use when a client needs cash runway projection, burn rate analysis, or scenario-based liquidity planning. NOT for annual budgets, P&L variance analysis, or bank reconciliation.
Build a 13-week rolling cash flow forecast from QBO data with 3-scenario modeling (base, upside, downside).
As a process F 49/100 · Will not run — References files that are not bundled: scripts/pipelines/cash-flow-forecast.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: 1. 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 8, column 28: - GlowLabs-type clients: runway/burn emphasis; SB Paulson-type: interest expe… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: scripts/pipelines/cash-flow-forecast.py - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "updated"
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: scripts/pipelines/cash-flow-forecast.py
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 60 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1685 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 16 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 359: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 60 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: 70.