Terminal
Terminal/Skill
Forecasts 30, 60 and 90 day cash flow from ledger, payment or CSV data, with confidence bands, risk flags and an XLSX export.
By Anthropic
Works with
npx skills add anthropics/knowledge-work-plugins --skill cash-flow-snapshotProduces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a two-part output: a concise chat summary and a downloadable XLSX workbook.
Quick start
"Will I make payroll next month?"
Claude pulls the current bank balance, AR/AP, and fixed costs from connected sources, calculates expected inflows and outflows across 30, 60, and 90-day windows, applies confidence bands from each customer's payment variance, and flags specific risks by name.
Check which connectors are live. Pull from every one that is, in one batch:
../../shared/connector-neutrality.md); if two are connected, ask which is the source of record and take totals from that one onlylist-orders) as the inflow, plus payout timing. Shopify on its own is enough to run: for a commerce business it is often the largest inflow. The payout read may fail because the connector's scopes exclude Shopify Payments — then ask the owner for their payout schedule and model from that; never infer a lag (reference/v2_sources.md)If no connector is live and no file is attached, ask the user to either connect a source or upload a CSV (income/expense tabular data, any reasonable format). Note which sources were used in the output — this affects confidence band width.
Always establish the starting cash balance — "will I make payroll" is a question about the balance, not the net. Pull it in Step 2, or ask: "What's in the business account right now, and as of what date?" Never assume one. If nobody knows, head the output "no opening balance — net change only" and drop cash-on-hand from the risk flags.
From the ledger:
reference/v2_sources.md)From Gusto, when connected:
From PayPal / Stripe / Square:
From CSV upload:
For each AR customer (or income source from CSV), calculate:
If fewer than 3 payments exist for a customer, use the population mean as the point estimate and apply a ±30% variance band as the default. When running on CSV data with sufficient history (≥3 payments per source), compute the band from the actual payment variance — do not assume ±30%.
Produce three time windows: 0–30 days, 31–60 days, 61–90 days.
For each window, compute:
| Line | Method |
|---|---|
| Expected inflows | AR due in window, adjusted for mean payment lag |
| Expected outflows | AP due in window + fixed costs falling in window |
| Net cash position | Inflows − Outflows |
| Confidence band | ± weighted average payment variance as a % of expected inflows |
Confidence band formula:
band_pct = weighted_avg_stddev_days / avg_payment_lag_days
low = net_cash × (1 − band_pct)
high = net_cash × (1 + band_pct)
Round band_pct to one decimal place. Cap at ±50% — higher variance means the data is too thin to model; flag it instead (see Step 5).
Scan for conditions that push the low-band estimate negative or create a liquidity crunch. For each risk found, produce a one-line flag:
Limit to the top 5 risks by severity (largest dollar impact first).
Chat summary (always). Use a markdown table for the forecast, not a fenced code block — the chat surface renders markdown tables; a fenced block shows up as raw monospace text. Shape:
Then the forecast as a markdown table, amounts carrying the business's currency
code (../../shared/currency-and-locale.md), never a bare symbol:
| Window | Expected | Low | High |
|---|---|---|---|
| 30-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX |
| 60-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX |
| 90-day net | AUD X,XXX | AUD X,XXX | AUD X,XXX |
Then risks as a short bulleted list under "⚠ Risks flagged: ".
XLSX workbook (always): read xlsx/SKILL.md first, then produce three sheets:
Summary — the 30/60/90 forecast table with confidence bands. Beneath each window row, expand inline sub-rows showing the individual transactions that make up its inflows (green) and outflows (red). This makes the estimates auditable without leaving the Summary sheet.
Detail — all transactions grouped by window, sorted by date within each group. Include a running net column (cumulative inflows minus outflows within the window) and a subtotal row at the bottom of each window showing total inflows, total outflows, and net. Grey out past transactions in a separate section at the bottom for reference. Ensure all three windows have rows even if one is empty — show a "No transactions in this window" placeholder row.
Risks — the flagged risks with dollar impact and affected window.
Save as cash-flow-snapshot-[YYYY-MM-DD].xlsx.
The forecast page (always, alongside the chat summary — never instead of
it), delivered per the owner's stored output preference — never default to a
markdown file. Check the ## Business context block's Output preference
(shared style guide rule, ../../shared/artifact-style.md):
One line on what just happened: the forecast is built and the risks are named. Then offer the single most relevant next step, plus at most two others nearby:
/plan-payroll.invoice-chase to pull collections forward./close-month so next forecast runs on clean books.Max three offers, and never repeat an offer the owner declined this session.
This skill is read-only — no approval gate before generating the forecast.
Remind the user after delivery:
"This forecast is based on [sources listed]. It is not a substitute for accounting advice — verify with your bookkeeper before making financing decisions."
Read reference/v2_sources.md for the full mapping:
Nothing about the forecast logic changes. These are additional legs into the same model.
This skill is schedulable. The monthly preset is a cash heads-up before the month turns.
Offer it once, after a forecast the owner found useful:
Want this monthly, a few days before month end? That's when it's most useful,
and it's the same forecast you just got.
Scheduling is a property of this skill. There is no separate command for it.
QuickBooks summary fields lie. Read ../../shared/quickbooks-report-traps.md before quoting any total from a QuickBooks summary object: the AP aging summary nets vendor credits into its buckets and can show a negative overdue figure, and the P&L summary can report expenses as zero against real rows. Total the rows, or use the detail call.
| File | Load when |
|---|---|
reference/gotchas.md | When a connector returns unexpected data or variance is extreme |
reference/examples/worked-example.md | When modeling the output format for a new data shape |
The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer build-connector — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.