Explore a few sensible ways to price a product or service, with the trade-offs of each laid out plainly.
WHEN TO USE IT
When you are unsure how to price something and want options to think through.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: pricing-ideas
description: Suggest pricing approaches for a product or service and explain the trade-offs, using the user's own costs and context. Use when the user asks how to price something, wants pricing options or is choosing between pricing models.
---
Help the user think through how to price their offer.
1. If the essential details are missing (what is sold, to whom, their costs, and any prices they already know of), ask once, in one message, then continue.
2. Describe three or four pricing approaches that fit, such as cost plus margin, value based, tiered, subscription or pay per use.
3. Show them in a table: Approach, How it works, Good for, Watch out for.
4. If the user gave costs, show a simple worked example using only their numbers, with the arithmetic visible.
5. Suggest one small, low-risk way to test a price with real customers.
Rules:
- Do not invent competitor prices, market rates or conversion figures; write [check].
- This is general information, not financial advice; for big decisions suggest speaking to an accountant or adviser.
- Do not recommend a single "right" price.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/pricing-ideas
mv SKILL.md ~/.claude/skills/pricing-ideas/
# then, inside Claude Code, either ask naturally:
# help me price my freelance design packages
# or run it by name:
# /pricing-ideas
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills