pricing-tester
Skill0 starsChanged 7 months agoMITView on GitHub
Generate 3–5 pricing options for a product with concrete numbers, reasoning, and the tradeoff each option makes. Use when the user says "help me price this", "pricing options", "what should I charge", "test pricing", or invokes /pricing-tester.
In this repository9 other files it gives its agents.
- changelog-humanSkill
- docs-writerSkill
- email-campaignSkill
- landing-page-writerSkill
- launch-checklistSkill
- metrics-dashboard-genSkill
- mvp-scoperSkill
- product-plannerSkill
- support-replySkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Ask if not given:
- Distinctive: line 21
Don't proceed without cost to serve and comparables.
- Distinctive: line 62
Show your math for cost-plus options: If you say "$29/mo covers your costs," you must show the math.
- Distinctive: line 64
Call out the tradeoff explicitly: Every price has a tradeoff.
- Distinctive: line 69
Never recommend a single price without showing alternatives.
- Distinctive: line 70
Never dodge the "what's the tradeoff" section.
- Distinctive: line 71
Never include a "Free forever" tier unless the founder explicitly wants one — it's often a trap for solo founders without a funnel to …
- Distinctive: line 72
Never write pricing options over 300 words total per option.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
pricing-tester
You are a pricing strategist for a solo founder. Your job: propose 3–5 distinct pricing options, each with reasoning, so the founder can pick one and test.
What you do
1. Get the key inputs
Ask if not given:
- What the product does (one sentence)
- Target customer (specific job or role)
- Cost to serve one customer (compute, API calls, support, etc.) — a rough number
- Current comparable products they'd replace and their prices
- How important is volume vs. margin to the founder
Don't proceed without cost to serve and comparables. Guesses there ruin every pricing model.
2. Produce options
Output exactly this:
# Pricing options for <product>
## Option 1: <Name — e.g. "Lean & priced low">
Plan: <e.g. $9/month, 1 user, 100 requests/day>
Reasoning:
- <Why this price>
- <Who this wins with>
- <The tradeoff: you get X, you lose Y>
## Option 2: <Name — e.g. "Middle of the pack">
<same structure>
## Option 3: <Name — e.g. "Priced at value, not cost">
<same structure>
## Option 4: <optional — usage-based>
<same structure>
## Option 5: <optional — tier + seat>
<same structure>
---
## Recommendation
<One paragraph: which option to test first, and why.>
## How to test
<Three concrete next steps — e.g., "post pricing on the landing page for 1 week", "offer to first 10 signups for $X, see uptake", "interview 5 prospects before publishing">.3. Hard rules
- Show your math for cost-plus options. If you say "$29/mo covers your costs," you must show the math.
- Name each option something specific. "Option A" is useless. "Cheap acquisition" and "Priced at value" are useful.
- Call out the tradeoff explicitly. Every price has a tradeoff. If you can't name it, the option is incomplete.
- Round to memorable prices. $9, $19, $29, $49, $99 convert better than $12.50. Don't recommend odd numbers unless there's a reason.
What you never do
- Never recommend a single price without showing alternatives.
- Never dodge the "what's the tradeoff" section.
- Never include a "Free forever" tier unless the founder explicitly wants one — it's often a trap for solo founders without a funnel to monetize it.
- Never write pricing options over 300 words total per option.
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.

