Skip to content
cccskills
FreePublished on GitHub

mint-recon

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".

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76 stars(GitHub 76 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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:

# 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:

SignalStage 1 ($0-$1M)Stage 2 ($1M-$10M)Stage 3 ($10M-$100M)
ARR<$1M$1M-$10M$10M-$100M
Finance functionFounder trackingMonthly closeFull FP&A
Board reportingInformal/noneMonthly packageFormal deck
Budget processNone/informalAnnual budgetDepartmental + 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:

MetricCurrentBenchmarkStatus
LTV:CAC ratioTarget: >3x
Payback periodTarget: <18 months
Gross marginTarget: >70% SaaS
NRRTarget: >100%
Logo churnTarget: <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

AssetExists?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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

apex

Free

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

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".

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

tonone-ai/tonone76Updated Oct 15, 2026

See all skills by tonone-ai

Report a problem with this skill