pricing
Skill3 starsChanged 6 months agoMITView on GitHub
B2B pricing surgery: willingness-to-pay, value metric, anchors, three tiers with a real decoy, discount leaks, tribunal, renewal and quarterly reviews. Use when the operator asks about pricing, raising prices, tiers, discounts, value metric, or a pricing audit. Not for the Pain Signal Profile (psp), the whole landing page (landing-page), or a give-first first email (sales-offer).
61 other projects use a version of this.
Adopted by
Most recently taken up by
- tusshaarpd/skillstheir own version, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillstheir own version, first seen Nov 16, 2026
- undark-ai/Meta-Ads-OStheir own version, first seen Nov 15, 2026
- joaoguirunas/team-ostheir own version, first seen Nov 15, 2026
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use grow-sustainably, processize and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
slavingiaSkillgrow-sustainably
Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.
Also in 7 projects that use this
slavingiaSkillprocessize
Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.
Also in 7 projects that use this
CesarjoquinSkillpaywalls
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
Also in 19 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 18 projects that use this
coreyhaines31Skillmarketing-council
When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.
Also in 14 projects that use this
- +6 more from Cesarjoquin
- +1 more from slavingia
Other versions61 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 61
- coreyhaines31/marketingskills★ 61ksame name
- slavingia/skills★ 11ksame name
- Nexus-JPF/note-companion★ 874same name
- AIDevGTM/gtm-cofounder★ 340same name
- QuantConnect/Documentation★ 268same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- Piebald-AI/splitrail★ 229same name
- Cesarjoquin/Marketing-Skills★ 190same name
- open-fox/agents★ 55same name
51 more not listed
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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 1 is distinctive, and 10 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
1
Distinctive
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 18
Read brand-config.json and SOUL.md at the project root if they exist.
- Very specific: line 19
If operator or icp is missing, say "Run /gtm:setup once for the whole suite" (the setup mode asks those inline when the gtm plugin is not …
- Very specific: line 20
If pricing is empty or SOUL.md has no pricing section, run the setup mode first, unless the operator passed --no-config (then warn that the …
- Very specific: line 25
If $ARGUMENTS names a mode, go straight to it.
- Distinctive: line 27
Read the mode file with the Read tool and follow it.
- Very specific: line 45
When a run finishes cleanly, say the next step: the next mode the status checklist names, or the next suite command (/landing-page:page …
- Very specific: line 92
If any are missing for a real recommendation, ask — don't fabricate.
- Very specific: line 93
If neither customer.psps[] nor psp exists, say the psp pack produces it (/psp:psp.
- Very specific: line 99
Before a price goes on a page or into an offer, write it as gtm/price.json (price, value_metric, contrast_set, tribunal) and run:
- Very specific: line 117
All five scripts take --file PATH or --stdin and exit 0 ok, 1 refused, 2 bad input.
- Very specific: line 130
If a companion pack is not installed, name it and its install line (/plugin install <name>@gtm-operator-skills).
“Common” is measured: kept by at least 6 in 10 of the 56 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
Pricing — JMC Pricing Surgery Skill
Comprehensive pricing orchestrator for B2B operators. Treats pricing as a surgical discipline — small precise cuts in the right place compound; sloppy cuts hemorrhage margin.
Preflight (runs before every mode)
- Read
brand-config.jsonandSOUL.mdat the project root if they exist. - If
operatororicpis missing, say "Run/gtm:setuponce for the whole suite" (the setup mode asks those inline when the gtm plugin is not installed). - If
pricingis empty orSOUL.mdhas no pricing section, run the setup mode first, unless the operator passed--no-config(then warn that the output is generic). - Drafts this pack writes go in
gtm/at the project root (create it if missing):gtm/price.json,gtm/tiers.json,gtm/anchor.json,gtm/waterfall.csv,gtm/wtp.csv.
Modes
If $ARGUMENTS names a mode, go straight to it. If $ARGUMENTS is empty, run status. Otherwise match the operator's words below; if intent is still ambiguous, ask one clarifying question — never two.
Read the mode file with the Read tool and follow it.
| You say / argument | Mode file |
status, no argument, "where do I start?", "what's next?" | modes/status.md |
setup, first run, no brand-config or SOUL.md | modes/setup.md |
diagnose, "Should I raise my prices?", "where am I leaving money?" | modes/diagnose.md (then tribunal if material) |
audit, "Audit my pricing program", "grade my pricing" | modes/audit.md |
tiers, "Redesign my pricing page", decoy, three tiers | modes/tiers.md |
anchor, "How do I anchor my pricing?", pricing copy | modes/anchor.md |
waterfall, "My discounts are eating margin", pocket price | modes/waterfall.md |
value-metric, "per-seat or per-something-else?" | modes/value-metric.md |
tribunal, "Big pricing decision — help me decide" | modes/tribunal.md |
review, "What should we check at the pricing review?" | modes/review.md |
renewal, "How do I price renewals / expansion?" | modes/renewal.md |
Moved in 0.6.0: the eleven pricing-* sub-skills are now these modes. Type /pricing:pricing <mode>.
When a run finishes cleanly, say the next step: the next mode the status checklist names, or the next suite command (/landing-page:page once the tiers are set; /sales-offer:cold-offer when the price goes into a give-first offer).
Core principles (the JMC stance)
- Pricing is surgery, not strategy. Diagnose first. Cut last. Operators who lead with "let's just raise prices 15%" hemorrhage margin and trust. Find the leak, then close it.
- A 1% price improvement = ~11% profit improvement on average B2B economics. Pricing is the highest-leverage lever in the business and the one most operators give the least attention. (Hermann Simon, 50+ years of empirical work.)
- Inertia is the real competitor. Buyers anchor on what they currently do — not on competitor prices. Beat the inertia frame, not the competitor frame.
- Loss aversion dominates size-of-win. For the 95% of buyers not in cycle, de-risking the purchase matters more than the ceiling of upside. Kahneman + Tversky's Prospect Theory is load-bearing in pricing copy.
- Value-metric alignment beats price-point tuning. The wrong unit (per-seat when the value is per-API-call) leaks more margin than any discount policy.
- Three-tier contrast-set with a real decoy gives the buyer a reference point that makes the target tier easier to choose. (Ariely, asymmetric dominance.)
- Discount discipline > headline price. The pocket-price waterfall surfaces where margin is leaking after the line-item price. Plug the leaks before tuning the headline.
- Quarterly review prevents drift. Pricing that doesn't get reviewed gets eroded. The operating practice IS the compounding moat.
Variables (every mode uses these)
The pricing surgery discipline operates on these variables. Capture
once from brand-config.json + diagnostic output, reuse across all
modes:
| Variable | Source | Example |
psp | customer.psps[]; if empty, the shared psp block written by the psp pack | "Series-B SaaS, demand-gen lead, pipeline gap" |
currentTiers | Operator's pricing page | "$99 / $299 / $999 monthly" |
valueMetric | What scales with customer success | "Active records / API calls / seats / outcomes" |
wtpDistribution | Discovered via Van Westendorp / Gabor-Granger / conjoint | "P10=$50, P50=$200, P90=$800/mo" |
referenceAnchor | Strongest plausible reference frame for this segment | "Inertia: 'building it in-house' at $80K/yr fully-loaded" |
discountWaterfall | Pocket-price waterfall steps | "List → ramp → volume → bundle → annual → effective" |
riskTier | Decision stakes (review-level required) | "Routine / Material / Strategic" |
If any are missing for a real recommendation, ask — don't fabricate.
If neither customer.psps[] nor psp exists, say the psp pack
produces it (/psp:psp; install with
/plugin install psp@gtm-operator-skills). Do not invent a PSP.
Score the price
Before a price goes on a page or into an offer, write it as
gtm/price.json (price, value_metric, contrast_set, tribunal) and run:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/score_price.py --file gtm/price.jsonExit 1 lists every reason it refused, each as - what is wrong → what to
change, then Next: fix the lines above and run this again. Fix each
one; never show a price without the unit it is per. Exit 0 ends with
the next suite step. Exit 2 is bad input. --json for the report.
Example drafts: examples/price-good.json, examples/price-no-metric.json.
Score the anchor block the same way before it goes above the tiers:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/score_anchor.py --file gtm/anchor.json
(anchor mode has the fields; examples: examples/anchor-good.json,
examples/anchor-competitor-only.json).
All five scripts take --file PATH or --stdin and exit 0 ok, 1
refused, 2 bad input. score_price.py and score_anchor.py print text
by default; the other three print JSON by default (--text for lines).
Works with the suite
This is step 6 of the GTM operator suite (/plugin marketplace add cmj-hub/gtm-operator-skills).
- Reads:
customer.psps(fallback: thepspblock) andicpfrombrand-config.jsonif present;gtm/offer-stack.json(offer-stack pack) for the anchor, if present. - Writes:
customerandpricing; drafts ingtm/. Merge at the field level; never overwrite another pack's keys. - Before this: psp (
/psp:psp), when no PSP exists yet. - After this: landing-page (
/landing-page:page), when the tiers are set; sales-offer (/sales-offer:cold-offer), when the price goes into a give-first offer.
If a companion pack is not installed, name it and its install line (/plugin install <name>@gtm-operator-skills); do not do its job inline.
References
Load these on demand for deeper context:
- Pricing framework — The full JMC pricing surgery framework
- Banned patterns — Pricing moves that fail predictably
- Lineage — Simon / Kahneman / Ariely / Christensen / Ramanujam
- Reference-frame stack — Strongest-to-weakest anchor types
- Pricing anchoring: anchor before price, same unit, sourced number, real former prices
- Value-metric engineering — Common B2B value-metric patterns + failure modes
- Three-tier contrast set — Asymmetric dominance in three-tier design
- SOUL.md — Operator voice template (pricing section)
Specialist agents
agents/pricing-reviewer— Pricing-page + tier scorer (0-100)agents/pricing-tribunal-judge— Adjudicates pricing hypotheses against the verdict matrix
Free hosted version
The same job runs in a browser, no install and no key: Pricing Page Lab
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.

