GTM engineering isn't one system, it's six layers: know the competitor before you build a play against them, build the collateral reps actually need, decide who's qualified, decide who gets them once qualified, mine the call for what really happened, and automate the workflow underneath all of it. gtm-skills' GTM Engineer pack is 6 free skills covering that stack, each with explicit boundaries so they don't overlap. Links to the skill files and to the Intempt agent that runs the same layer continuously against live pipeline data.
GTM engineering is the layer most teams don't name until it's broken: leads sitting unassigned, sales and marketing disagreeing on what "qualified" means, a discovery call transcript nobody re-reads. It's infrastructure work, not a single deliverable, and it has six distinct layers that all need to work together without overlapping.
So this pack is built with explicit boundaries between each skill, not just six separate prompts.
TL;DR
- gtm-skills' GTM Engineer pack is 6 free skills: competitor research, sales enablement, lead qualification scoring, lead assignment routing, call transcript mining, and workflow automation design.
- Install once with npx skills add sidchaudhary/gtm-skills.
- Start with the-routing-engine - lead handoff is the most common break point between marketing and sales.
- Intempt's GTM Engineer agent wires this same logic into live workflows that run without manual input.
How to install these in about 60 seconds
- Run npx skills add sidchaudhary/gtm-skills.
- Create a Claude project per skill - "Routing Engine," "Transcript Miner."
- Paste the skill's SKILL.md into the project instructions.
- Start a chat with your lead criteria, call transcript, or workflow description.
The 6 skills
1. The Routing Engine
Designs the lead-to-opportunity layer between marketing and sales: MQL scoring model, routing rules, speed-to-lead SLAs, and lifecycle stage definitions. Use it when leads aren't reaching sales fast enough, or marketing and sales disagree on what counts as qualified. Read the skill.
2. The Lead Router
Designs the actual assignment logic for an already-qualified lead - round-robin, territory, account-owner, or score-threshold - with explicit tie-break and fallback rules. The layer after the-routing-engine: once a lead is qualified, who actually gets it. Read the skill.
3. The Competitor Dossier
Researches a competitor from their public website and builds a structured profile: positioning, pricing, strengths and weaknesses, and competitive implications. For deep research on a specific competitor, not a one-off sales angle. Read the skill.
4. The Enablement Kit
Produces sales collateral - one-pagers, ROI calculators, proposal templates, and playbooks - mapped to buyer persona and deal stage. For when a rep needs a specific asset to hand a prospect, not a generic template. Read the skill.
5. The Transcript Miner
Takes a raw sales call transcript and extracts deal signals, objections, confirmed pain points, a stakeholder map, and a specific recommended next action. Use it before writing a follow-up email or updating a CRM record, so nothing from the call gets lost. Read the skill.
6. The Workflow Builder
Designs marketing and sales automation workflows with trigger-condition-action patterns, branching logic, error handling, and integration points. The general-purpose layer underneath everything else in this pack. Read the skill.
The order to build them in
Start with the-routing-engine - lead handoff between marketing and sales is the most common break point, and fixing it changes conversion rates downstream more than any single campaign. Add the-lead-router immediately after, since it's the layer that completes the handoff. The-transcript-miner comes next, once calls are actually happening and worth mining. Save the-competitor-dossier and the-enablement-kit for when a specific deal or a specific competitor needs deeper prep, and the-workflow-builder for whatever recurring automation the other five surface a need for.
What to never hand over
The actual SLA commitment to sales - the-routing-engine designs the speed-to-lead target, but promising reps a number you can't operationally hit is a leadership decision, not a generated one. And competitive claims about a rival's weaknesses should never go external without a human checking them against the-competitor-dossier's actual sourcing - research this specific can age fast.
When you outgrow the manual version
Intempt's GTM Engineer agent wires this same layer into live workflows: stage transitions, lead routing, task creation, and Slack alerts that run without manual input, while it monitors deal age and flags risk before deals fall through the cracks - with a daily summary so nothing needs a person watching it constantly. Same six jobs, running as infrastructure instead of a one-time design doc.
Frequently asked questions. Answered.
Six free Claude Skills covering RevOps infrastructure: competitor research, sales enablement collateral, lead-to-opportunity routing logic, lead assignment logic, call transcript mining, and marketing/sales workflow automation design. Install with npx skills add sidchaudhary/gtm-skills.
