gtm
Skill16 starsChanged 49 days agoApache-2.0View on GitHub
Run the GTM contact pipeline from a plain-English campaign brief. Interprets the brief against context/ + gtm.config.yaml, plans the run, and drives the stages (company_search → people_search → qualify → email_enrich → phone_enrich → activate) threading one list_id, with approval gates, a do-not-contact pass, list QA and an activation preflight. Also reports on or resumes an existing list. Use when the user describes a campaign ("find me … at … for …"), says "/gtm …", "run the pipeline", "build a list", "status of list N", or "resume list N".
7 other projects use a version of this.
Adopted by
Most recently taken up by
- sorawit-w/agent-skillstheir own version, first seen Nov 1, 2026
- mia-cx/skillstheir own version, first seen Nov 1, 2026
- ajstars1/founder-stacktheir own version, first seen Oct 25, 2026
- harshsinghmp/muse-skillstheir own version, first seen Oct 15, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- donatassimkus/claude-ai-skillstheir own version, first seen Jul 23, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- debpalash/OpenGTM★ 112same name
- mia-cx/skills★ 4same name
- sorawit-w/agent-skills★ 2same name
- ajstars1/founder-stack★ 1same name
- donatassimkus/claude-ai-skills★ 1same name
- harshsinghmp/muse-skills★ 1same name
- akachandan1/proofstack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activateSkill
- company-discoverySkill
- company-enricherSkill
- contact-qualifierSkill
- contact-sourcerSkill
- email-finderSkill
- gtm-setupSkill
- phone-finderSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Read gtm.config.yaml and the context/ files.
- Very specific: line 32
Run only the available stages, threading the list_id.
- Very specific: line 34
Before activation: qa, suppress posture=send, preflight_activate (must exit 0), then Gate #4.
- Very specific: line 39
If the brief is empty, ask for one (what to sell / who to target / where), or offer to infer it from context/icp.md.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
The user's input: $ARGUMENTS
Execute the orchestrator: read agents/orchestrator/agent.md and follow it exactly. Read
REVIEW.md once per session; it binds you and every sub-agent you start.
status <list_id>→python3 storage/cli.py run_report --input '{"list_id":<id>}'; present stages logged, counts, cost (estimate vs actual), open warnings and gate verdicts. Change nothing.resume <list_id>→ orchestrator §0: continue from the first stage whose latest event is not ok/warn/skipped, using the plan and expansion frozen on the list. Say where you are resuming and why.- Anything else is a brief:
- Read
gtm.config.yamland thecontext/files. Ificp.md/personas.mdare missing or still templates, offer/gtm-setupinstead of guessing an ICP. - Interpret the brief into a concrete plan, expand the role and segment, and preview titles on a few sample companies.
- Present the plan (Gate #1) and get approval unless autonomy says otherwise; freeze it onto the list.
- Run only the available stages, threading the
list_id. After each stage:log_event, then readlist_summaryback and compare it with what the stage reported. - Before activation:
qa,suppress posture=send,preflight_activate(must exit 0), then Gate #4. - Produce the export (say UNSCRUBBED if
suppression_appliedis false) and finish withrun_report.
- Read
If the brief is empty, ask for one (what to sell / who to target / where), or offer to
infer it from context/icp.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

