본문으로 건너뛰기
cccskills
무료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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

apex

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-gate

무료

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

apex-plan

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tonone-ai/tonone762026년 10월 15일 업데이트

tonone-ai의 스킬 모두 보기

이 스킬의 문제 신고