skills/sales-playbook/SKILL.md
Create and refine sales playbooks, deal strategies, MEDDPICC analyses, customer decks, and outreach sequences. Use for any sales methodology work, pipeline review, or go-to-market planning.
npx skillsauth add espennilsen/pi sales-playbookInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build sales artifacts grounded in MEDDPICC methodology and Espen's enterprise AI sales experience.
For every deal analysis, score each dimension (1-3: weak/moderate/strong) and identify gaps:
| Dimension | Question | |-----------|----------| | Metrics | What measurable outcomes does the customer expect? | | Economic Buyer | Who has budget authority? Have we engaged them? | | Decision Criteria | What technical/business criteria drive the decision? | | Decision Process | What are the steps, timeline, and approvals needed? | | Paper Process | What legal/procurement steps are required to close? | | Implicate the Pain | What happens if they do nothing? Is the pain urgent? | | Champion | Who inside is selling on our behalf? Can they mobilize? | | Competition | Who else is being evaluated? What's our differentiation? |
When creating a playbook, use this structure:
# [Product/Segment] Sales Playbook
## Ideal Customer Profile
- Industry, size, tech stack, pain signals
## Value Proposition
- 1-sentence elevator pitch
- 3 key differentiators vs. status quo
- 3 key differentiators vs. competition
## Discovery Questions
- 5-7 open questions that uncover MEDDPICC dimensions
## Objection Handling
| Objection | Response Framework |
|-----------|-------------------|
## Proof Points
- Customer stories, metrics, case studies
## Competitive Positioning
- Feature comparison, narrative reframes
## Sales Motion
- Prospecting → Discovery → Demo → Proposal → Close
- Time-to-close benchmark, typical deal size
# [Campaign Name] Outreach Sequence
## Target Persona
Role, industry, pain points, trigger events
## Sequence (10-14 days)
### Day 1 — Email 1: Pain-led hook
### Day 3 — LinkedIn connect + note
### Day 5 — Email 2: Social proof
### Day 8 — Call attempt + voicemail
### Day 10 — Email 3: Insight share
### Day 14 — Email 4: Break-up
## Personalization Variables
- {{company_pain}}, {{relevant_metric}}, {{mutual_connection}}
tools
# pi-a2a Long-Running Tasks Skill ## Overview The pi-a2a extension supports **long-running tasks** that can execute for hours or days without timeouts. This is essential for: - Data processing pipelines - Batch operations - Research and aggregation tasks - External API jobs with unpredictable duration - Any A2A task that exceeds the standard timeout ## When to Use **Use long-running tasks when:** - Task execution time is unpredictable or known to exceed 10 minutes - The remote agent is proc
development
Orchestrate cmux terminal panes — split terminals, run parallel processes, read output from other panes, and use the built-in browser. Use when working inside cmux and you need to run a dev server, watch tests, spawn sub-agents, or preview web pages.
testing
Review UI designs and implementations for accessibility, consistency, usability, and visual quality. Use when asked to review a design, audit accessibility, check UI consistency, compare implementation against mockups, or evaluate a user interface.
tools
Create, review, and improve skills for Pi agents. A skill is a folder with a SKILL.md that teaches an agent specialized workflows, domain knowledge, or tool integrations. Use when asked to create a new skill, improve an existing skill, review a skill for quality, scaffold a skill from a workflow, or convert documentation into a skill. Also triggers on "make a skill for", "build a skill", "skill for [topic]", "teach the agent to", or "package this workflow as a skill".