gtm-operator-skills / evp
AGENTS.md3 starsChanged 24 days agoMITView on GitHub
Missing brand-config + SOUL on first invocation → run the setup mode, skills/evp/modes/setup.md. Shared operator/icp questions are asked once for the suite by /gtm:setup. The 3-tier brief goes to gtm/evp-brief.md in the operator's project (create gtm/ if missing). brand-config.json and SOUL.md stay at the root.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- cmj-hub/claude-evpword for word, first seen May 24, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cmj-hub/claude-evp★ 3100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/cold-email/AGENTS.mdAGENTS.md
- skills/founder-brand/AGENTS.mdAGENTS.md
- skills/pricing/AGENTS.mdAGENTS.md
- skills/psp/AGENTS.mdAGENTS.md
- build-packSkill
- company-context-packSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Refuse made-up proof: Every EVP variant must cite proof from the operator's reservoir, not invented case studies.
- Distinctive: line 9
Tier-fit check: Never produce a Tier-5 line when the buyer is Tier 2.
- Very specific: line 13
Publish the outreach line: When the operator picks the line for primary_outreach_tier, write the evp block: tier, primary, outcome, …
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md — Behavior rules for claude-evp
Rules
- Always load brand-config.json + SOUL.md first. Missing either → run the
setupmode (skills/evp/modes/setup.md). - Refuse vague outcomes. "Improve" / "optimize" / "drive growth" — push back with the operator's outcomes-I-will-claim list.
- Refuse made-up proof. Every EVP variant must cite proof from the operator's reservoir, not invented case studies.
- Enforce the 22-word limit. Hard constraint.
- Tier-fit check. Never produce a Tier-5 line when the buyer is Tier 2. Calibrate to brand-config.primary_outreach_tier or the explicit tier the user requested.
- Schwartz model is the canon. 5 tiers: unaware / problem-aware / solution-aware / product-aware / most-aware. Refuse to substitute marketing-funnel terms.
- Read the PSP, never invent it. Pain and vocabulary come from
brand-config.psp(published by the psp pack), falling back topsp_drafts.primary. Neither → name the psp pack and its install line (/plugin install psp@gtm-operator-skills, then/psp:psp). - Merge, never overwrite.
brand-config.jsonandSOUL.mdare shared by every pack in the suite. Read the existing file, add or update only this pack's fields (evp_drafts,competitors,primary_outreach_tier,refresh_cadence_days,evp), and leave every other key exactly as it was. Never rewrite the file from the example, never delete another pack's keys. Show the diff and ask before changing a field that already has a value.operatorandicpare shared: fill gaps only. InSOUL.md, touch only this pack's own##sections. - Publish the outreach line. When the operator picks the line for
primary_outreach_tier, write theevpblock:tier,primary,outcome,tradeoff,proof. Downstream packs (cold-email, landing-page, sales-offer, email-sequence) readevp.
What the agent NEVER does
- Generates an EVP without brand-config + SOUL (refuses) Scoring a draft the operator pasted is the exception: score it, say which checks the missing config skipped, then offer setup.
- Claims outcomes outside the operator's "will claim" list
- Cites invented case studies / metrics
- Substitutes "predictable", "scalable", "best-in-class" for specific outcomes
- Produces Tier-mismatched lines (e.g., Tier-5 close on Tier-2 audience)
- Rewrites
brand-config.jsonorSOUL.mdwholesale, or drops another pack's keys or sections - Writes the
pspblock (that belongs to the psp pack)
Onboarding flow
Missing brand-config + SOUL on first invocation → run the setup mode,
skills/evp/modes/setup.md. Shared operator/icp questions are asked
once for the suite by /gtm:setup.
Work files
The 3-tier brief goes to gtm/evp-brief.md in the operator's project
(create gtm/ if missing). brand-config.json and SOUL.md stay at
the root.
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.

