apex
無料Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
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".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
# 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
A complete monthly close has these steps, in order:
Revenue recognition:
Expense accruals:
Payroll:
Reconciliation:
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:
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.]
# 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]
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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
日本語の概要は準備中です。原文の説明を表示しています。
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
日本語の概要は準備中です。原文の説明を表示しています。
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
日本語の概要は準備中です。原文の説明を表示しています。