Case Study Builder
BrianRWagner/ai-marketing-claude-code-skills
Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.
A skill your agent uses when the user wants to build their sales engine — sales deck, case studies, outbound campaigns, partnership programs, or ABM strategy.
$ npx skills add GTM-Strategist/gtm-strategist-skills --skill executing-sales -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills executing-sales --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/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/executing-sales .claude/skills/executing-sales && 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 "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .claude/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-salesType 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 GTM-Strategist/gtm-strategist-skills --skill executing-sales -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills executing-sales --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/executing-sales .agents/skills/executing-sales && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .agents/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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 GTM-Strategist/gtm-strategist-skills --skill executing-sales -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills executing-sales --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/executing-sales .cursor/skills/executing-sales && 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 "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .cursor/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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/GTM-Strategist/gtm-strategist-skills.git --path .claude/skills/executing-sales--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 GTM-Strategist/gtm-strategist-skills --skill executing-sales -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills executing-sales --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/executing-sales .gemini/skills/executing-sales && 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 "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .gemini/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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 GTM-Strategist/gtm-strategist-skills executing-salesInstalls 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 GTM-Strategist/gtm-strategist-skills --skill executing-sales -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/executing-sales .github/skills/executing-sales && 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 "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .github/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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 GTM-Strategist/gtm-strategist-skills --skill executing-sales -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GTM-Strategist/gtm-strategist-skills executing-sales --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/executing-sales .opencode/skills/executing-sales && 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 "executing-sales" agent skill from https://github.com/GTM-Strategist/gtm-strategist-skills/tree/master/.claude/skills/executing-sales into .opencode/skills/executing-sales/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executing-sales", 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.
executing-salesA skill your agent uses when the user wants to build their sales engine — sales deck, case studies, outbound campaigns, partnership programs, or ABM strategy.
Executing Sales is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user wants to build their sales engine — sales deck, case studies, outbound campaigns, partnership programs, or ABM strategy. Phase 12 of 12: interactive guided workflow for sales deck, one-pager, case studies, outbound campaigns, partnership programs, dream client lists, video selling, ABM, sales scripts, and customer exit interviews.
Its SKILL.md is about 7.1k 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. The repository describes itself as: Your AI go-to-market co-pilot. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a5ead26. It shows what the files ask for, not the result of running them.
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.
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.
Links to these hosts (documentation or services it may open):
gtmstrategist.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Executing Sales loads about 7.1k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 3,937 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.
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.
The full file from GTM-Strategist/gtm-strategist-skills at commit a5ead26, republished under its MIT licence (© GTM-Strategist). 3,937 words, ~7,147 tokens.
.claude/skills/executing-sales/SKILL.md (or your agent's skills folder).You are executing Phase 12 of the GTM Strategist methodology. This is the final phase. Everything the user has built across Phases 1-11 — positioning, ICP, messaging, pricing, marketing, launch — now gets converted into a repeatable sales engine. The goal is not "do sales." The goal is to build a system that generates pipeline, closes deals, and learns from every outcome.
Read my-gtm-context.md at the project root. Pay close attention to sections on ICP, pricing, product stage, and team resources. Sales execution must match the user's current capacity — a solo founder running enterprise ABM is a mismatch.
Check outputs/ for prior phase deliverables. This phase builds directly on:
outputs/06-positioning-statement.md or outputs/06-* (positioning and messaging)outputs/03-icp-profile.md or outputs/03-* (validated ICP and personas)outputs/05-pricing-*.md (pricing strategy and business model)outputs/07-* (launch assets — website, demo, pitch deck)outputs/10-* or outputs/11-* (GTM system and marketing)If prior outputs exist, reference them throughout. The sales deck, one-pager, and outbound campaigns should all be consistent with established positioning and messaging. If they don't exist, flag that the user is building sales assets without validated foundations — workable, but riskier.
Work one task at a time. Present the deliverable, get feedback, then move to the next. Don't dump all ten tasks at once.
Duration: 1-2 weeks | Output: outputs/12-sales-deck.md
A sales deck is NOT a pitch deck. A pitch deck sells your company to investors. A sales deck sells your solution to buyers. The entire narrative arc is about the buyer's world — not yours. If the first three slides are about your company history, team, and funding, start over.
What to do:
Read positioning outputs (outputs/04-*) and messaging outputs (outputs/05-*). The sales deck must be a direct expression of established positioning.
Guide the user through this structure (one slide per section):
For each slide, write the actual copy — not just bullet points about what should go there. The user should be able to hand this to a designer.
Add speaker notes for key slides: what to say, what objections to anticipate, where to pause for questions.
The deliverable should include: Full slide-by-slide deck content with copy, speaker notes, and design direction for each slide.
Duration: < 1 day | Output: outputs/12-one-pager.md
The one-pager is the sales leave-behind. It's what your champion shares internally when they need to get budget approval, buy-in from their boss, or alignment from another department. If you don't give them this, they'll write their own — and they'll get your value prop wrong.
What to do:
Read the sales deck output (outputs/12-sales-deck.md) if it exists, plus positioning and pricing outputs.
Build the one-pager with these sections:
Format guidance: this should fit on a single page when printed or exported to PDF. Use clear hierarchy — someone scanning it for 30 seconds should get the core message.
Write two versions if the user sells to multiple personas: one for the end user (pain-focused) and one for the economic buyer (ROI-focused).
The deliverable should include: Complete one-pager copy, layout guidance, and a note on when and how to use it in the sales process.
Duration: 1-2 weeks | Output: outputs/12-case-studies.md
Case studies are the most persuasive sales asset you can create. Nothing you say about your product is as credible as what a customer says. The challenge: most case studies are boring company-centric narratives that nobody reads. Fix that.
What to do:
Help the user identify 3-5 early customers or beta users for case studies. Prioritize:
For each case study, use this structure:
Provide interview questions the user can send to customers to gather the raw material. Keep it to 7-10 questions, framed as a casual conversation, not a formal interview.
Note on video testimonials: a 60-second video of a customer saying "this product saved us X" is worth more than any written case study. Encourage the user to ask for video alongside written quotes. Even a selfie-style iPhone video works.
The deliverable should include: Case study template, customer interview questions, and draft case studies for each identified customer (or placeholders with guidance if the user hasn't conducted interviews yet).
Duration: Ongoing (< 6 months to see results) | Output: outputs/12-outbound-campaign.md
Outbound is not "spray and pray." A structured outbound campaign is a system: defined targets, personalized sequences, multi-channel touchpoints, and tracked metrics. Most outbound fails because founders send 500 identical emails and call it a campaign.
What to do:
Read ICP outputs (outputs/03-*) and the dream client list (outputs/12-dream-client-list.md) if it exists.
Define the target list. Help the user build a list of 50-200 target accounts:
Craft the outbound sequence. Build a multi-channel sequence (typically 8-12 touchpoints over 3-4 weeks):
Personalization framework. Show the user how to personalize at scale:
Metrics to track:
Write the actual email copy for the full sequence. Each email should be under 150 words — brevity is respect for the reader's time.
The deliverable should include: Target list criteria, full sequence with copy for every touchpoint, personalization framework, and metrics dashboard template.
Duration: < 6 months | Output: outputs/12-partnership-program.md
Partnerships are a force multiplier — but only when they're structured. A handshake agreement to "share leads" produces exactly zero leads. Version 01 should be simple, specific, and easy for both sides to execute.
What to do:
Help the user identify which type of partnership fits their stage:
Identify 5-10 potential partners. Criteria:
Build the partnership one-pager. This is what you send to a potential partner:
Define the operating model for v01:
Start with ONE partnership. Get it working. Then replicate.
The deliverable should include: Partner criteria, prospect list, outreach one-pager, v01 operating model, and a 90-day pilot plan.
Duration: < 1 day | Output: outputs/12-dream-client-list.md
Your dream client list is the top 25-50 companies you'd love to have as customers. Not "anyone who might buy" — the specific companies where you'd get the highest value, strongest case studies, and most referrals. This list drives outbound (Task 4) and ABM (Task 8).
What to do:
Read ICP outputs (outputs/03-*). The dream list must match your validated ICP — not aspirational logos you'd love on your website but that don't fit your product.
Guide the user to build the list using these criteria:
Enrichment. For each dream client, capture:
Lookalike expansion. From the dream list, identify patterns and find similar companies:
Connect this list to the outbound campaign (Task 4): dream clients are your Tier 1 targets.
The deliverable should include: The ranked dream client list with enrichment data, lookalike expansion criteria, and notes on connection paths.
Duration: < 1 day | Output: outputs/12-video-selling.md
Personalized video messages cut through the noise in ways text cannot. A 60-second Loom video in a cold outreach sequence gets 3x the response rate of text alone. This is not about production quality — it's about human connection at scale.
What to do:
Identify where video fits in the sales process. Best use cases:
Video framework (60-90 seconds max):
Tool recommendations:
Tips for effectiveness:
Write 3 video script outlines tailored to the user's product and ICP: one for cold outreach, one for post-demo follow-up, and one for deal reactivation.
The deliverable should include: Video selling playbook with use cases, framework, tool recommendation, and 3 script outlines.
Duration: < 6 months | Output: outputs/12-abm-program.md
ABM flips the funnel. Instead of casting a wide net and qualifying down, you start with specific target accounts and build personalized campaigns to engage them. ABM works when your deal size justifies the per-account investment — if your ACV is under $5K, ABM is probably overkill.
What to do:
Qualify for ABM. Help the user assess if ABM is right for their stage:
If the answer is "not yet," recommend focusing on Tasks 4 and 6 first and revisiting ABM when the user has more traction.
Select target accounts. Pull from the dream client list (Task 6). ABM tiers:
Build the ABM playbook per tier:
Metrics for ABM:
Start with a 90-day pilot on Tier 1 accounts only. Prove the model before scaling.
The deliverable should include: ABM qualification assessment, tiered account list, per-tier playbook, content plan, and 90-day pilot structure with success criteria.
Duration: 1-3 hours | Output: outputs/12-sales-call-script.md
Not a word-for-word script — a framework. The best sales conversations feel like conversations, not pitches. But without a structure, founders either ramble through demos or forget to qualify. This framework ensures every call covers the essentials while staying natural.
What to do:
Read ICP outputs (outputs/03-*), positioning (outputs/04-*), and pricing (outputs/07-*).
Build the call framework in these stages:
Opening (2-3 minutes):
Discovery (10-15 minutes):
Write 8-12 specific discovery questions tailored to the user's product and ICP.
Qualification:
Demo / Solution Presentation (10-15 minutes):
Objection Handling:
Close (5 minutes):
Add a "Post-Call Checklist" — what the user should do within 1 hour of every call:
The deliverable should include: The full call framework with specific questions, objection responses, and post-call checklist.
Duration: 3-6 hours | Output: outputs/12-exit-interviews.md
Every churned customer and every lost deal contains intelligence that your competitors would pay for. Most companies never collect it. Exit interviews are uncomfortable — that's precisely why they're valuable.
What to do:
Help the user identify who to interview:
Target: 5-10 interviews. Even 3 will produce actionable insights.
Interview framework (20-30 minutes each):
Context:
Decision:
Product/Experience:
Recovery (for churns):
Open-ended:
Outreach approach. Getting people to do exit interviews is hard. Tips:
Synthesis framework. After interviews, organize findings into:
Action plan. For each finding category, recommend specific next steps — product roadmap input, sales process fixes, positioning adjustments, or pricing changes.
The deliverable should include: Interview framework, outreach email template, synthesis template, and (after interviews are conducted) a findings report with categorized insights and recommended actions.
After completing the tasks above, the user should have:
| Output | What It Enables |
|---|---|
12-sales-deck.md | A buyer-focused presentation that sells the transformation, not the product |
12-one-pager.md | A leave-behind that champions use to sell internally on your behalf |
12-case-studies.md | Third-party proof that your product delivers real results |
12-outbound-campaign.md | A structured, multi-channel system for generating pipeline |
12-partnership-program.md | A force multiplier that opens new channels without proportional effort |
12-dream-client-list.md | A prioritized hit list of high-value accounts to pursue |
12-video-selling.md | A human-connection advantage that cuts through inbox noise |
12-abm-program.md | A focused, high-touch approach for landing strategic accounts |
12-sales-call-script.md | A repeatable framework for qualifying, presenting, and closing |
12-exit-interviews.md | A feedback loop that turns losses into future wins |
This is the final phase. The user now has a complete GTM system — from strategic foundations (Phase 1) through customer validation, positioning, messaging, pricing, product, marketing, launch, and now sales execution. The system is never "done" — it's a loop. Exit interview findings feed back into positioning (Phase 4), customer discovery (Phase 2), and product development (Phase 8). Outbound results refine the ICP (Phase 3). Case studies fuel marketing (Phase 10-11). Every phase strengthens every other phase.
There is no Phase 13. From here, the user should:
GTM Strategist methodology by Maja Voje. https://gtmstrategist.com
© GTM-Strategist, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/executing-sales of GTM-Strategist/gtm-strategist-skills.
Open the folder on GitHubat commit a5ead26
Executing Sales 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 |
|---|---|---|---|---|---|---|
| Executing Sales this skillGTM-Strategist/gtm-strategist-skills | 263 | — | ~7.1k | Automated safety check: Pass | MIT | |
| Case Study BuilderBrianRWagner/ai-marketing-claude-code-skills | 440 | — | ~1.8k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 610 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sales Enablement Kitaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Battlecardsgrowthack88/growth-marketing-os | 116 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Competitive Battlecardphuryn/pm-skills | 27k | — | ~721 | Automated safety check: Pass | MIT |
BrianRWagner/ai-marketing-claude-code-skills
Turns a client win into case studies, proposal blurbs, social proof quotes and sales stories, after collecting the details and at least one concrete number.
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.
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch…
growthack88/growth-marketing-os
Creates competitive battlecards for sales deal conversations.
phuryn/pm-skills
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns.
gooseworks-ai/goose-skills
Research a specific competitor across their website, reviews, ads, social presence, and pricing — then produce a structured sales battlecard with positioning traps, objection handlers, landmine…
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to position their product in the market, craft messaging, define their UVP/USP, or build a visual identity.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to validate their customer assumptions, test their ICP, design experiments, or create customer personas from evidence.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to choose marketing channels, plan their launch newsletter, set a GTM budget, collect social proof, or build their communication strategy.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user wants to research competitors, plan customer interviews, conduct market research, or understand their competitive landscape.
GTM-Strategist/gtm-strategist-skills
A skill your agent uses when the user is preparing to launch, wants to set up a war room, build a launch support network, write launch emails, or plan launch day activities.
Categories
A skill your agent uses when the user wants to build their sales engine — sales deck, case studies, outbound campaigns, partnership programs, or ABM strategy. Executing Sales is an agent skill from GTM-Strategist/gtm-strategist-skills. Use this skill when the user wants to build their sales engine — sales deck, case studies, outbound campaigns, partnership programs, or ABM strategy.
Executing Sales fits situations like: the user wants to build their sales engine — sales deck; outbound campaigns; partnership programs.
Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill executing-sales -a claude-code`. Or copy the skill folder (.claude/skills/executing-sales in GTM-Strategist/gtm-strategist-skills) into .claude/skills/executing-sales in your project. Claude Code loads it when a task matches its description.
Run `npx skills add GTM-Strategist/gtm-strategist-skills --skill executing-sales -a codex`. Or copy the skill folder (.claude/skills/executing-sales in GTM-Strategist/gtm-strategist-skills) into .agents/skills/executing-sales in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GTM-Strategist/gtm-strategist-skills --skill executing-sales -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executing-sales, .gemini/skills/executing-sales, .github/skills/executing-sales and .opencode/skills/executing-sales in your project.
SKILL.md names no scripts, command-line tools or credentials: Executing Sales is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: gtmstrategist.com. This is read from the text; nothing was executed.
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.
Executing Sales is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 7.1k tokens (SKILL.md is roughly 29k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Executing Sales: Case Study Builder (BrianRWagner/ai-marketing-claude-code-skills, 440 stars), B2B Lead Generation (minhnv0807/ai-business-skills, 610 stars), Sales Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars) and Battlecards (growthack88/growth-marketing-os, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
GTM-Strategist (a GitHub organization) maintains it in GTM-Strategist/gtm-strategist-skills, which has 263 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 7, 2026.
Source: GTM-Strategist/gtm-strategist-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.