icp-review
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill before shipping customer-facing copy you will spend money or reputation on: a blog post, ad, cold email, proposal, pricing or landing page. Produces an evidence-based buyer panel read built only from verbatim quotes in your own sales and client call transcripts: where a buyer stops reading, the strongest objection the copy raises and never answers, and the questions the reader brings with them, every claim tied to a real quote and checked by code. Also use for "ICP review this", "would this resonate", "what would a buyer think", "which of these lands", "why isn't this converting", "review this before I ship". First run walks through setup.
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- kondo-owed-reply-sweepSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 5 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run every command from this skill's folder (cd "<skill base directory>" first).
- Very specific: line 30
Read the widening. A non-empty dropped means the answer is not persona-specific.
- Very specific: line 35
Keep it fresh. When the user says "refresh the panel", or the newest quote is more than about 90 days old, run step 3 of …
- Very specific: line 47
MUST cite only quote_keys from the retrieved evidence pack.
- Very specific: line 48
MUST pass references/validate_verdict.py (exit 0) before showing the user any verdict.
- Very specific: line 49
MUST include strongest_objection on every verdict, including favourable ones.
- Distinctive: line 50
MUST pre-register Choose predictions before the real result exists.
- Very specific: line 51
NEVER load anything in excluded_docs: the user's own positioning, message house, site copy or scripts.
- Distinctive: line 52
NEVER add the draft under review to the evidence base.
- Distinctive: line 53
NEVER let the panel write copy.
- Distinctive: line 54
NEVER give a seat a name, backstory, mood or biography.
- Very specific: line 55
NEVER use the client seat on acquisition copy.
- Very specific: line 56
NEVER simulate a click path.
- Distinctive: line 57
NEVER pad the corpus with invented or paraphrased quotes.
- Very specific: line 58
NEVER publish a buyer quote or attribute one to a named person or company unless public_quote_rule in references/profile.json allows it.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
Applies to any draft, topic, set of variants or live page that a real buyer will read. Produces one validated verdict per seat, every claim citing a buyer quote that exists, with the strongest objection first and the verdict last.
A made-up persona invents opinions. This panel can only use what buyers actually said on calls, and when the evidence is thin it says "I can't judge this" instead of guessing.
The play
Run every command from this skill's folder (cd "<skill base directory>" first). The tools are Python 3, standard library only.
- Check setup. Read
references/profile.json. Ifsetup_completeisfalse, ordata/corpus.jsondoes not exist, stop and runreferences/setup.mdwith the user before anything else: eight short questions, then extract and tag verbatim buyer quotes from their call transcripts. Never judge copy from general knowledge as a stand-in. A panel with no corpus is a persona, and personas make things up. - Route. Work out the play from what the user hands over (Brief, Gate, Choose, Diagnose, Retention), pick the seats, and say in one line which ran and why. The routing table, the four seats and what each may never judge are in
references/routing-and-seats.md.objectorruns in every play except Brief. - Retrieve.
mkdir -p runs/<YYYY-MM-DD>-<slug>, thenpython3 references/panel.py evidence --seat <seat> [--persona …] [--stage …] [--pattern …] > runs/<…>/pack-<seat>.json. - Respect the band.
insufficient(n under 5): the verdict MUST benull; say the corpus does not cover it.thin(5 to 11):confidenceMUST be"weak signal". Never widen past the seat's base filter to manufacture an answer. - Read the widening. A non-empty
droppedmeans the answer is not persona-specific. Say which level it was answered at before anything else. - Draft the verdict to
references/verdict-schema.jsonand save it asruns/<…>/verdict-<seat>.json. Every assertion carriesquote_keys drawn only from the returned pack. - Validate.
python3 references/validate_verdict.py runs/<…>/verdict-<seat>.json --evidence runs/<…>/pack-<seat>.json. If it rejects, fix the verdict, never the validator. - Present the answer first: two or three sentences on what to fix, then the detail in the inverted reporting order in
references/routing-and-seats.md. - On a Choose play with a real result coming, pre-register the pick in
predictions.jsonlbefore the result exists, fill in the winner when it lands, and runpython3 references/score.py. - Keep it fresh. When the user says "refresh the panel", or the newest quote is more than about 90 days old, run step 3 of
references/setup.mdon the new transcripts only, thenpython3 references/build_corpus.py.
What good looks like
- First thing I check that most people skip:
strongest_objection, not the verdict. The verdict tends to agree with whoever wrote the draft, because the draft came from the same instincts. The objection is the field with no polite answer. - The mediocre version: asking an AI to "pretend to be my ICP". It reads well, cites nothing, and invents an opinion for every gap.
- Second mediocre version: running it on every draft. The dissent becomes noise and gets ignored on the one that mattered.
- I know a run is honest when a thin seat declines to judge,
distinct_callsis reported next to the quote count, and a stale or widened slice is named before any answer. - I know the panel is right only from
score.py. The gate proves the evidence exists; it cannot prove the reasoning. Until roughly 30 scored predictions, these are well-sourced opinions, not calibrated predictions, and say so.
Rules
- MUST cite only
quote_keys from the retrieved evidence pack. - MUST pass
references/validate_verdict.py(exit 0) before showing the user any verdict. - MUST include
strongest_objectionon every verdict, including favourable ones. - MUST pre-register Choose predictions before the real result exists.
- NEVER load anything in
excluded_docs: the user's own positioning, message house, site copy or scripts. That grades their copy against their copy. - NEVER add the draft under review to the evidence base.
- NEVER let the panel write copy. It judges; a panel that grades its own drafts converges on its own priors.
- NEVER give a seat a name, backstory, mood or biography.
- NEVER use the
clientseat on acquisition copy. - NEVER simulate a click path. Navigation is answered as
unresolved_questions. - NEVER pad the corpus with invented or paraphrased quotes.
- NEVER publish a buyer quote or attribute one to a named person or company unless
public_quote_ruleinreferences/profile.jsonallows it.
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.

