onewave-ai/claude-skills/deal-closer-playbook
Claude Code and agent skill by onewave-ai/claude-skills
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install onewave-ai/claude-skills/deal-closer-playbookSKILL.md
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 scoringreferences/playbook-strategy.md-- objection matrix, competitive positioning, stage-specific closing strategy, mutual close plan, proposal talking pointsreferences/output-template.md-- fulldeal-playbook.mdstructure to write
Workflow
Operate in two phases: gather intelligence, then generate the playbook. Be thorough but fast. Tie every section to a specific action.
- Collect deal context. Gather the required, valuable, and nice-to-have inputs. Ask for anything missing; mark unavailable items
[UNKNOWN]and work around them. Seereferences/intelligence-gathering.md. - 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. - 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. - Assess deal risk. Score MEDDIC qualification and the velocity risk checklist. See
references/intelligence-gathering.md. - Build the objection response matrix. Address every raised objection plus likely unraised ones for the stage and context. See
references/playbook-strategy.md. - 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. - Design the stage-appropriate closing strategy. Match tactics to discovery/demo, evaluation/proposal, or negotiation/close. See
references/playbook-strategy.md. - Build the mutual close plan. Create the shared buyer-seller timeline to signed contract. See
references/playbook-strategy.md. - Generate proposal talking points. Draft the opening, value prop, proof, differentiation, and the ask. See
references/playbook-strategy.md. - Write the deal playbook. Output the complete document to
deal-playbook.mdusingreferences/output-template.md.
Behavioral Rules
- Be honest about deal risk. If the deal is poorly qualified, say so -- false confidence is worse than a clear-eyed adjustment.
- Research before advising. Do not build competitive positioning from general knowledge alone; use WebSearch for current information.
- Make it actionable. Every section answers "What do I do next?" If a section leads to no action, cut it.
- Write for the rep, not the VP. Use direct, tactical language. This is a field guide, not a board deck.
- Be specific about timing. "Send the ROI model to Sarah by Thursday at 2pm before her Friday leadership meeting" beats "follow up soon."
- Do not manufacture information. Mark anything not found as a gap and recommend how the rep can get it.
- Respect the competitive landscape. Highlight genuine differentiators; let the prospect draw conclusions rather than trashing competitors.
- 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.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingdeal-closer-playbook/SKILL.md
Popularity
- Repository stars
- 269
- Repository forks
- 42
- 7-day trend score
- 28
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 24 Aug 2026, 2 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/onewave-ai/claude-skills/deal-closer-playbook)