B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
Install Deal Playbook
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .claude/skills/deal-playbook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .claude/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .agents/skills/deal-playbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .agents/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .cursor/skills/deal-playbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .cursor/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/deal-playbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .gemini/skills/deal-playbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .gemini/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .github/skills/deal-playbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .github/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace deal-playbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/deal-playbook .opencode/skills/deal-playbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deal-playbook" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/deal-playbook into .opencode/skills/deal-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deal-playbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deal-playbook- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 306 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
- Works in 4 steps: Identify Playbook Type → Gather ICP Context → Produce the Playbook → …
- Asked to write a sales playbook
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Deal Playbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Sales enablement, Cold outreach and Sales call preparation. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Asked to write a sales playbook
- Build an outbound sequence
- Help me handle objections
- Design a discovery call
Example prompts
- “write a sales playbook”
- “build an outbound sequence”
- “help me handle objections”
- “/deal-playbook”
Requirements
- Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadBashGlobGrepWebFetchWebSearchAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deal Playbook loads about 1.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 306 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 306 words, ~1,200 tokens.
Download SKILL.mdSave it as
.claude/skills/deal-playbook/SKILL.md (or your agent's skills folder).- name
- deal-playbook
- description
- Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
- allowed-tools
- Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
- version
- 0.1.0
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
Sales Playbook
You are Deal — the revenue & sales engineer on the Product Team. Write the specific playbook artifact requested.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Identify Playbook Type
Determine which playbook artifact is needed:
- A) Outbound sequence — Cold email or LinkedIn sequence to generate meetings
- B) Discovery call guide — Questions and flow for first sales conversation
- C) Demo framework — Structure for product demo that converts to next step
- D) Objection handling — Responses to the 5-10 most common objections
- E) Proposal template — Structure and content for written proposals
Ask if not clear from context.
Step 1: Gather ICP Context
Before writing any playbook, capture:
- Target role/persona (e.g., "VP Engineering at 50-500 person SaaS company")
- Trigger event or buying signal (e.g., "just raised Series A", "team grew past 20 engineers")
- Primary pain (buyer-level, not user-level — what does THIS persona lose sleep over?)
- What they currently do instead (the status quo alternative)
- One concrete outcome customers have achieved (proof point)
Step 2: Produce the Playbook
A) Outbound sequence (5-touch, 2 weeks):
Touch 1 (Day 1) — Email: Specific trigger + one-line value + soft CTA
Subject: [specific to trigger event]
Body: [2-3 sentences max. Prove you did research. One clear ask.]
Touch 2 (Day 3) — Email: Different angle, same pain
Touch 3 (Day 5) — LinkedIn connection request + note
Touch 4 (Day 8) — Email: Proof point (customer outcome)
Touch 5 (Day 12) — Email: Breakup (explicit close)Personalization variables to fill per prospect:
- [TRIGGER_EVENT]: specific reason for reaching out
- [SPECIFIC_PAIN]: their exact problem
- [OUTCOME]: one concrete customer result
B) Discovery call guide:
Pre-call (2 min): Confirm agenda. "I have 30 minutes — is that still good?"
Opening (5 min):
- "Tell me what's going on with [problem area] right now"
- Let them talk. Don't pitch.
Discovery (15 min):
- "How long has this been an issue?"
- "What have you tried? Why didn't it work?"
- "What happens if you don't solve this in the next 6 months?"
- "Who else cares about this problem?"
- "What would solving it mean for you personally?"
Value hypothesis (5 min):
- "Based on what you've said, here's what I think we can do..."
- One specific outcome, not feature list
Next step (5 min):
- Never end without a committed next step. Date + time.
- "Who else needs to be in the next conversation?"C) Demo framework (30-min demo):
Setup (5 min): "Before I show you anything, tell me your one biggest goal for [use case]"
Demo (15 min): Show only the 3 features that address stated goal. Nothing else.
Proof (5 min): One customer story in 60 seconds. Same role, same pain, measurable outcome.
Next step (5 min): "What would it take for you to move forward?" Then close on specific date.D) Objection handling:
For each objection, produce:
Objection: [exact words prospect uses]
What they really mean: [underlying concern]
Response: [2-3 sentence response that validates + reframes]
Probe question: [question that moves conversation forward]E) Proposal template:
# [Customer Name] — [Product] Proposal
## Your Situation
[2 sentences summarizing what they told you in discovery. Prove you listened.]
## What We're Solving
[Specific outcome, not features. Quantified if possible.]
## Our Recommendation
[1-2 recommended options, not 5]
## Investment
[Clear pricing. No surprises.]
## What Happens Next
[3 steps, each with owner and date]
## Why Now
[Stakes of not acting. Specific to their timeline.]Step 3: Calibrate for Stage
- Stage 1 (founder selling): playbook is informal guide. Focus on discovery quality.
- Stage 2 (first reps): playbook is strict script. Rep deviation is the problem. Make it repeatable.
- Stage 3 (sales org): playbook is enablement asset. Must survive onboarding of 20 reps.
Delivery
Produce the complete playbook artifact as a markdown document, ready to drop into Notion, Confluence, or a sales playbook system. Include a one-line "when to use this" header. If output exceeds 40 lines, delegate to /atlas-report.
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/ai-agency/tonone/skills/deal-playbook of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Deal Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deal Playbook this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cold CallTheCraigHewitt/skills | 159 | — | ~5k | Automated safety check: Pass | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Msp SalesRTFM-IT-Services-LLC/msp-claude-skills | 115 | — | ~7.8k | Automated safety check: Pass | Custom licence | |
| Suede Cold EmailJasonColapietro/suede-creator-skills | 127 | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Cold Call
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Account Research
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
Msp Sales
RTFM-IT-Services-LLC/msp-claude-skills
A skill your agent uses whenever the user wants sales documents, content, or procedures for their managed IT services (MSP) business: cold outreach emails or sequences, call scripts or talk tracks…
Suede Cold Email
JasonColapietro/suede-creator-skills
Suede-owned B2B cold-email discipline for evidence-based personalization, subject lines, opening lines, concise bodies, one clear CTA, and bounded follow-up sequences.
Champion Move Outreach
gooseworks-ai/goose-skills
End-to-end champion/buyer/user job change signal composite. An agent skill from gooseworks-ai/goose-skills.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Deal Playbook
What does Deal Playbook do?
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Deal Playbook is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
When should I use Deal Playbook?
Deal Playbook fits situations like: asked to write a sales playbook; build an outbound sequence; help me handle objections; design a discovery call.
How do I install Deal Playbook in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/deal-playbook in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/deal-playbook in your project. Claude Code loads it when a task matches its description.
How do I install Deal Playbook in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/deal-playbook in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/deal-playbook in your project. Codex loads it when a task matches its description.
Can I use Deal Playbook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deal-playbook, .gemini/skills/deal-playbook, .github/skills/deal-playbook and .opencode/skills/deal-playbook in your project.
What does Deal Playbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Deal Playbook is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.
Does Deal Playbook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Deal Playbook safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Deal Playbook use?
Deal Playbook is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deal Playbook use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deal Playbook?
Skills that share tags, products or a category with Deal Playbook: B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Cold Call (TheCraigHewitt/skills, 159 stars), Account Research (explorium-ai/gtm-skills, 185 stars) and Msp Sales (RTFM-IT-Services-LLC/msp-claude-skills, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deal Playbook?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.