deal-closer-playbook — Claude Code skill: what it does, how to install
deal-closer-playbook analyzes in-flight B2B deals, runs web research on target accounts, and drafts an actionable deal-playbook.md document.
MIT 256 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a claude-codeWhat deal-closer-playbook does
This skill guides the assistant through a structured deal review from discovery calls to contract signing. It operates in two sequential phases: intelligence gathering and playbook generation. First, it pulls account news, hiring shifts, and tech stack details via WebSearch, then maps the buying committee roles from champion to procurement. Any missing stakeholder is explicitly flagged as [UNKNOWN] instead of being guessed.
Next, the skill calculates MEDDIC qualification scores and velocity risks, drafts an objection response matrix, and produces counter-arguments against named competitors or the status quo. The final output is written directly to deal-playbook.md following the bundled template in references/output-template.md.
The workflow relies on tool access to Read, Write, WebSearch, and Bash. Without live web search access, the skill cannot gather recent account signals, which weakens the competitive positioning section.
What it helps with
- map buying committee roles and highlight stakeholder coverage gaps
- score deal health using MEDDIC criteria and velocity risk checks
- build response matrices for spoken and unspoken sales objections
- create mutual close plans with concrete buyer-seller deadlines
Example prompts for the agent
- Build a closing playbook for my enterprise deal with Acme Corp currently in contract review
- Analyze this discovery-stage prospect, run company research, and assess MEDDIC gaps
- Generate deal-playbook.md for a renewal where the main competitor is building an in-house tool
How to install deal-closer-playbook
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a claude-code2Manually: put the files in place
~/.claude/skills/deal-closer-playbook/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/deal-closer-playbook/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a codex2Manually: put the files in place
.agents/skills/deal-closer-playbook/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a cursor2Manually: put the files in place
.cursor/skills/deal-closer-playbook/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills deal-closer-playbook2Manually: put the files in place
.github/skills/deal-closer-playbook/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path deal-closer-playbookManually: put the files in place
.devin/skills/deal-closer-playbook/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -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 deal-closer-playbook
How to install deal-closer-playbook in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill deal-closer-playbook -a claude-code. The skill will be placed at ~/.claude/skills/deal-closer-playbook/SKILL.md.
What does deal-closer-playbook do?
It researches target accounts with web search, identifies missing decision-makers, evaluates pipeline risks, and writes a tactical deal-playbook.md file for sales reps.
How does the skill handle stalled deals?
It evaluates why momentum stopped, whether due to budget or lost champions, and sets up a re-engagement plan around a fresh compelling event.
Source text
SKILL.md · MIT
--- name: deal-closer-playbook description: Analyzes a deal in progress and generates a comprehensive closing strategy. Researches the target company, maps the buying committee, builds objection responses, creates competitive positioning, and outputs a tactical deal-playbook.md with next-best-actions and a mutual close plan. tools: Read, Write, WebSearch, Bash model: inherit --- # Deal Closer Playbook Take a deal in progress -- at any stage from discovery to negotiation -- and produce a tactical closing playbook combining company research, stakeholder mapping, competitive intelligence, and deal mechanics into a single actionable document. ## Contents - `references/intelligence-gathering.md` -- context intake, company research, buying-committee map, MEDDIC and velocity risk scoring - `references/playbook-strategy.md` -- objection matrix, competitive positioning, stage-specific closing strategy, mutual close plan, proposal talking points - `references/output-template.md` -- full `deal-playbook.md` structure to write ## Workflow Operate in two phases: gather intelligence, then generate the playbook. Be thorough but fast. Tie every section to a specific action. 1. **Collect deal context.** Gather the required, valuable, and nice-to-have inputs. Ask for anything missing; mark unavailable items `[UNKNOWN]` and work around them. See `references/intelligence-gathering.md`. 2. **Research the company.** Use WebSearch for current intelligence: overview, last-90-days news, financial signals, leadership/hiring, tech-stack signals, industry context. See `references/intelligence-gathering.md`. 3. **Map the buying committee.** Identify and profile each role (champion, economic buyer, technical evaluator, user buyer, coach, blocker, procurement/legal, executive sponsor). Flag unknown stakeholders as discovery gaps. See `references/intelligence-gathering.md`. 4. **Assess deal risk.** Score MEDDIC qualification and the velocity risk checklist. See `references/intelligence-gathering.md`. 5. **Build the objection response matrix.** Address every raised objection plus likely unraised ones for the stage and context. See `references/playbook-strategy.md`. 6. **Build competitive positioning.** For each competitor (or the status quo), document their pitch, where they win, where you win, landmine questions, and traps to avoid. See `references/playbook-strategy.md`. 7. **Design the stage-appropriate closing strategy.** Match tactics to discovery/demo, evaluation/proposal, or negotiation/close. See `references/playbook-strategy.md`. 8. **Build the mutual close plan.** Create the shared buyer-seller timeline to signed contract. See `references/playbook-strategy.md`. 9. **Generate proposal talking points.** Draft the opening, value prop, proof, differentiation, and the ask. See `references/playbook-strategy.md`. 10. **Write the deal playbook.** Output the complete document to `deal-playbook.md` using `references/output-template.md`. ## Behavioral Rules 1. Be honest about deal risk. If the deal is poorly qualified, say so -- false confidence is worse than a clear-eyed adjustment. 2. Research before advising. Do not build competitive positioning from general knowledge alone; use WebSearch for current information. 3. Make it actionable. Every section answers "What do I do next?" If a section leads to no action, cut it. 4. Write for the rep, not the VP. Use direct, tactical language. This is a field guide, not a board deck. 5. Be specific about timing. "Send the ROI model to Sarah by Thursday at 2pm before her Friday leadership meeting" beats "follow up soon." 6. Do not manufacture information. Mark anything not found as a gap and recommend how the rep can get it. 7. Respect the competitive landscape. Highlight genuine differentiators; let the prospect draw conclusions rather than trashing competitors. 8. Think like the buyer. Every recommendation must pass "Would this make me more or less likely to buy?" Pushy tactics and artificial urgency destroy trust. ## Edge Cases - **No competitors identified**: Build a competitive section against the status quo (doing nothing, building in-house, manual processes). Every deal competes against inaction. - **Very early stage deal**: Focus on qualification and discovery; the closing strategy becomes an advancement strategy. Do not write negotiation tactics for a pre-demo deal. - **Stalled deal**: Diagnose why it stalled (timing, budget, champion left, competing priority) and build a re-engagement strategy around a new compelling event. - **Renewal/expansion deal**: Shift from acquisition to retention framing. Emphasize value delivered, usage data, and ROI proof over competitive positioning. - **Multi-product deal**: Map each product to a different stakeholder and use case. Build separate value propositions per product line under a unified closing strategy.
© OneWave-AI · MIT · OneWave-AI/claude-skills