plan-payroll

bởi anthropic

Dự báo tiền mặt, xếp hạng hóa đơn quá hạn và sắp xếp nhắc nhở PayPal để chủ doanh nghiệp tự tin chạy bảng lương. Chấp nhận tùy chọn khoảng thời gian và ngày trả lương…

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill plan-payroll

Tải ZIP GitHub

23.3k

Run the payroll-confidence pipeline by chaining two skills. The owner approves at each handoff — never send a reminder or commit a forecast without explicit confirmation.

Parse arguments:

--horizon (default 30) — forecast window in days (30, 60, or 90)
--payroll-date (optional) — the date payroll runs; defaults to next Friday

Step 1 — Cash forecast (cash-flow-snapshot)

Trigger the cash-flow-snapshot skill workflow:

Pull AR, AP, and historical cash timing from QuickBooks, PayPal, Stripe, or Square (whichever are connected). Fall back to CSV upload if no connector is live.
Layer in known fixed costs (rent, payroll, recurring vendor charges).
Produce a 30/60/90-day forecast (use the requested --horizon) with percentage-variance confidence bands.
Flag named risks — e.g., "payroll on May 15 lands $4,200 below your fixed-cost floor at the median forecast."
Deliver chat summary + downloadable XLSX.
Present to the owner. Wait for explicit "okay, see what we can collect" before Step 2.

If the forecast shows payroll is comfortably covered, ask the owner whether they still want to chase overdue invoices or stop here.

Step 2 — Overdue collection (invoice-chase)

After Step 1 approval, trigger the invoice-chase skill workflow:

Pull overdue invoices from QuickBooks and PayPal.
Rank by amount × days-late × customer payment history.
For each, draft a reminder matched to tone (gentle for good customers, firm for repeat late payers).
PayPal-issued invoices queue as PayPal-send drafts; non-PayPal invoices queue as Mail drafts.
Present the ranked list with drafted reminders. Show the projected cash impact if a top-N subset gets paid within the horizon — does that close the payroll gap from Step 1?
Wait for explicit "send these" per reminder (or batch approval) before pushing.

Approval gates (must hold)

Never send a reminder without owner approval — drafts only until "send" is given.
Never commit a forecast as authoritative without owner sign-off.
If a connector is unreachable (QuickBooks, PayPal, Mail), stop, report which connector failed, and ask whether to retry, fall back to CSV, or abort.

Output

End the run with a one-paragraph recap: forecast verdict (covered / gap / risk), reminders sent and to whom, projected new cash position if reminders convert.