Skip to content
Back to skills

Mint Recon

ASecurity

Financial reconnaissance — audit current P&L, burn rate, runway, unit economics, and financial health to understand where the constraint is. Use when asked to "audit our finances", "what is our runway", "are our unit economics healthy", or "before building a financial model".

  • 71 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 27, 2026
businessgobashapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add tonone-ai/tonone --skill mint-recon --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mint Recon?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mint Recon
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tonone-ai-mint-recon/badge)](https://www.skillsdirectory.com/skills/tonone-ai-mint-recon)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mint-recon
description: Financial reconnaissance — audit current P&L, burn rate, runway, unit economics, and financial health to understand where the constraint is. Use when asked to "audit our finances", "what is our runway", "are our unit economics healthy", or "before building a financial model".
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version: 0.1.0
author: tonone-ai <hello@tonone.ai>
license: MIT
---

# Financial Reconnaissance

You are Mint — finance engineer on the Operations Team. Map the current financial state before building any model, budget, or board package.

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: Detect Financial Artifacts

Scan for financial and accounting artifacts:

```bash
# P&L or income statement docs
find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "p&l\|income statement\|profit and loss\|revenue\|expenses\|ebitda\|gross margin" 2>/dev/null | head -15

# Budget or headcount plan docs
find . -name "*.md" -o -name "*.csv" 2>/dev/null | xargs grep -l "budget\|headcount plan\|spending plan\|annual plan\|financial plan" 2>/dev/null | head -10

# Burn rate and runway docs
find . -name "*.md" 2>/dev/null | xargs grep -l "burn rate\|burn\|runway\|cash position\|cash flow\|working capital" 2>/dev/null | head -10

# Unit economics docs
find . -name "*.md" 2>/dev/null | xargs grep -l "ltv\|cac\|customer acquisition cost\|lifetime value\|payback\|gross margin\|churn\|nrr" 2>/dev/null | head -10
```

### Step 1: Diagnose Financial Stage

Determine which stage the company is at based on available signals:

| Signal           | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) |
| ---------------- | ---------------- | ------------------ | -------------------- |
| ARR              | <$1M             | $1M-$10M           | $10M-$100M           |
| Finance function | Founder tracking | Monthly close      | Full FP&A            |
| Board reporting  | Informal/none    | Monthly package    | Formal deck          |
| Budget process   | None/informal    | Annual budget      | Departmental + FP&A  |

### Step 2: Map Cash Position

Identify current state of:

- **Cash balance** — How much cash is in the bank right now?
- **Monthly burn** — What does the company spend per month, gross and net?
- **Runway** — At current burn, how many months until cash hits zero?
- **Revenue** — ARR, MRR, and trend (growing, flat, declining)?
- **Gross margin** — What percentage of revenue flows through after COGS?

### Step 3: Assess Unit Economics

Check health of core metrics:

| Metric         | Current | Benchmark          | Status |
| -------------- | ------- | ------------------ | ------ |
| LTV:CAC ratio  |         | Target: >3x        |        |
| Payback period |         | Target: <18 months |        |
| Gross margin   |         | Target: >70% SaaS  |        |
| NRR            |         | Target: >100%      |        |
| Logo churn     |         | Target: <2%/month  |        |

### Step 4: Identify the Constraint

Map the primary financial constraint:

- **Runway too short** — Less than 12 months: raise or cut immediately
- **Unit economics broken** — LTV:CAC below 1.5x: stop growth spend, fix the model
- **Burn too high** — Burn growing faster than revenue: identify top 3 burn drivers
- **Gross margin too low** — Below 60%: pricing or COGS problem before scaling
- **Churn killing LTV** — Monthly logo churn above 3%: CS and product problem first

### Step 5: Inventory Financial Assets

| Asset                    | Exists?  | Quality |
| ------------------------ | -------- | ------- |
| P&L / income statement   | [yes/no] |         |
| Cash flow / runway model | [yes/no] |         |
| Budget vs actuals        | [yes/no] |         |
| Unit economics doc       | [yes/no] |         |
| Revenue forecast         | [yes/no] |         |
| Cap table                | [yes/no] |         |
| Board financial package  | [yes/no] |         |

### Step 6: Present Assessment

```
## Financial Reconnaissance

**Stage:** [1/2/3] — [descriptor] | **ARR:** [current or estimated]
**Cash:** [$X] | **Burn:** [$X/mo] | **Runway:** [N months]
**Primary constraint:** [the one thing limiting financial health]

### Unit Economics
| Metric       | Current | Benchmark | Status |
|--------------|---------|-----------|--------|
| LTV:CAC      |         | >3x       |        |
| Payback      |         | <18 mo    |        |
| Gross margin |         | >70%      |        |

### Financial Asset Gaps
[List the 2-3 most critical missing artifacts]

### Highest Leverage Action
[Single most important financial task this week]
```

## Delivery

If output exceeds 40-line CLI budget, invoke `/atlas-report` with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.