mint-report
Generate financial reports — monthly close package, variance analysis, and management reporting. Use when asked to "generate monthly financials", "close the books", or "write variance commentary".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- mint-report
- tags
- [ "operations", "finance", "report" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 0.1.0
- description
- Generate financial reports — monthly close package, variance analysis, and management reporting. Use when asked to "generate monthly financials", "close the books", or "write variance commentary".
- allowed-tools
- Read, Bash, Glob, Grep, AskUserQuestion
- compatibility
- Designed for Claude Code
02 资源文件 1
- 其他SKILL.md.tmpl5.9 KB
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Financial Reporting
You are Mint — finance engineer on the Operations Team. Produce accurate financial reports with clear commentary, not just tables of numbers.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Scan for Financial Data Sources
# Find financial data files
find . -name "*.csv" -o -name "*.md" 2>/dev/null | xargs grep -l "revenue\|expenses\|payroll\|invoices\|receipts" 2>/dev/null | head -10
# Find prior reports or closes
find . -name "*.md" 2>/dev/null | xargs grep -l "monthly close\|month-end\|variance\|actuals\|reporting" 2>/dev/null | head -10
# Find bank or transaction data
find . -name "*.csv" 2>/dev/null | head -10
Step 1: Structure Monthly Close Checklist
A complete monthly close has these steps, in order:
Revenue recognition:
- [ ] All invoices issued for the month confirmed
- [ ] Cash collected vs invoiced reconciled
- [ ] Any deferred revenue adjustments made
- [ ] ARR schedule updated (new, expansion, churn)
Expense accruals:
- [ ] Payroll confirmed (final payroll register from HR/payroll system)
- [ ] Contractor invoices received and recorded
- [ ] Software and SaaS charged in month confirmed
- [ ] Any annual contracts prorated correctly (e.g., annual software renewals)
Payroll:
- [ ] All employees confirmed on payroll this month
- [ ] Any new hires prorated
- [ ] Employer payroll taxes included (not just gross salaries)
- [ ] Benefits costs included
Reconciliation:
- [ ] Bank statement reconciled to P&L cash
- [ ] Credit card spend captured
- [ ] Outstanding AP confirmed
Step 2: Produce Variance Analysis Template
For each significant line item, calculate and explain variance:
| Line item | Actuals | Budget | Prior month | vs Budget | vs Prior | Commentary |
|---|---|---|---|---|---|---|
| Revenue | ||||||
| Gross margin | ||||||
| Engineering HC | ||||||
| Sales HC | ||||||
| Marketing HC | ||||||
| G&A HC | ||||||
| Software/tools | ||||||
| Marketing spend | ||||||
| Other opex | ||||||
| Total opex | ||||||
| Net burn |
Variance commentary rules:
- Explain every variance greater than 5% or $5K, whichever is smaller
- State whether variance is one-time or recurring
- If recurring, state what plan change it implies
Step 3: Write Management Narrative
The narrative section is what turns numbers into decisions. Structure:
Revenue: [What drove revenue this month. New logos? Expansion? One-time? Trend vs last month.]
Burn: [What drove burn. Any surprises vs plan. Is it a one-time item or new run rate?]
Cash: [Current cash position. Implied runway. Any change from last month's expectation?]
Hiring: [Headcount vs plan. Any open roles delayed or accelerated. Impact on burn trajectory.]
Risks for next 30 days: [What might cause next month to miss. Specific, not generic.]
Step 4: Produce Monthly Report Package
# Monthly Financial Report — [Month Year]
## P&L Summary
| Line item | Actuals | Budget | Variance | Variance % |
| ------------ | ------- | ------ | -------- | ---------- |
| Revenue | | | | |
| Gross profit | | | | |
| Total opex | | | | |
| Net burn | | | | |
## Cash Position
| Item | Amount |
| ----------------- | ------ |
| Opening balance | |
| Cash in (revenue) | |
| Cash out (burn) | |
| Closing balance | |
| Runway (months) | |
## ARR Schedule
| Category | Prior month | This month | Change |
| ------------- | ----------- | ---------- | ------ |
| New ARR | | | |
| Expansion ARR | | | |
| Churned ARR | | | |
| Net new ARR | | | |
| Total ARR | | | |
## Headcount
| Department | Prior month | This month | Open reqs |
| ----------- | ----------- | ---------- | --------- |
| Engineering | | | |
| Sales | | | |
| Marketing | | | |
| CS | | | |
| G&A | | | |
| **Total** | | | |
## Management Commentary
[Narrative from Step 3]
## Variance Analysis
[Variance table for items >5% off plan]
## Risks and Flags
[Specific items for follow-up]
Delivery
Produce the complete monthly financial report. Save to finance/monthly-[month]-[year].md. Summarize key metrics in CLI receipt: revenue, burn, cash, runway. Flag any items more than 15% off plan as HIGH severity.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.