cash-flow-forecaster · onewave-ai — Claude Code skill: forecast and install
The cash-flow-forecaster Claude Code skill creates a rolling 13-week cash flow forecast from bank exports, invoices, payroll, and recurring commitments. It flags weeks when cash falls below a chosen minimum.
MIT 104 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a claude-codeWhat cash-flow-forecaster does
The skill builds a weekly cash forecast from bank or transaction exports, unpaid customer invoices, upcoming bills, payroll dates, and recurring commitments. It reviews 8–12 weeks of history to estimate spending patterns and uses customers’ past payment delays rather than invoice due dates. Variable recurring costs are marked ESTIMATE.
It produces cash-flow-13wk.csv plus a summary of each week’s opening cash, inflows, outflows, and closing cash. Weeks below the user’s minimum comfort level receive the CRUNCH label. For each crunch point, the skill lays out possible moves such as following up on a specific receivable or delaying a bill. Expected revenue is included only when the user supplies expected deals; the skill does not invent incoming payments.
The forecast needs recent bank data, open invoices, upcoming bills, payroll dates, and known recurring items. Bank and transaction exports can use .csv or .xlsx. The workflow also supports weekly updates that compare actual figures with the previous forecast.
What it helps with
- build a 13-week view of cash on hand
- spot weeks that fall below a cash minimum
- factor customer payment delays into expected receipts
- compare actual figures with last week’s forecast
Example prompts for the agent
- Build a cash forecast from
bank.csv,AR.xlsx, andAP.xlsx. - When is the next week below my cash minimum?
- Roll the forecast forward using this week’s actual payments.
How to install cash-flow-forecaster
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a claude-code2Manually: put the files in place
~/.claude/skills/cash-flow-forecaster/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cash-flow-forecaster/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a codex2Manually: put the files in place
.agents/skills/cash-flow-forecaster/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a cursor2Manually: put the files in place
.cursor/skills/cash-flow-forecaster/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cash-flow-forecaster2Manually: put the files in place
.github/skills/cash-flow-forecaster/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cash-flow-forecasterManually: put the files in place
.devin/skills/cash-flow-forecaster/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cash-flow-forecaster
How do I install cash-flow-forecaster in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cash-flow-forecaster -a claude-code. The skill file is at ~/.claude/skills/cash-flow-forecaster/SKILL.md.
What does cash-flow-forecaster do?
It builds a weekly cash flow forecast covering 13 weeks, marks weeks below the selected minimum, and lays out possible ways to address each shortfall.
What data does cash-flow-forecaster need?
It uses bank or transaction exports, unpaid customer invoices, upcoming bills, payroll dates, and known recurring items. Exports can be .csv or .xlsx.
Source text
SKILL.md · MIT
--- name: cash-flow-forecaster description: Build a 13-week rolling cash flow forecast from bank exports, AR aging, AP bills, payroll, and recurring commitments -- the report that tells a small business whether it survives the quarter. Flags the crunch weeks early enough to act. tools: Read, Glob, Grep, Write, Bash model: inherit --- # Cash Flow Forecaster Profitable businesses die of cash starvation; the 13-week forecast is the instrument that prevents it. Input: bank/transaction exports (.csv/.xlsx), open invoices (AR), upcoming bills (AP), payroll schedule, and known recurring items. Output: a week-by-week cash position with the crunch points circled. ## Workflow 1. **Establish the baseline.** Current cash across accounts (from the most recent export -- state the as-of date prominently). Reconstruct 8-12 weeks of history to learn the rhythm: payroll cadence, rent day, typical weekly card/vendor spend, revenue deposit patterns. 2. **Schedule the knowns.** Inflows: open AR placed in the week each invoice is *likely* paid -- due date plus that customer's historical lateness, not the due date printed on the invoice. Outflows: payroll (with tax deposit timing), rent, loan payments, insurance, subscriptions, credit card due dates, quarterly estimated taxes -- the ambush everyone forgets. 3. **Model the unknowns.** Recurring-but-variable spend from historical averages, labeled `ESTIMATE`. New revenue only if the user provides expected deals -- never invent pipeline. 4. **Build the forecast.** `cash-flow-13wk.csv` + summary: weekly beginning cash, inflows, outflows, ending cash. Flag every week ending below the user's minimum comfort level (ask; default one payroll cycle) as `CRUNCH`, and the first crunch week is the headline. 5. **Scenario the levers.** For each crunch: what closes the gap -- which specific AR to chase this week (pairs with `cowork-invoice-chaser`), which AP can slide two weeks without damage, where the line of credit covers, what the owner draw pause buys. Concrete moves with amounts, not advice-shaped sentences. ## Rules - Payment behavior beats due dates: a net-30 customer who pays in 55 days forecasts at 55. - Never fabricate inflows. Hope is not a week-9 deposit; unconfirmed revenue stays out or sits in a clearly separated optimistic scenario. - Estimates are labeled and totaled separately so the user can see how much of the forecast is soft. - Weekly granularity, not monthly -- a month that nets positive can contain a week that bounces payroll. - The as-of date and data gaps are stated up front; a forecast built on a two-week-old balance says so. - Re-run weekly: roll the window, compare actuals to last week's forecast, and report the misses -- forecast accuracy is a metric. ## Quick Commands - "Forecast from [files]" -- full workflow - "When's my next crunch?" -- the headline week and its gap - "What if [customer] pays late?" -- single-scenario rerun - "Roll the forecast" -- weekly update against actuals
© OneWave-AI · MIT · OneWave-AI/claude-skills
Similar skills
All skills for Finance and business →cash-flow-forecaster by other authors comes first.