Finance Skills is an open-source skill library for AI agents that work with finance operators, accountants, revenue teams, and founders. It gives agents specific operating procedures for recurring finance workflows: AR follow-up, dunning emails, contract-to-invoice checks, usage billing review, revenue recognition QA, payment reconciliation, close checklists, and CFO briefings.
The project is inspired by the structure of Garry Tan's gstack: small, opinionated skills that turn a general coding or research agent into a specialist for a specific job. The content here is original and focused on finance operations rather than software delivery.
- A set of
SKILL.mdfolders that can be copied into an agent skill system. - A practical starting point for finance workflows that need judgment, traceability, and human review.
- A public artifact finance teams can fork, adapt, and make more specific to their billing stack, accounting policy, and close process.
- It is not accounting, tax, legal, or audit advice.
- It is not a replacement for controller, CFO, auditor, or counsel review.
- It does not send customer communications, post journal entries, or change source systems without explicit human approval.
| Skill | Use it when |
|---|---|
ar-collections |
Reviewing AR aging, prioritizing overdue accounts, and drafting collector worklists. |
dunning-emails |
Drafting customer-safe payment reminder sequences from invoice and account context. |
contract-to-invoice |
Extracting billing obligations from contracts and comparing them with draft invoices. |
usage-billing-review |
Checking metered usage invoices against usage exports, pricing terms, and exception rules. |
revenue-recognition-qa |
Reviewing revenue schedules, deferrals, SSP assumptions, and support for unusual deals. |
payment-reconciliation |
Matching payments, deposits, remittances, invoices, and bank activity. |
finance-close-checklist |
Running a month-end close checklist and surfacing blockers by owner and due date. |
cfo-briefing |
Turning finance inputs into a concise CFO-ready operating brief. |
invoice-health-check |
Scoring invoice completeness and collection risk before sending or sharing. |
Copy the folders you want into your agent's skills directory. For Codex-style skills:
mkdir -p ~/.codex/skills/finance
cp -R skills/* ~/.codex/skills/finance/For Claude-style local skills:
mkdir -p ~/.claude/skills/finance
cp -R skills/* ~/.claude/skills/finance/Then ask your agent to use the relevant skill by name, for example:
Use the usage-billing-review skill to check this May usage invoice against the CSV export and pricing schedule.
- Source-backed outputs: Every finding should point to the source document, row, customer, invoice, or system export that supports it.
- No silent posting: Drafts and recommendations are fine. Sending email, posting journal entries, writing off balances, or changing customer records requires explicit approval.
- Materiality matters: Call out what is financially material, operationally urgent, and merely tidy-up work.
- Protect customer trust: Customer-facing language should be accurate, calm, and free of internal blame.
- Keep an audit trail: List assumptions, missing data, and unresolved exceptions.
The skills work best with concrete files or excerpts:
- AR aging reports
- Invoice PDFs or exports
- Contract excerpts, order forms, and pricing tables
- Usage logs or billing meter exports
- Payment processor payouts and remittance files
- Bank activity exports
- Revenue schedules and close calendars
- Board, investor, or operating KPI decks
Contributions are welcome. Add a new skill when a workflow is common, repeatable, and benefits from a clear review checklist. Keep each SKILL.md short enough to load quickly, with detailed examples moved into a references/ folder only when necessary.
Good contributions include:
- New finance workflow skills.
- Better output templates.
- More precise controls for auditability, approvals, and customer-safe language.
- Stack-specific references for tools like Stripe, QuickBooks, NetSuite, Salesforce, Chargebee, Maxio, Paddle, or spreadsheets.
MIT.
