SkillAgentSearch skills...

afrexai-sales-playbook

Complete B2B sales system — from ICP to closed-won. Discovery frameworks, objection handling, pipeline management, forecasting, and deal acceleration. Works for any B2B company.

Install / Use

npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-sales-playbook

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of afrexai-sales-playbook

afrexai-sales-playbook scores 90/100 on our quality scale, 1222nd of 2,780 Automation skills we index (top 44%).

Its SKILL.md is 29 KB long, well organised into 42 sections with 17 code examples: a thorough specification that gives an agent plenty to work with.

With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-10-30 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

afrexai-sales-playbook compared with similar skills

All 4 of these similar skills score higher than afrexai-sales-playbook; compare them before choosing.

SkillScoreStarsUpdatedFormat
afrexai-sales-playbook (this skill)by LeoYeAI902.1k4mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install afrexai-sales-playbook?
Run npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-sales-playbook. The install tabs above show the steps for each supported agent.
Which AI agents does afrexai-sales-playbook work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is afrexai-sales-playbook safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is afrexai-sales-playbook still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: afrexai-sales-playbook version: 1.0.0 description: "Complete B2B sales system — from ICP to closed-won. Discovery frameworks, objection handling, pipeline management, forecasting, and deal acceleration. Works for any B2B company." author: afrexai tags: sales, b2b, pipeline, crm, deals, closing, objections, forecasting, revenue

B2B Sales Playbook ⚡

The complete system for running a repeatable, scalable B2B sales operation.

Not a CRM wrapper. Not a template collection. This is a full sales methodology — from identifying your ideal customer to closing the deal and expanding the account.


Phase 1: Ideal Customer Profile (ICP) & Territory

ICP Definition Template

icp:
  company:
    industry: [SaaS, Fintech, Healthcare, etc.]
    size_employees: [50-500]
    size_revenue: [$5M-$50M ARR]
    geography: [US, UK, DACH, etc.]
    tech_stack: [signals they use tools you integrate with]
    growth_stage: [Series A-C, post-PMF, scaling]
    
  pain_indicators:  # Observable signals, not assumptions
    - hiring_for: [roles that signal the pain you solve]
    - tech_adoption: [recently adopted X tool = need for Y]
    - org_changes: [new VP of X = budget for initiatives]
    - regulatory: [upcoming compliance deadline]
    - public_statements: [earnings call mentions, press releases]
    
  buyer_personas:
    economic_buyer:  # Signs the check
      title_patterns: [VP Sales, CRO, CEO]
      cares_about: [revenue growth, cost reduction, competitive advantage]
      speaks_in: [ROI, board metrics, market share]
      
    champion:  # Fights for you internally
      title_patterns: [Director, Head of, Senior Manager]
      cares_about: [team productivity, career advancement, solving daily pain]
      speaks_in: [workflow, efficiency, team capacity]
      
    technical_evaluator:  # Validates feasibility
      title_patterns: [Engineering Manager, Architect, IT Director]
      cares_about: [integration, security, maintenance burden]
      speaks_in: [APIs, uptime, migration effort]
      
    end_user:  # Uses it daily
      title_patterns: [Individual contributors]
      cares_about: [ease of use, time saved, fewer context switches]
      
  anti-signals:  # DO NOT pursue
    - company_size_under: 20  # too small, long sales cycle for low ACV
    - no_budget_indicator: [startup pre-revenue, recent layoffs >30%]
    - tech_mismatch: [on-prem only, legacy stack incompatible]
    - cultural: [committee-driven decisions with 6+ stakeholders at low ACV]

Territory Planning

Account Tiering:

| Tier | Criteria | Accounts | Time Allocation | Touch Frequency | |------|----------|----------|-----------------|-----------------| | Tier 1 | Perfect ICP fit + active pain signals | 20-30 | 50% of time | 2-3x/week | | Tier 2 | Good ICP fit, no active signals yet | 50-80 | 30% of time | 1x/week | | Tier 3 | Partial fit, worth monitoring | 100-200 | 15% of time | 2x/month | | Inbound | Any qualified inbound | Variable | 5% of time | Respond <1hr |

Monthly Territory Review:

  1. Re-score all Tier 1 accounts — any demote to Tier 2?
  2. Scan Tier 2 for new signals — any promote to Tier 1?
  3. Remove dead accounts from Tier 3 (no engagement in 90 days)
  4. Add new accounts from prospecting
  5. Calculate territory coverage: (accounts with activity / total) — target >80% for Tier 1

Phase 2: Prospecting & Outreach

Multi-Channel Sequence Framework

Principle: No single channel works. Layer them.

Standard Tier 1 Sequence (14 days):

| Day | Channel | Action | Goal | |-----|---------|--------|------| | 1 | Email | Personalized cold email (see template below) | Open + reply | | 1 | LinkedIn | View profile + connect (NO pitch in connect msg) | Warm the name | | 3 | Email | Follow-up with value add (article, insight, data) | Demonstrate expertise | | 5 | LinkedIn | Comment on their recent post (genuine, not salesy) | Build familiarity | | 7 | Phone | Cold call (see script below) | Live conversation | | 7 | Email | Voicemail follow-up email | Multi-touch reinforcement | | 10 | LinkedIn | Send message referencing your email/call attempts | Channel switch | | 12 | Email | Breakup email (creates urgency) | Force response | | 14 | Phone | Final attempt | Last touch |

Sequence Rules:

  • STOP the sequence the moment they reply (positive OR negative)
  • Never send more than 1 email per day to the same person
  • Personalization must reference something SPECIFIC (their company, role, recent news)
  • If they open but don't reply 3x → they're reading, switch to phone
  • If zero engagement after full sequence → move to Tier 3, retry in 90 days

Cold Email Templates

Template 1: The Trigger Event

Subject: [Trigger event] → quick thought

[First name],

Saw [specific trigger — new hire, funding, product launch, earnings mention].

When [companies in their situation] hit this stage, [specific problem] usually becomes the bottleneck — [data point or example].

[One sentence on how you solve this, tied to the trigger.]

Worth a 15-min call to see if this applies to [company]?

[Your name]

Template 2: The Peer Reference

Subject: How [similar company] solved [problem]

[First name],

[Similar company in their industry] was dealing with [specific problem] — [quantify: X hours/week, $Y lost, Z% error rate].

They [brief result: cut X by 40%, saved $Y/month, shipped Z days faster].

Happy to share what they did differently — no pitch, just the playbook.

15 min this week?

[Your name]

Template 3: The Breakup

Subject: Closing the loop

[First name],

I've reached out a few times about [problem/topic] — I'll assume the timing isn't right.

If [problem] becomes a priority later, I'm here. 

Deleting your reminder from my CRM now.

[Your name]

Why breakup emails work: 30-40% reply rate. People respond to loss aversion. "Deleting your reminder" creates fear of losing access.

Cold Call Script

Opening (first 10 seconds decide everything):

"Hi [Name], this is [You] from [Company]. 
Did I catch you at an okay time?"

[If yes:]
"I'll be brief. I noticed [trigger/signal] and wanted to ask —
are you currently dealing with [specific problem]?"

[If they confirm the problem:]
"Got it. What's that costing you right now — in time, money, or headaches?"

[Let them talk. Take notes. Ask follow-up questions.]

"That's exactly what we help with. [One sentence proof point.]
Would it make sense to set up 20 minutes this week to dig into this properly?"

Common cold call responses + rebuttals:

| They Say | You Say | |----------|---------| | "Not interested" | "Totally fair — can I ask, is it because [problem] isn't a priority, or you've already solved it?" | | "Send me an email" | "Happy to — what specifically would be most useful to include? That way I don't waste your time." | | "We already have a solution" | "Good — how's it working? Most companies I talk to have something in place but still have gaps in [specific area]." | | "Bad timing" | "When would be better? I can put a reminder in for [suggested date]." | | "How did you get my number?" | "LinkedIn / your website. I know cold calls aren't fun — I'll keep it under 2 minutes." |


Phase 3: Discovery — The Most Important Meeting

MEDDPICC Qualification Framework

Score each element 1-3 (1=unknown, 2=partially known, 3=fully confirmed):

deal_qualification:
  metrics:  # Quantifiable impact they care about
    score: [1-3]
    detail: "[What numbers matter? Revenue increase, cost reduction, time saved?]"
    source: "[Who told you? Validated how?]"
    
  economic_buyer:  # Person with budget authority
    score: [1-3]
    name: "[Name and title]"
    access: "[Have you spoken to them directly?]"
    priority: "[Is this in their top 3 priorities?]"
    
  decision_criteria:  # How they'll evaluate options
    score: [1-3]
    technical: "[Integration, security, performance requirements]"
    business: "[ROI threshold, payback period, risk tolerance]"
    political: "[Internal politics, competing priorities]"
    
  decision_process:  # How they'll make the decision
    score: [1-3]
    steps: "[What happens between now and signed contract?]"
    timeline: "[When do they need to decide? Hard deadline?]"
    stakeholders: "[Who's involved? Who has veto power?]"
    
  paper_process:  # Legal/procurement steps
    score: [1-3]
    procurement: "[Standard terms or custom negotiation?]"
    legal_review: "[How long does legal take? Past precedent?]"
    security_review: "[Required? How long?]"
    
  identified_pain:  # The problem driving this
    score: [1-3]
    pain: "[What hurts? What breaks?]"
    impact: "[Cost of inaction — quantified]"
    urgency: "[Why now? What happens if they wait?]"
    
  champion:  # Your internal advocate
    score: [1-3]
    name: "[Who is it?]"
    motivation: "[Why do THEY personally care?]"
    power: "[Can they influence the economic buyer?]"
    coached: "[Have you prepped them for internal selling?]"
    
  competition:  # What you're up against
    score: [1-3]
    competitors: "[Named competitors in the evaluation]"
    status_quo: "[Doing nothing is always a competitor]"
    differentiation: "[Why you win against each]"
    
  total_score: "[X/24]"
  # 20-24 = Strong deal, forecast confidently
  # 15-19 = Gaps to fill, work the unknowns
  # 10-14 = At risk, needs significant work
  # <10 = Unqualified, don't invest time

Discovery Questions by Category

Situation (understand current state):

  1. Walk me through how [process] works today, start to finish.
  2. What tools/systems are involved?
  3. How many people touch this process?
  4. How long has it been this way?

Problem (surface the pain): 5. Where does it break down? 6. What's the impact when it fails? (Get a NUMBER) 7. How often does that happen? 8. What have you tried to fix it? 9. Why didn't that work?

Implication (expand the pain): 10. If this doesn't get fixed in the next 6 months, what happens? 11. How does this affect [their boss / their team / the company]? 12. What's the cost of doing nothing? (Force them to quantify) 13. What other initiatives depend on solving this?

Need-Payoff (let THEM sell the solution): 14. If you could wave a magic wand, what would this look like? 15. What would it mean for your team if [pain] went away? 16. If you could get [specific metric improvement], what would that unlock? 17. How would [their boss] react to those results?

Process (map the buying journey): 18. Besides you, who else needs to weigh in on this? 19. What's happened before when you've bought software like this? 20. Is there a budget allocated, or would this need approval? 21. What's the ideal timeline for having this running? 22. What would kill this deal?

Discovery Call Structure (30 min)

| Segment | Time | What You Do | |---------|------|-------------| | Opening | 2 min | Confirm agenda, set expectations, get permission to ask questions | | Context | 5 min | Ask situation questions — understand their world | | Pain | 10 min | Ask problem + implication questions — go DEEP on 1-2 pains | | Vision | 5 min | Ask need-payoff questions — paint the future state | | Process | 5 min | Map decision process, timeline, stakeholders | | Next Steps | 3 min | Agree on SPECIFIC next action with date |

Golden Rule: Talk <30% of the time. If you're talking more, you're pitching, not discovering.


Phase 4: Demo & Presentation

The Problem-Solution-Proof Framework

Never demo features. Demo outcomes.

Structure:

  1. Mirror their pain (2 min) — "You told me [specific pain from discovery]. Here's what that costs you: [quantified impact]."
  2. Show the solution (15 min) — Walk through their USE CASE, not a generic tour. Use THEIR data, THEIR terminology, THEIR workflow.
  3. Prove it works (5 min) — Case study of similar company. Before/after numbers. "Company X had the same problem. Here's

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryAutomation
Updated3mo ago
Forks325

Languages

Python

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 info