Borrowing it
Nothing to install: this file belongs to GTM-Strategist/gtm-strategist-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GTM-Strategist/gtm-strategist-skills/master/.claude/skills/executing-sales/SKILL.mdgit clone --depth 1 https://github.com/GTM-Strategist/gtm-strategist-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gtm-strategist/gtm-strategist-skills/executing-sales)<a href="https://agentmods.dev/skills/gtm-strategist/gtm-strategist-skills/executing-sales"><img src="https://agentmods.dev/badge/skills/gtm-strategist/gtm-strategist-skills/executing-sales/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gtm-strategist/gtm-strategist-skills/executing-sales"><img src="https://agentmods.dev/badge/skills/gtm-strategist/gtm-strategist-skills/executing-sales.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00079 | $0.06525 |
| Opus 5 | $0.00039 | $0.03263 |
| Sonnet 5 | $0.00016 | $0.01305 |
| Haiku 4.5 | $0.00008 | $0.00653 |
Grade A, and why
executing-sales scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 12: Executing Sales — Building Your Sales Engine
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.
Before You Start
-
Read
my-gtm-context.mdat 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.mdoroutputs/06-*(positioning and messaging)outputs/03-icp-profile.mdoroutputs/03-*(validated ICP and personas)outputs/05-pricing-*.md(pricing strategy and business model)outputs/07-*(launch assets — website, demo, pitch deck)outputs/10-*oroutputs/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.
Task 1: Sales Deck
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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 454 lines · 79 tokens per session scan A 939bcaa930a3
executing-sales is a skill published in the GitHub repository GTM-Strategist/gtm-strategist-skills (254 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 6,525 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…