Sales Script
shawnpang/startup-founder-skills
When a founder needs demo scripts, discovery call frameworks, objection handling, RFP/RFI responses, competitive feature matrices, POC planning, or closing playbooks.
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.
Install Discovery Call Playbook
$ npx skills add gtmagents/gtm-agents --skill discovery-calls -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gtmagents/gtm-agents discovery-calls --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/gtmagents/gtm-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .claude/skills/discovery-calls && 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 "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .claude/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-callsType 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 gtmagents/gtm-agents --skill discovery-calls -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gtmagents/gtm-agents discovery-calls --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .agents/skills/discovery-calls && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .agents/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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 gtmagents/gtm-agents --skill discovery-calls -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gtmagents/gtm-agents discovery-calls --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .cursor/skills/discovery-calls && 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 "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .cursor/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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/gtmagents/gtm-agents.git --path plugins/sales-prospecting/skills/discovery-calls--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 gtmagents/gtm-agents --skill discovery-calls -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gtmagents/gtm-agents discovery-calls --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .gemini/skills/discovery-calls && 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 "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .gemini/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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 gtmagents/gtm-agents discovery-callsInstalls 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 gtmagents/gtm-agents --skill discovery-calls -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .github/skills/discovery-calls && 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 "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .github/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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 gtmagents/gtm-agents --skill discovery-calls -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gtmagents/gtm-agents discovery-calls --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gtmagents/gtm-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/sales-prospecting/skills/discovery-calls .opencode/skills/discovery-calls && 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 "discovery-calls" agent skill from https://github.com/gtmagents/gtm-agents/tree/main/plugins/sales-prospecting/skills/discovery-calls into .opencode/skills/discovery-calls/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discovery-calls", 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
discovery-calls- GitHub stars
- 414
- Used in
- 1 other repo
- Token cost
- ~368 tokens
- SKILL.md length
- 144 words
- Files
- 3 (incl. references, assets)
- Skills in repo
- 121
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email.
- Works in 5 steps: PREP – Purpose, Research, Evidence, Plan… → Call Flow – Rapport & agenda → context →… → Question Set – workflow, trigger,… → …
- Preparing for a first call with a prospect booked from an outbound sequence
- SKILL.md covers When to Use, Framework, Templates and Tips
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill gives sales reps a repeatable way to plan, run and summarize a first call with a new prospect. It starts with PREP (purpose, research, evidence, plan) and then follows a call flow of rapport and agenda, context, pain and impact, vision, and next steps, with a question set on workflow, trigger, stakeholders, success criteria, urgency and budget.
Two bundled files support it: references/question_bank.md holds persona-specific questions, and assets/scorecard.md scores the answers against MEDDICC or BANT. A note-capture template covers company, initiatives, tools, pain, decision team, timeline and next actions, and a recap email outline runs from summary to insights to a confirmed next meeting. Tips include time-boxing a 30-minute call and sending the recap within an hour.
When your agent uses it
- Preparing for a first call with a prospect booked from an outbound sequence
- Giving SDRs and BDRs a structured script for early conversations
- Qualifying an opportunity against MEDDICC or BANT after the call
- Writing a post-call recap email that confirms next steps
Example prompts
- “Prep me for tomorrow's discovery call with the VP of Operations at a logistics company.”
- “Draft a 30-minute call plan using PREP for a prospect who downloaded our pricing guide.”
- “Turn my notes in ./notes/acme-call.md into a MEDDICC scorecard and a recap email.”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- PREP – Purpose, Research, Evidence, Plan before every call.
- Call Flow – Rapport & agenda → context → pain/impact → vision → next steps.
- Question Set – workflow, trigger, stakeholders, success criteria, urgency, budget.
- Note Capture – log company, initiatives, tools, pain, decision team, timeline, next actions.
- Qualification Overlay – map answers to MEDDICC/BANT to guide handoff.
What it can do on your machine
Read from SKILL.md and the folder at commit 78e0419. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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
Discovery Call Playbook loads about 368 tokens when it runs, and up to ~859 if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 144 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 passed
The automated check found no risky patterns in SKILL.md.
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 gtmagents/gtm-agents at commit 78e0419, republished under its Apache-2.0 licence (© gtmagents). 144 words, ~368 tokens.
Download SKILL.mdSave it as
.claude/skills/discovery-calls/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- discovery-calls
- description
- Use when planning, running, or summarizing discovery calls to uncover pain, timeline, and authority.
Discovery Calls Skill
When to Use
- New prospects booked from outbound/marketing sequences.
- SDRs/BDRs need a structured first-call script.
- AEs want to validate multi-threaded opportunities quickly.
Framework
- PREP – Purpose, Research, Evidence, Plan before every call.
- Call Flow – Rapport & agenda → context → pain/impact → vision → next steps.
- Question Set – workflow, trigger, stakeholders, success criteria, urgency, budget.
- Note Capture – log company, initiatives, tools, pain, decision team, timeline, next actions.
- Qualification Overlay – map answers to MEDDICC/BANT to guide handoff.
Templates
- Question Bank: See
references/question_bank.mdfor persona-specific questions. - Scorecard: See
assets/scorecard.mdfor MEDDICC/BANT qualification. - Notes Template:
Company / Persona:
Initiatives:
Current Tools / Process:
Pain / Impact:
Decision Team:
Timeline & Budget:
Next Actions:- Post-call recap email: (summary → insights → next meeting confirmation).
Tips
- Time-box sections (2/3/8/4/3) to keep 30-min calls crisp.
- Mirror the prospect’s vocabulary from research notes to build rapport fast.
- Always confirm next steps live and send recap within 1 hour.
- Tag recordings with chapters so AEs can jump to pain/impact moments.
© gtmagents, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references, assets) in plugins/sales-prospecting/skills/discovery-calls of gtmagents/gtm-agents.
- SKILL.md
- assets/scorecard.md
- references/question_bank.md
Open the folder on GitHubat commit 78e0419
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gtmagents/gtm-agents, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Discovery Call 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 |
|---|---|---|---|---|---|---|
| Discovery Call Playbook this skillgtmagents/gtm-agents | 414 | 1 repos | ~368 | Automated safety check: Pass | Apache-2.0 | |
| Sales Scriptshawnpang/startup-founder-skills | 343 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Deal Playbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Luopan Company Researchzhangxiaoqiang1991/luopan | 389 | — | ~998 | Automated safety check: Pass | MIT | |
| Company Researchstophobia/deerflow2.0-enhanced | 822 | — | ~845 | Automated safety check: Pass | MIT | |
| Meeting Prep BriefBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~922 | Automated safety check: Pass | None |
Similar skills
Deal Playbook
jeremylongshore/tons-of-skills-marketplace
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
Luopan Company Research
zhangxiaoqiang1991/luopan
罗盘的公司研究子模式。研究具体上市或非上市公司的财务增长、商业模式、 竞争生态位、治理与组织信号，并分别生成投资初筛和求职初筛。
Company Research
stophobia/deerflow2.0-enhanced
综合企业背景调研技能，用于尽职调查、合作伙伴评估、投资分析、市场研究等场景。支持公司工商信息、财务数据、法律风险、舆情分析、竞品对比等多维度调研，自动生成Markdown和HTML格式的专业调研报告。触发条件：用户提及"企业调研"、"公司背景"、"尽职调查"、"合作伙伴评估"、"投资分析"、"市场研究"等关键词。
Meeting Prep Brief
BrianRWagner/ai-marketing-claude-code-skills
Builds a pre-meeting brief from your Obsidian vault: participant research, past notes, open commitments, a prioritized agenda and sharp questions.
Sdt
StopDisTrain/sdt-skills
SDT 内容生产工具箱的总入口：根据当前任务选择最合适的 sdt- 模块，既能完成标题、开头等单一步骤，也能组织从账号研究到发布的完整流程。用户不知道该用哪个 SDT Skill，或希望一站式完成内容生产时使用。
More from gtmagents/gtm-agents
All 121 skills in this repoEnrichment Data Sourcing
gtmagents/gtm-agents
Chooses and orders data providers for email, phone, company and intent enrichment, with waterfall sequences and credit-saving tactics across 150+ sources.
Cold Email Personalization
gtmagents/gtm-agents
Writes personalized B2B cold emails from prospect research, using a gated workflow, a quality rubric and follow-up sequences.
Lifecycle Mapping for Automation
gtmagents/gtm-agents
Frames marketing automation around lifecycle stages, signals, touches and SLAs, with worksheets for onboarding, expansion, renewal and churn-prevention journeys.
Social Selling
gtmagents/gtm-agents
A skill your agent uses when engaging prospects through LinkedIn, communities, and social channels to spark warm conversations and meetings.
Drip Campaigns
gtmagents/gtm-agents
A skill your agent uses when you need to map sequenced nurture flows with pacing, storytelling arcs, and value ladders.
Editorial Ops
gtmagents/gtm-agents
A skill your agent uses when planning multi-channel editorial calendars, enforcing publishing cadences, and coordinating distribution workflows across GTM teams.
Related
Categories
Questions about Discovery Call Playbook
What does Discovery Call Playbook do?
Structures sales discovery calls with a PREP routine, a five-part call flow, a question bank, a qualification scorecard and a follow-up recap email. This skill gives sales reps a repeatable way to plan, run and summarize a first call with a new prospect. It starts with PREP (purpose, research, evidence, plan) and then follows a call flow of rapport and agenda, context, pain and impact, vision, and next steps, with a question set on workflow, trigger, stakeholders, success criteria, urgency and budget.
When should I use Discovery Call Playbook?
Discovery Call Playbook fits situations like: preparing for a first call with a prospect booked from an outbound sequence; giving SDRs and BDRs a structured script for early conversations; qualifying an opportunity against MEDDICC or BANT after the call; writing a post-call recap email that confirms next steps.
How do I install Discovery Call Playbook in Claude Code?
Run `npx skills add gtmagents/gtm-agents --skill discovery-calls -a claude-code`. Or copy the skill folder (plugins/sales-prospecting/skills/discovery-calls in gtmagents/gtm-agents) into .claude/skills/discovery-calls in your project. Claude Code loads it when a task matches its description.
How do I install Discovery Call Playbook in Codex?
Run `npx skills add gtmagents/gtm-agents --skill discovery-calls -a codex`. Or copy the skill folder (plugins/sales-prospecting/skills/discovery-calls in gtmagents/gtm-agents) into .agents/skills/discovery-calls in your project. Codex loads it when a task matches its description.
Can I use Discovery Call 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 gtmagents/gtm-agents --skill discovery-calls -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discovery-calls, .gemini/skills/discovery-calls, .github/skills/discovery-calls and .opencode/skills/discovery-calls in your project.
What does Discovery Call Playbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Discovery Call Playbook is instructions for the agent only.
Does Discovery Call 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 Discovery Call Playbook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Discovery Call Playbook use?
Discovery Call Playbook is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Discovery Call Playbook use?
About 368 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 491 tokens, read only when the agent opens those files.
What are the alternatives to Discovery Call Playbook?
Skills that share tags, products or a category with Discovery Call Playbook: Sales Script (shawnpang/startup-founder-skills, 343 stars), Deal Playbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Luopan Company Research (zhangxiaoqiang1991/luopan, 389 stars) and Company Research (stophobia/deerflow2.0-enhanced, 822 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Discovery Call Playbook?
gtmagents (a GitHub user) maintains it in gtmagents/gtm-agents, which has 414 GitHub stars. The repository holds 121 skills in this directory. The repository was last updated on April 3, 2026.
Source: gtmagents/gtm-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.