Skip to main content
skill CX Codex

prospect-panel-simulator — Claude Code skill: sales review and install

prospect-panel-simulator is a skill that simulates buyer reactions to sales and marketing materials before they go live, surfacing objections and likely next actions.

MIT 164 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill prospect-panel-simulator -a claude-code
Open on GitHub

What prospect-panel-simulator does

Use the skill to test a specific artifact: a cold email, pitch deck, pricing page, demo script, or proposal. It models how a busy prospect reads, where they lose interest, what makes them hesitate, and what they do next. The panel can include an economic buyer, champion, blocker, and end user, whose reactions may differ.

The skill prefers personas from icp-deep-scanner results and can run that scanner in read-only mode when tools are connected. If the user’s description is the only basis for a panel, the result is marked PROVISIONAL. Its report groups reactions by persona and flags weak lines, trust concerns, and possible rewrites. Connections are read-only, so the skill does not send materials; real prospect names and email addresses are excluded from its output.

What it helps with

  • Check whether a cold email earns a reply or gets ignored
  • Spot price objections on a landing page
  • Find where a prospect stops following a pitch deck
  • Flag wording that weakens trust in a proposal
  • Compare how buyer-committee roles react to one message

Example prompts for the agent

  • Review outreach.md as a cold email and predict how an economic buyer and end user would react.
  • Run a prospect panel on this pricing page and list the strongest objections.
  • Assess this deck before I send it; show where each buyer persona loses interest.

How to install prospect-panel-simulator

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill prospect-panel-simulator -a claude-code

2Manually: put the files in place

~/.claude/skills/prospect-panel-simulator/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/prospect-panel-simulator/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about prospect-panel-simulator

How do I install prospect-panel-simulator in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill prospect-panel-simulator -a claude-code. The skill file is at ~/.claude/skills/prospect-panel-simulator/SKILL.md.

What does prospect-panel-simulator do?

It simulates potential buyers’ reactions to sales and marketing materials, identifies objections, and suggests rewrites for weak lines. The report also predicts each persona’s next action.

What data does the prospect panel use?

It prefers personas from icp-deep-scanner and can run that tool in read-only mode when connected. A panel based only on the user’s description is labeled PROVISIONAL.

Source text

SKILL.md · MIT
---
name: prospect-panel-simulator
description: Simulate a panel of your real prospects and buyers to pressure-test sales and marketing before it goes out — cold emails, pitch decks, landing pages, pricing pages, demo scripts, proposals. Each simulated prospect reacts in character, raises the objection they'd actually raise, and tells you whether they'd reply, book, or ghost. Use to de-risk outbound and messaging without burning real leads.
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, Agent
model: inherit
---

# Prospect Panel Simulator

Before you send the email, run the deck, or publish the pricing page — run it past the people who'd receive it. This skill simulates a panel of your actual prospects and reacts the way the market will: skeptical, busy, half-reading, comparing you to three other options.

Where `customer-panel-of-experts` debates a business *decision* with existing customers, this skill stress-tests a *sales or marketing artifact* against people who don't know you yet and don't owe you a reply.

## What it pressure-tests
- Cold emails and full sequences (does it get a reply, or a delete?)
- Pitch decks and one-pagers (where do they check out?)
- Landing pages and pricing pages (what makes them bounce?)
- Demo scripts and discovery-call openers
- Proposals and SOWs (what gets pushed back on?)

## Step 0 — Assemble the prospect panel

1. **Preferred:** load personas from `icp-deep-scanner` output (`personas/`, `icp-profile.md`) and seat the **buying committee** — economic buyer, champion, blocker, and end user — since a cold artifact hits all of them differently.
2. **If no library exists** and tools are connected, run `icp-deep-scanner` (read-only) to ground the panel in real won/lost-deal data and real objection language.
3. **Bootstrap** from the user's description only as a last resort, labeled **PROVISIONAL**.

Critically, model **cold-state** prospects: they have low context, low trust, and an alternative they already use. A simulated prospect who reads charitably is useless.

### Security
Read-only connections. No sending, no writing to any tool. No real prospect names/emails in output — these are archetypes. Secrets stay in env vars.

## Step 1 — Take in the artifact

Read exactly what will go out (paste, file, or URL via WebFetch). Note the channel and the moment: a cold email at 7am from an unknown sender is judged differently than a pricing page reached after a demo. Confirm: who is this for, what's the one action it's asking for, and what does the prospect see *right before* this?

## Step 2 — Simulate reactions

Each panel member reacts in character through the real sequence of a busy buyer:

1. **First 3 seconds** — subject line / headline / first slide only. Open or delete? Keep scrolling or bounce? Be brutal; most things die here.
2. **Skim** — what they actually absorb on a fast read, what they skip, where the eye snags.
3. **Objection** — the specific reason this particular persona hesitates, stated in their words ("we already use X", "no budget this quarter", "who are these guys", "feels generic").
4. **Trust check** — does anything read as spam, AI-generated, over-promised, or off (the champion and the economic buyer flag different things).
5. **Verdict + next action** — reply / book / forward to {persona} / ignore / unsubscribe — and the honest probability.

Let personas disagree: a value prop that excites the end user can spook the economic buyer on price.

## Step 3 — Report

```markdown
# Prospect Panel — {Artifact}
Generated: {timestamp} · Panel: {personas} · Channel: {cold email / LP / deck} · Grounding: {data / PROVISIONAL}

## Predicted outcome: {STRONG / MIXED / WEAK} — est. reply/convert signal
One-line read on whether to send as-is.

## Reaction by persona
| Persona | Opens? | Gets it? | Top objection | Action |

## Where it loses people (ranked, with the exact line)
1. "{quoted line}" — {persona} → {reaction} → {fix}

## AI-tell / trust flags
- Phrases or patterns that read as generic, automated, or over-promised.

## Rewrite the weak points
- Before → After on the 2–3 highest-leverage lines.

## A/B worth running
- The one variable most worth testing live.
```

## Step 4 — Iterate
Offer to apply the rewrites and re-run the panel on v2, or hand the winning angle to `cold-email-sequence-generator` / `landing-page-copywriter` to scale it.

## Guardrails recap
Model cold, skeptical, time-poor prospects — not friendly readers · ground in real won/lost data when available, flag PROVISIONAL otherwise · read-only, no sending · quote the exact lines that fail · no real prospect PII.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Marketing and content →

From the same set185

The whole set →
hyperframes-ad-director hyperframes-ad-director turns a marketing brief into a finished short-form video ad built in HyperFrames: hook, script, storyboard, HTML composition, captions, and voiceover. CX Codex +1 185installs claude-design-critic The claude-design-critic skill reviews a website or UI for generic design and copy, then ranks concrete fixes. Use it after generating a frontend or when a page feels bland. CX Codex +1 184installs claude-landing-composer claude-landing-composer builds custom Next.js landing pages with Tailwind v4 and Motion animations. Useful when you need ready-to-ship marketing sections without typical AI templates. CX Codex +1 178installs claude-design-system-architect claude-design-system-architect is a Claude Code skill that turns a brand brief or existing site into reusable design tokens, component specs, and project files. It defines shared rules for a new product or inconsistent UI. CX Codex +1 172installs customer-panel-of-experts customer-panel-of-experts assembles a panel of buyer personas to debate product changes, price hikes, or launches before committing resources. CX Codex +1 162installs icp-deep-scanner The icp-deep-scanner skill turns data from connected tools into an Ideal Customer Profile and a persona library. Use it when you need to refresh your ICP or build buyer personas from actual data, not guesses. CX Codex +1 161installs product-launch-war-room product-launch-war-room is a Claude Code skill that tests a launch plan against expert and customer viewpoints, then returns a decision and rollout steps. Run it for a product launch, repricing, or repositioning. CX Codex +1 159installs pricing-change-strategist pricing-change-strategist plans a price increase or tier restructure with churn modeling. CX Codex +1 158installs

Project sponsors

Companies that keep this analytics open