C✳CODEZ.WIN
🌐 English

Localized reading guide

plan-payrollPurpose, usage and source

Runs the payroll-confidence chain end to end — forecasts cash across the payroll window with cash-flow-snapshot, ranks and drafts overdue-invoice reminders with invoice-chase to close any gap, then assembles timesheets, flags every anomaly, and stages the run with payroll-prep. On Gusto the run is staged for the owner to submit; on QuickBooks Payroll, or with no payroll system, the last step is a validated run sheet the owner keys in. This chain never presses the payroll button. Builds on the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books), with Gmail or M365, PayPal, Square, Stripe, and either Gusto or QuickBooks Payroll adding detail, and falls back to CSV and timesheet uploads. Use it whenever payroll is the worry, including "can I make payroll," "payroll is due Friday," "plan payroll," "will I have enough to pay the crew," or "I need to run payroll but money is tight." Accepts optional horizon and payroll-date arguments.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
small-business/skills/plan-payroll/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Agent workflows
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

Runs the payroll-confidence chain end to end — forecasts cash across the payroll window with cash-flow-snapshot, ranks and drafts overdue-invoice reminders with invoice-chase to close any gap, then assembles timesheets, flags every anomaly, and stages the run with payroll-prep. On Gusto the run is staged for the owner to submit; on QuickBooks Payroll, or with no payroll system, the last step is a validated run sheet the owner keys in. This chain never presses the payroll button. Builds on the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books), with Gmail or M365, PayPal, Square, Stripe, and either Gusto or QuickBooks Payroll adding detail, and falls back to CSV and timesheet uploads. Use it whenever payroll is the worry, including "can I make payroll," "payroll is due Friday," "plan payroll," "will I have enough to pay the crew," or "I need to run payroll but money is tight." Accepts optional horizon and payroll-date arguments.

How the upstream workflow works

Step 1 — Is payroll covered? (cash-flow-snapshot)

Invoke cash-flow-snapshot. It owns the forecast math, the confidence bands, and the CSV fallback — do not rebuild any of it here. Goes in: the horizon and the payroll date. Comes out: a 30/60/90-day forecast, named risk flags, a chat summary, and an XLSX. Say the verdict in one line before anything else: covered, tight, or short by a named dollar amount on a named date.

Upstream passage · L18 ↗

Step 2 — Close the gap (invoice-chase)

Invoke invoice-chase. It owns the ranking, the tone matching, and the send path per invoice type. Goes in: the gap amount and the date it lands, from Step 1. Comes out: ranked overdue invoices with a drafted reminder each, PayPal-issued invoices queued as PayPal sends and the rest as mail drafts. Tie the ranking back to Step 1: show what gets collected inside the horizon and whether that actually closes the payroll gap. A reminder that pays in 45 days does nothing for a Friday run — say so.

Upstream passage · L29 ↗

Step 3 — Stage the run (payroll-prep)

Invoke payroll-prep. It owns the period setup, the hour totals, the anomaly checks, and the books sync. Goes in: the pay period, the roster, and the cash verdict from Step 1. Comes out: a run sheet person by person, every anomaly flagged against the person it belongs to, totals, and the cash needed on the pay date. Carry Step 1 forward instead of recomputing it. When payroll-prep reports whether the run clears, it uses the forecast this chain already produced, plus anything Step 2 is expected to collect.

Upstream passage · L40 ↗

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Skill format and directory specification ↗

Read further in the source

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.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
42ac5999ae910b49d103961d5792d24a596e02ed2cadf86799c199939d53f251
Back to the full Skill catalog