claude-psp
AGENTS.md3 starsChanged 6 months agoMITView on GitHub
If both config files are missing on first invocation, run the setup mode, skills/psp/modes/setup.md (~15-minute guided setup). Shared operator/icp questions are asked once for the suite by /gtm:setup. The PSP doc goes to gtm/psp.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/gtm-operator-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- cmj-hub/gtm-operator-skills★ 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 repositoryOne other file it gives its agents.
- pspSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
No fabricated signals: If a candidate signal can't be sourced publicly, don't include it.
- Very specific: line 21
Score before you hand off: Run scripts/score_psp.py on every PSP and show the operator each flag.
- Very specific: line 23
Publish the locked primary: When the operator locks a primary PSP that the scorer passes, write the psp block: signal_anchors …
- Very specific: line 36
If both config files are missing on first invocation, run the setup mode, skills/psp/modes/setup.md (~15-minute guided setup).
≈ “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-psp
Identity layering
| File | Job | Owner |
skills/psp/SKILL.md + skills/psp/modes/ | JMC FRAMEWORK (5-component PSP), one skill with modes | JMC (do not edit) |
SOUL.md | Operator's perspective on their buyer | You |
brand-config.json | ICP precision + PSP drafts + published psp block + signal sources | You (shared with every pack in the suite) |
Rules
- Always load brand-config.json + SOUL.md first. Missing either → run the
setupmode (skills/psp/modes/setup.md), unless the operator's request carries the seller facts itself: then work from those and offer setup afterward. - Refuse abstract pain. Force the 11am-Tuesday operational moment. If the operator says "they need better demand gen", push back.
- No demographics as signals. "VP of Marketing at Series B SaaS" is not a signal. Quote what they DID.
- No fabricated signals. If a candidate signal can't be sourced publicly, don't include it.
- Pain language must come from the operator's vocabulary list. Refuse to substitute category jargon.
- Time-anchor every PSP. Without a 90-day trigger (new-exec / budget-cycle / obvious-failure), the PSP isn't operational.
- Felt-pain role ≠ buying authority. Push the operator to name who FEELS the pain at 11am Tuesday.
- Stale signals get flagged. Signals >30 days old should not be in active outreach lists.
- Score before you hand off. Run
scripts/score_psp.pyon every PSP and show the operator each flag. Exit 1 (under 70, a stale signal, or a pain that uses none of the buyer's vocabulary phrases) means it isn't operational yet. - 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 (psp_drafts,psp,signal_sources,research_cadence), 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 locked primary. When the operator locks a primary PSP that the scorer passes, write the
pspblock:signal_anchors(psp_drafts.primary.signalfirst),primary_pain,timing_trigger,felt_pain_role,vocabulary. Downstream packs (evp, prospect-list, cold-email, pricing, geo, email-sequence) readpsp, not the drafts.
What the agent NEVER does
- Generates a PSP without brand-config.json + SOUL.md or seller facts in the request (refuses + routes to onboarding). Scoring a draft the operator pasted is the exception: score it, say which checks the missing config skipped, then offer setup.
- Prints method rules (recency windows, trigger lists) or tool names in a finished doc as if they were facts, or guesses a pronoun for a named person
- Invents vocabulary the operator hasn't sourced from real buyer writing
- Uses generic LinkedIn-thought-leader voice
- Substitutes the operator's category jargon back into their PSP
- Rewrites
brand-config.jsonorSOUL.mdwholesale, or drops another pack's keys or sections
Onboarding flow
If both config files are missing on first invocation, run the setup
mode, skills/psp/modes/setup.md (~15-minute guided setup). Shared
operator/icp questions are asked once for the suite by /gtm:setup.
Work files
The PSP doc goes to gtm/psp.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.

