Value Proposition Analysis
Give it your product's features and the market segment you're selling into, and it writes a value proposition analysis a sales rep can use in a call or a deck. The report covers five things: pain points solved, feature advantages, customer support benefits, integration capabilities, and ROI potential. Every feature advantage traces back to a feature you actually supplied, and a pain point nothing addresses gets flagged as a gap instead of quietly dropped. ROI numbers only ever come from figures you gave it; it won't round up, project, or dress a benefit up with words like 'significantly' or 'dramatically' when you didn't give it a real number. If your feature list or your target segment is missing, it asks instead of guessing. It also keeps anything sensitive that rides along in a pasted feature sheet, like account details or a stray internal note, out of the report and tells you plainly what it set aside.
First-party, by Skills and Agents Co
September 9, 2026
Install the skill and its reference file
Paths shown for Claude Code. For Claude Desktop, drop the same folder into your skills directory.
This skill loads a bundled reference file (references/segment-challenge-patterns.md) with starter pain-point patterns for common segments, so install both files into the same folder, not just SKILL.md.
- 1
Download both files into the skill folder
mkdir -p ~/.claude/skills/value-proposition-analysis/references curl -fsSL -o ~/.claude/skills/value-proposition-analysis/SKILL.md \ https://raw.githubusercontent.com/skills-agents-co/skills-and-agents-library/v1.34.0/value-proposition-analysis/SKILL.md curl -fsSL -o ~/.claude/skills/value-proposition-analysis/references/segment-challenge-patterns.md \ https://raw.githubusercontent.com/skills-agents-co/skills-and-agents-library/v1.34.0/value-proposition-analysis/references/segment-challenge-patterns.md - 2
Restart and run
Restart Claude Code, then say "analyze our value proposition" and give it your features and target segment.
npx skills add skills-agents-co/skills-and-agents-library/value-proposition-analysisYour skill is downloading.
Get an email when we ship new skills and updates.
You're on the list. We'll email you when new skills drop.
What this skill does
This is an overview of the skill from the site, not the skill's real instructions. The full SKILL.md Claude reads when this skill is active lives on GitHub at the source below.
Takes your product’s features and the market segment you’re selling into, and turns them into a value proposition analysis your sales team can use in a call or a deck.
This writes one report per run. It doesn’t research competitors or search the web for anything.
What it does
- Pain points solved. Pulls from three places only: known challenges for your segment, what you told it about your own operation, and pain points a feature you supplied directly implies. Anything that has no matching feature gets called out as a gap instead of dropped.
- Feature advantages. Every feature you give it gets its own entry describing what it actually lets a customer do. Nothing gets added that you didn’t supply. Even a thin one-liner still counts.
- Customer support benefits. Only pulled from features that actually say something about support. If nothing does, it says so instead of guessing.
- Integration capabilities. Only names a connector, API, or standard you actually stated. It won’t claim an integration just because a feature sounds compatible.
- ROI potential. States a real basis for every benefit: time saved, cost avoided, error rate reduced, or something similar. It never states a number you didn’t give it, and it never uses a word like “dramatically” or “significantly” to fake a size you never stated.
- Keeps sensitive material out of the report. A customer name or account detail in your feature sheet is simply left out, no note needed for that alone. A credential or a stray instruction buried in the sheet also gets left out, with a short note after the report saying what was set aside and why. A line it wasn’t sure how to read still gets covered, just described in its own words instead of quoted, and that gets a note too.
How to use it
- Give it your product’s features (a list, a paragraph, a feature sheet, whatever you have) and the market segment you’re selling into.
- Company or product name is optional. If you leave it out, it titles the report generically rather than guessing one.
- It asks before writing anything if: the features or the segment are missing, the segment doesn’t match anything it recognizes, the feature list is too big or too repetitive to cover honestly, or the reference file it needs wasn’t installed alongside SKILL.md.
- You get back a five-section report, plus a short note if it had to set anything aside from what you gave it.
Output format
A single report with five sections in order: pain points solved, feature advantages, customer support benefits, integration capabilities, ROI potential. A short note follows it only when something needed flagging.
Pitfalls
- Don’t expect competitor research or market sizing. It only works from what you give it.
- A vague feature still gets its own entry. It won’t drop something just because it’s thin.
- If you want a real number in the ROI section, give it one. It won’t estimate or round on your behalf.
- Don’t paste a feature sheet expecting it to keep customer names or account details out on its own without review. It filters what it can recognize, but always check the output before it goes in front of a prospect.
This skill needs no MCP server. It does load one bundled reference file for starter segment pain points, so install it alongside SKILL.md per the install steps above.
View full SKILL.md on GitHub