Localized reading guide
cash-flow-snapshotPurpose, usage and source
Reads AR/AP, historical cash timing, and known fixed costs from the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) or from PayPal, Square, or Stripe — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/cash-flow-snapshot/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Reads AR/AP, historical cash timing, and known fixed costs from the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) or from PayPal, Square, or Stripe — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.
How the upstream workflow works
Step 1 — Identify available data sources
Check which connectors are live. Pull from every one that is, in one batch: The ledger — MYOB, NetSuite, QuickBooks, Xero, or Zoho Books, whichever is connected — for AR aging, AP, fixed costs, and the cash balance. Ledgers are peers (../../shared/connector-neutrality.md); if two are connected, ask which is the source of record and take totals from that one only PayPal — transaction history and settlement timing Square — sales and payout history
Step 2 — Pull the data
From the ledger: Balance sheet: bank and cash balances with the as-of date — the opening balance (MYOB holds none; see reference/v2_sources.md) AR aging report: customer name, invoice amount, invoice date, due date, days outstanding AP: vendor name, amount due, due date
Step 3 — Compute historical payment timing
For each AR customer (or income source from CSV), calculate: Mean payment lag — average days from invoice/transaction date to receipt Payment variance — standard deviation of payment lag across last 6–12 payments Use variance to set confidence band width (see Step 4)
Upstream passage · L80 ↗band_pct = weighted_avg_stddev_days / avg_payment_lag_days
low = net_cash × (1 − band_pct)
high = net_cash × (1 + band_pct)Requirements and setup
compatibility
Requires one or more of: a ledger MCP (MYOB, NetSuite, QuickBooks, Xero, Zoho Books), PayPal MCP, Shopify MCP, Square MCP, Stripe MCP, file upload (CSV fallback). Output uses xlsx skill.
Upstream passage · L1 ↗Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Cash Flow Snapshot
- Step 1 — Identify available data sources
- Step 2 — Pull the data
- Step 3 — Compute historical payment timing
- Step 4 — Build the 30/60/90-day forecast
- Step 5 — Flag named risks
- Step 6 — Deliver outputs
- After the run
- Approval gates
- More sources, and a schedule
- Running on a schedule
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
1e5584378c5817981899bfa81296d8a9c2a7e4381a2f1deed616194e51944fff