GTM Vault skills
Skills built from systems that already ran.
Every operator skill here is built from a system a named operator walked through on GTM Vault, with the episode, the timestamps and the number it produced. Download one into Claude, or run it through the GTM Vault MCP. Free for everyone. 18 operator skills and the 8 skills GTM Vault itself runs on.
Built from the systems of
26 of 26 skills
Signals and scoringFree
PQL scoring and routing agentScores every product signup out of 100 from product and CRM data, then routes it to sales or nurture.
Say “score our signups”“build a PQL model”“route product-qualified leads”“set up a website visitor agent”
To derive signals from closed-won and closed-lost history rather than product usage, use Win-loss gap signal discovery.
7 signals, scored out of 100Michael Bartimer scores each PLG signup on seven signals out of 100, about half pulled live from PostHog, with 60 or greater sales ready.
Signals and scoringFree
Review intelligence signal layerTurns public reviews into buying signals: a star filter before the model, then Claude flags fixable complaints.
Say “find accounts from reviews”“review intelligence”“mine Google reviews for leads”“negative review signals”
16 of 20 reviews dropped before the modelIn the test run Vinayak Mishra showed, the star-rating gate discarded 16 of 20 reviews and passed 4 to Claude.
Pipeline generationFree
Account monitoring universeScores a TAM on four layers, watches it for signals, and gates outreach from first signal to phone call.
Say “prioritize our account list”“which accounts should reps work this month”“build an account scoring model”“set up signal monitoring”
To put scored accounts in front of a BDR as one action layer, use Account scoring to a BDR action layer.
17 to 18 days down to the same dayUmar Farooq Adam said inbound lead time fell from 17 to 18 days to the same day once the universe was live.
Signals and scoringFree
Win-loss gap signal discoveryMines won against lost accounts for fit and anti-fit signals, scores targets, and stages gated outbound.
Say “find signals that predict wins”“build a propensity model”“win-loss analysis”“why do we lose deals we should win”
To score live product signups rather than mine history, use PQL scoring and routing agent.
Under 30 minutes, under $10Jai Toor said a month-long workflow that cost almost $2,000 now runs in under 30 minutes for under $10.
Pipeline generationFree
Outbound run from Claude CodeScrape, enrich, personalize and launch split-tested outbound campaigns from Claude Code prompts.
Say “build an outbound campaign in Claude Code”“scrape and enrich a list”“replace my Clay table with prompts”“set up a split test”
For the sending infrastructure underneath a campaign rather than the build itself, use Cold email as a GTM engine.
8 opportunities from 180 emailsTim Scheuer reported eight positive sales opportunities from just over 180 emails, set up in about 40 minutes of prompting.
Pipeline generationFree
Cold email as a GTM engineA lean cold email system: a cheap sending stack, layered ICP filters, a two-step offer and an AI post-call closer.
Say “build a cold email system”“set up cheap sending infrastructure”“my cold email lands in spam”“qualify my outbound list”
To build and split-test the campaign from prompts rather than stand up the stack, use Outbound run from Claude Code.
About $200 a monthCharles Cormier said he would need about 200 dollars a month to rebuild his whole cold email stack.
Data and contextFree
MCP and API enrichment pipelineSplits enrichment between MCP context checks and direct API volume calls, run by a supervisor agent.
Say “build me an enrichment pipeline”“MCP or API for enrichment”“stop emailing our customers”“enrich this list in Claude Code”
To expose the same enrichment to reps as one-click actions, use Enrichment actions in the rep's browser.
About 50 cents a leadAlexander Shartsis said Skyp runs managed enrichment at around 50 cents a lead after choosing which APIs it calls.
The rep surfaceFree
Agents behind the repHides an orchestrator and single-job outbound agents behind one rep action, such as a CRM checkbox.
Say “reps are not using our AI”“design our outbound agents”“build an agent workforce for BDRs”“one-click email drafts”
To give the rep one view across systems rather than one trigger, use Headless dashboard for AEs.
About 60% of the BDR workflowAngelo Quiambao said his agents became around 60% of the daily BDR workflow at Qualified.
Signals and scoringFree
Revenue intelligence layerScores target accounts and inspects pipeline against segment win rates, cycle lengths and stage gates.
Say “prioritize my accounts”“score our target accounts”“inspect the pipeline”“is 3x coverage enough”
5,000 scored MQAsMichele Shepard said Demandbase produced 5,000 scored MQAs at Emburse and saved 20 minutes per account.
Founder-led GTMFree
Get cited by AI searchPlan and measure how a B2B company gets seen, cited and chosen in ChatGPT, Perplexity and Claude.
Say “get us cited by ChatGPT”“GEO plan”“AI search visibility”“why do we not show up in Perplexity”
3 weeks to a monthJason Patel said to give it three weeks to a month before visibility shows, far quicker than SEO.
Pipeline generationFree
Account scoring to a BDR action layerScore the TAM in Clay, monitor signals only on accounts that clear the score, and give BDRs one action layer on the CRM.
Say “score our TAM”“prioritize accounts for BDRs”“turn intent signals into action”“my reps juggle the CRM, Sales Nav and Apollo”
To build the monitored universe before scoring it, start with Account monitoring universe.
30 to 60 minutes a dayGarrett Wolfe said the action layer saves reps as little as half an hour to an hour a day across his clients.
Data and contextFree
Enrichment actions in the rep's browserBring RevOps-built Clay workflows into the rep's browser as one-click actions that read the page, query Clay or the CRM, and write back.
Say “give reps access to our Clay tables”“build a Chrome extension for our sellers”“reps live in ZoomInfo but RevOps lives in Clay”“turn our Clay workflows into buttons”
To design the enrichment calls behind the buttons, use MCP and API enrichment pipeline.
The rep surfaceFree
Headless dashboard for AEsOne custom AE view joins CRM, data, outreach and back office sources, with engagement and call context written back automatically.
Say “my reps live in five tabs”“build a custom view on top of Salesforce”“reps will not update the CRM”“go headless on the CRM”
To hide the work behind a single rep action instead of a view, use Agents behind the rep.
Founder-led GTMFree
LinkedIn outbound with Loom demosFounder-led LinkedIn outbound to a known ICP, with one-minute personalized Loom demos and technical Reddit posts that build demand.
Say “build LinkedIn outbound with personalized demos”“send Loom videos to prospects”“show the prospect their own demo”“get demand from Reddit without getting banned”
Founder-led GTMFree
Niche down to expandPick the segment your sales call record supports over founder conviction, reposition website, pricing and messaging together, and route churn reasons into the roadmap.
Say “we are selling to everyone”“beta users will not convert”“we are stuck at the same MRR”“which ICP should we pick”
2.5x revenue the next monthAfter repositioning to lead gen agencies, Nick Velkovski said HeyReach grew revenue 2.5x the next month.
The rep surfaceFree
GTM engineer rollout on ClayStand up a GTM engineer on Clay: rank the playbooks, start from existing assets, enrich inbound into MQLs, design one proprietary signal, and prioritize each rep's morning.
Say “we need a GTM engineer”“where do we start with Clay”“our inbound leads never become MQLs”“our reps start every day with no list”
Data and contextFree
Revenue context layer for ClaudeBuild a three-pillar revenue context layer that feeds Claude through MCP, resolves each person to one identity, and splits meetings and Slack per deal.
Say “our agents give generic output”“we just pass the transcript to the LLM”“connect our deal context to Claude”“build a context graph for sales”
95% fewer actions per follow-upGorish Aggarwal said a context layer cuts the human actions needed to produce one follow-up email by 95%, without giving a method or sample.
Founder-led GTMFree
Self-learning founder support loopFounders answer every request by hand, document the resolutions, then an agent in Slack answers from that record and escalates gaps, learning from each founder reply.
Say “founders are drowning in support”“scale support without hiring”“build a support agent that learns”“automate a process without losing the human touch”
Content ops · PublishFree
Episode write-up formatThe canonical structure for every episode post, YouTube description, chapters, SEO fields and email header.
How GTM Vault is run · Needs: A transcript or recording notes. Substack and YouTube.
Content ops · PublishFree
LinkedIn episode announcementThe default launch post for every new episode, written to carry the trailer.
How GTM Vault is run · Needs: The episode write-up and the trailer.
Content ops · PublishFree
Clip caption packOne clip transcript in, captions for Instagram, LinkedIn, YouTube Shorts, X and Substack Notes out.
Say “caption pack”“run captions”“captions for this clip”“drip this transcript”
How GTM Vault is run · Needs: A clip transcript.
Content ops · ProduceFree
Trailer brief for the editorA per-episode creative brief so the editor hits the trailer on draft one, plus the review of the cut.
Say “a brief for the editor”“video brief”“trailer brief”
How GTM Vault is run · Needs: The episode audio, video or transcript.
Content ops · ProduceFree
Episode thumbnail railThe YouTube thumbnail and Substack card for every episode, built from Canva masters.
Say “run the thumbnail rail”“thumbnails for GTM 54”“episode thumbnails”“make the thumbnails for SMYS 10”
How GTM Vault is run · Needs: Canva and one master design per show and surface.
Content ops · ProduceFree
Post cover imagesOne cover system for every post that is not an episode, with a type tag and a picture per content type.
Say “generate a thumbnail”“create a cover image”“make an OG image”“covers for every post”
How GTM Vault is run · Needs: Node with Playwright. The generator and an example cards file are included.
Content ops · GrowFree
Signals digest railEvery two weeks: new GTM and AI studies, raises, open roles and events, as a digest and an essay footer.
Say “run the signals rail”“run signals”“bi-weekly digest”“build the signals block”
How GTM Vault is run · Needs: Web search.
Content ops · GrowFree
AI citation railKeeps the Stack Index citable by AI answer engines, and measures it with a fixed prompt panel.
Say “run the GEO rail”“run geo”“citation rail”“get us cited”
How GTM Vault is run · Needs: A public index or library you want cited.
How these are built
- One system, one operator, one episode. Each operator skill starts from a system described on the record and cites it by timestamp. The operator did not write or review the skill; it is built from what they said, and their numbers are theirs, not a promise.
- Runnable, not a summary. Every skill ends in steps Claude follows on your company and an artifact it produces: a scoring sheet, a spec, a sequence, a measurement loop.
- Tools are evidence, not placement. Each skill lists the tools the operator runs, from the Stack Index. Any tool doing the same job works. Placement is never for sale.
Two ways to use them
- Install one. Download the zip and add it as a skill in Claude's settings. In Claude Code, unzip it into
~/.claude/skills/. - Run it from the GTM Vault MCP. All 26 sit in the Skills group next to the thirty-four playbooks, free for every GTM Vault subscriber. Connect GTM Vault to Claude, then ask:Run the GTM Vault PQL scoring agent skill on our signups.