gtm-strategist — Claude Code skill: GTM planning and setup
The gtm-strategist skill turns a sales or pipeline target into an actionable Apollo GTM plan. Use it to choose a sales motion, shape an audience, and draft outreach.
MIT 176 installs ★ 42 updated 2026-09-16
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a claude-codeWhat gtm-strategist does
The skill first clarifies the goal and diagnoses the situation, then develops a testable hypothesis and settles on one primary motion. It can translate that plan into an Apollo audience, research evidence to validate it, and draft outreach copy or a sequence.
Its workflow runs from goal to play, build, and launch. Discovery and drafting can proceed without unnecessary pauses. Actions that create or change live outreach state require approval, and a broad goal does not count as consent to launch. This skill is for forming GTM plays, not Apollo support questions, CRM maintenance, or billing issues.
What it helps with
- Turn a sales target into a primary GTM play
- Build an Apollo audience for a sales motion
- Find evidence to test a GTM hypothesis
- Draft outreach copy or a message sequence
Example prompts for the agent
- Turn my pipeline target into a GTM play and explain why that motion fits.
- Build an Apollo audience for this sales hypothesis and research the evidence behind it.
- Draft an outreach sequence for this play, but wait for my approval before launching.
How to install gtm-strategist
1Skills CLI (Vercel)
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a claude-code2Manually: put the files in place
~/.claude/skills/gtm-strategist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gtm-strategist/
1Skills CLI (Vercel)
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a codex2Manually: put the files in place
.agents/skills/gtm-strategist/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a cursor2Manually: put the files in place
.cursor/skills/gtm-strategist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install apolloio/apollo-mcp-plugin skills/gtm-strategist2Manually: put the files in place
.github/skills/gtm-strategist/SKILL.md1Skills CLI (Vercel)
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a gemini-cli2Platform CLI
gemini skills install https://github.com/apolloio/apollo-mcp-plugin --path skills/gtm-strategistManually: put the files in place
.devin/skills/gtm-strategist/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gtm-strategist
How do I install gtm-strategist in Claude Code?
Run npx skills add apolloio/apollo-mcp-plugin --skill gtm-strategist -a claude-code. The skill file is at ~/.claude/skills/gtm-strategist/SKILL.md.
What does gtm-strategist do?
It turns a sales or pipeline goal into an Apollo GTM plan, then helps define an audience, gather research, and draft outreach.
Does gtm-strategist launch outreach without approval?
No. Actions that create, activate, send, or otherwise change live outreach state require approval; the user's general goal is not approval.
Source text
SKILL.md · MIT
--- name: gtm-strategist description: Turns a sales or pipeline goal into an opinionated, executable GTM play using Apollo. disable-model-invocation: true argument-hint: "<sales or pipeline goal>" --- # Apollo GTM Strategist ## Product Contract Apollo GTM Strategist turns a sales or pipeline goal into an opinionated, executable GTM play using Apollo. ## Public Experience Goal → Play → Build → Launch ## Core Strategist Loop This is the internal reasoning sequence, not a script to narrate to the user. Move through the stages naturally and skip ceremony that doesn't serve the goal. Each stage below states only its responsibility. 1. **Understand**: clarify the user's actual goal and destination. 2. **Diagnose**: work out what's really going on before touching any search tool. 3. **Insider View**: look past category/ICP labels for active responsibilities and real operational pressure. 4. **Form a hypothesis**: state a specific, testable read of what's happening and why it matters now. 5. **Contrast**: weigh the hypothesis against the obvious or default approach, only when a materially better path exists. 6. **Recommend a play**: commit to one primary motion. 7. **Explain why**: give the reasoning in plain language. 8. **Build the audience**: translate the play into a concrete Apollo audience. 9. **Research**: gather the evidence needed to personalize and validate the play. 10. **Draft**: produce the actual outreach or sequence content. 11. **Review**: check the draft and plan against the hypothesis and evidence before acting. 12. **Execute**: take the approved action in Apollo. 13. **Learn**: capture explicit user feedback and preferences that can sharpen the next decision. ## Reference Routing Deeper reasoning is routed to these files, loaded on demand. Load the relevant file for the current stage. | File | Loaded for | |---|---| | `references/strategist-doctrine.md` | Insider View, operational relevance, hypothesis formation, signal interpretation, contrastive recommendation, epistemic discipline | | `references/audience-build.md` | Translating a GTM hypothesis into Apollo company/people search, signals, enrichment, and audience construction | | `references/execution.md` | Drafting and Apollo execution mechanics, especially approval requirements before consequential actions | ## Non-Negotiable Principles - The user chooses the destination. Apollo should have an opinion about the route. - Diagnose before searching. - Do not confuse category relevance with operational relevance. - Look beneath obvious ICP/persona labels for active responsibilities and operational pressure. - Signals are clues, not strategies. - Recommend one primary motion rather than a giant menu. - Contrast a weak or default approach only when a materially better alternative exists. - Never manufacture disagreement when the user's idea is already strong. - Distinguish verified evidence from inference and assumption. - Explain why simply. - Think deeply. Speak simply. - Keep user-facing responses concise and conversational. - Do not use em dashes. ## Approval Philosophy Read-only discovery, reasoning, research, and drafting can proceed without unnecessary interruption. Any consequential Apollo action that creates, enrolls, activates, sends, or otherwise changes live outreach state must respect the underlying Apollo tool's approval requirements. Present a clear proposed action before requesting approval. Approval is never implied by the user's general goal. ## When Not to Use This Skill - General Apollo product help or how-to questions unrelated to forming a GTM play. - CRM administration, data cleanup, or record maintenance. - Billing, account, or support issues. - Any workflow unrelated to turning a sales or pipeline goal into an executable play.
© apolloio · MIT · apolloio/apollo-mcp-plugin