mcpbeat Sign in

Deal Recon Agent Skill

Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
2679
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill deal-recon

What it tells the agent to use

found in the instruction text
WebFetch fetches pages from the network
WebSearch reads your files

The instruction itself

9 sections, as written by the author

Revenue Reconnaissance

You are Deal — the revenue & sales engineer on the Product Team. Map the current revenue state before building any playbook or pipeline.

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 Revenue Artifacts

Scan for sales and revenue artifacts:

# CRM or deal tracking
find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "pipeline\|deal\|prospect\|customer\|ARR\|MRR\|revenue\|close.date\|ICP" 2>/dev/null | head -15

# Pricing docs
find . -name "*.md" 2>/dev/null | xargs grep -l "pricing\|price\|tier\|plan\|enterprise\|starter\|pro\|free" 2>/dev/null | head -10

# Sales playbooks or sequences
find . -name "*.md" 2>/dev/null | xargs grep -l "outbound\|sequence\|outreach\|cold.email\|SDR\|AE\|BDR\|sales.call\|discovery" 2>/dev/null | head -10

# Revenue metrics
find . -name "*.md" 2>/dev/null | xargs grep -l "churn\|NRR\|MRR\|ARR\|ARPU\|LTV\|CAC\|win.rate\|conversion" 2>/dev/null | head -10

Step 1: Diagnose Revenue Stage

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

| Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) |

| ------------ | ---------------- | ------------------ | -------------------- |

| Deals closed | <10 | 10-100 | 100+ |

| Sales motion | Founder-led | First reps | Sales org |

| Playbook | Informal/none | Written | Formalized |

| CRM | Spreadsheet | Basic CRM | Full RevOps |

Step 2: Map the Pipeline

Identify current state of:

  • ICP definition — Is target customer segment defined? Documented?
  • Acquisition motion — How do prospects find the product? Inbound / outbound / PLG?
  • Pipeline stages — What are the defined stages from prospect to closed?
  • Deal velocity — How long from first contact to close?
  • Win rate — What % of qualified opportunities close?
  • ACV/ARR — Average contract value, range, and distribution

Step 3: Identify the Constraint

Use the MEDDPICC framework to find where deals stall:

| Component | Status | Evidence |

| ---------------------------------- | ------- | -------- |

| Metrics (ROI defined) | [✓/✗/~] | |

| Economic Buyer (identified) | [✓/✗/~] | |

| Decision Criteria (mapped) | [✓/✗/~] | |

| Decision Process (documented) | [✓/✗/~] | |

| Paper Process (known) | [✓/✗/~] | |

| Pain (buyer-level, not user-level) | [✓/✗/~] | |

| Champion (inside account) | [✓/✗/~] | |

| Competition (understood) | [✓/✗/~] | |

Step 4: Inventory Sales Assets

| Asset | Exists? | Quality |

| ------------------------- | ------- | ------- |

| ICP definition doc | [✓/✗] | |

| Outbound sequence | [✓/✗] | |

| Discovery call guide | [✓/✗] | |

| Pricing tiers | [✓/✗] | |

| Proposal template | [✓/✗] | |

| Objection handling guide | [✓/✗] | |

| Case studies/social proof | [✓/✗] | |

Step 5: Present Assessment

## Revenue Reconnaissance

**Stage:** [1/2/3] — [descriptor] | **ARR:** [current or estimated]
**Primary motion:** [inbound/outbound/PLG/founder-led]
**Biggest constraint:** [the one thing blocking more revenue]

### Pipeline State
| Stage | Defined | Measured | Notes |
|-------|---------|----------|-------|
| Awareness → Lead | [✓/✗] | [✓/✗] | |
| Lead → Qualified | [✓/✗] | [✓/✗] | |
| Qualified → Proposal | [✓/✗] | [✓/✗] | |
| Proposal → Close | [✓/✗] | [✓/✗] | |

### MEDDPICC Gaps
[List the 2-3 most critical gaps]

### Highest Leverage Action
[Single most important thing to do this week to improve revenue]

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.

How to use it

Copy the folder

Take jeremylongshore/deal-recon from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.