customer-panel-of-experts — Claude Code skill: what it does
customer-panel-of-experts assembles a panel of buyer personas to debate product changes, price hikes, or launches before committing resources.
MIT 162 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a claude-codeWhat customer-panel-of-experts does
The skill convenes 3 to 6 buyer personas to evaluate critical business moves. It loads structured customer data from personas/ and icp-profile.md generated by icp-deep-scanner. If source profiles are missing, it flags the entire session as provisional so synthetic opinions never masquerade as grounded facts.
During the debate, each archetype reacts in character, challenges other personas, and surfaces dealbreakers. You receive an explicit verdict (such as GO, NO, or TEST FIRST), a vote table, ranked objections with blast radii, and the least expensive test to de-risk assumptions.
Data connections remain strictly read-only, and customer identity details are scrubbed from the output. For large panels, the skill can orchestrate parallel sub-agents using /agent-army.
What it helps with
- evaluate customer backlash before rolling out price increases
- test product launch messaging against realistic buyer objections
- choose between competing positioning strategies with buyer feedback
- identify churn risks when deprecating an existing feature
Example prompts for the agent
- Run a debate on raising our subscription prices by 20%
- Put together a customer panel to review our upcoming launch campaign
- Check how core personas react to removing this integration
How to install customer-panel-of-experts
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a claude-code2Manually: put the files in place
~/.claude/skills/customer-panel-of-experts/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/customer-panel-of-experts/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a codex2Manually: put the files in place
.agents/skills/customer-panel-of-experts/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a cursor2Manually: put the files in place
.cursor/skills/customer-panel-of-experts/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills customer-panel-of-experts2Manually: put the files in place
.github/skills/customer-panel-of-experts/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path customer-panel-of-expertsManually: put the files in place
.devin/skills/customer-panel-of-experts/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about customer-panel-of-experts
How to install customer-panel-of-experts in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill customer-panel-of-experts -a claude-code.
What does customer-panel-of-experts do?
It seats a virtual panel of customer archetypes to debate major decisions, providing a recommendation, ranked objections, and immediate testing ideas.
How does the panel obtain buyer personas?
It reads profiles from personas/ and icp-profile.md. If no library exists, it runs icp-deep-scanner or constructs temporary personas clearly tagged as provisional.
Source text
SKILL.md · MIT
---
name: customer-panel-of-experts
description: Build a panel of your real buyer personas (from a deep scan of any tools you allow it to connect to) and have them debate any decision you bring — a marketing launch, a price increase, a new product, a positioning change, a feature cut. Returns a structured debate, the strongest objections, and a clear recommendation. Use when you want your actual customers in the room before you commit.
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, Agent
model: inherit
---
# Customer Panel of Experts
Put your customers in the room before you spend money or burn trust. This skill assembles a panel of data-grounded buyer personas and runs a real debate on whatever you're deciding — then hands you the decision, the dissent, and what to test next.
It is the flagship of the panel family. It reads the persona library produced by `icp-deep-scanner` and turns it into a living, arguing room.
## When to use it
- "Should we raise prices 20%?" — and what each segment will actually do.
- "Here's the launch campaign for {product}. Will it land?"
- "We're killing {feature} and adding {feature}. Who revolts?"
- "Pick between positioning A and positioning B."
- Any high-stakes call where you'd normally guess what customers think.
## Step 0 — Get the personas
The panel is only as good as its members. In order of preference:
1. **Use an existing persona library.** Look for `personas/` and `icp-profile.md` (output of `icp-deep-scanner`). Load every persona file and `personas/index.md`.
2. **Generate one now.** If none exists and the user has connected tools, run `icp-deep-scanner` first (read-only) to build it from real data.
3. **Bootstrap from input.** If there's no data and no time, build 3–5 provisional personas from what the user tells you — and label the entire session **"PROVISIONAL — not grounded in customer data"** at the top and bottom. Never let a guessed panel masquerade as a researched one.
### Data & security rules
- Connecting tools is **read-only**. Never write to, send from, or modify a connected source. Confirm before any exception.
- Personas are archetypes. Do not surface real customer names/emails/account IDs in the debate. Quotes must be scrubbed.
- Secrets stay in env vars / the MCP connection — never printed or stored in output.
## Step 1 — Frame the decision
Restate the decision crisply and lock the variables before debating:
- **The decision:** one sentence, with the specific option(s) on the table.
- **What changes for the customer:** price, workflow, access, expectation.
- **Success metric:** what "this went well" means in numbers.
- **Reversibility:** can we walk it back, and at what cost?
If the user's ask is vague ("is this a good idea?"), tighten it into a decision with options before proceeding.
## Step 2 — Seat the panel
Select 3–6 personas relevant to THIS decision (a pricing decision needs the economic buyer and a price-sensitive segment; a feature cut needs the power users who rely on it). For each seated persona, state in one line who they are and why they're in the room. If a critical viewpoint is missing from the library, say so — don't invent a flattering one.
For a deep, parallel debate (many personas × many angles), dispatch one sub-agent per persona via `/agent-army`, then synthesize. Otherwise run it inline.
## Step 3 — Run the debate
Each persona argues **in character, from their real goals, pains, and language** — not as a generic critic. Structure:
1. **Gut reaction** — each persona's first, honest read of the decision (one paragraph, in their voice).
2. **Cross-examination** — personas challenge each other. The economic buyer and the end user often want opposite things; let that tension play out. Surface where one persona's win is another's loss.
3. **The strongest objection** — the single most dangerous reaction, stated as that customer would actually say it (and would actually act on — churn, downgrade, public complaint, silence).
4. **What would change their mind** — the concession, proof, or framing that flips a NO to a YES.
Keep personas honest: include the ones who will hate it. A panel that all agrees is a panel you rigged.
## Step 4 — Synthesize the decision
```markdown
# Customer Panel — {Decision}
Generated: {timestamp} · Panel: {persona list} · Grounding: {data-backed / PROVISIONAL}
## Recommendation: {GO / GO WITH CHANGES / NO / TEST FIRST}
One paragraph: what to do and why, in plain language.
## Vote by persona
| Persona | Verdict | Why | If it ships anyway, they will… |
## The objections that matter (ranked)
1. {Objection} — who raises it, how likely to act, blast radius, mitigation.
## What this changes about the plan
- Concrete edits to the launch / price / product before you commit.
## What to test before betting the company
- The cheapest experiment that would de-risk the biggest unknown.
## Confidence & blind spots
- Grounding strength, which personas are thin, which viewpoint is missing.
```
## Step 5 — Offer the next move
Offer to: rerun the panel against a revised plan, hand the strongest objection to `prospect-panel-simulator` to test live messaging, route a pricing decision to `pricing-change-strategist`, or escalate a full launch to `product-launch-war-room`.
## Guardrails recap
Grounded personas beat invented ones — and provisional panels say so loudly · read-only connections · no real PII in output · include the customers who'll hate it · every verdict ties to a persona's real motivation.
© OneWave-AI · MIT · OneWave-AI/claude-skills