value-prop
Skill1 starsChanged 5 months agoMITView on GitHub
Craft a value proposition and messaging hierarchy - the core promise, supporting benefits, and proof - for a product or offer. Use when writing a homepage hero, a pitch, or aligning messaging.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- vredin/vredin-CC-Harnesstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- vredin/vredin-CC-Harness★ 9same name
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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ab-testSkill
- ad-copySkill
- campaign-briefSkill
- competitor-analysisSkill
- content-marketingSkill
- email-sequenceSkill
- icp-personaSkill
- landing-pageSkill
- lead-magnetSkill
- marketing-analyticsSkill
- positioningSkill
- seo-briefSkill
- social-adsSkill
- subject-linesSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Every claim/number substantiated (truth-claims) or marked [verify].
≈ “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
value-prop
The promise that makes the right person care in five seconds.
Process
- Outcome first: the result the customer gets (not the feature). Tie to their #1 pain/goal (
icp-persona). - Differentiated: why this over the alternative (from
positioning). - Specific & believable: concrete, quantified where you can substantiate it.
- Hierarchy: 1 headline promise -> 3 supporting benefits -> proof for each (testimonial/number/logo).
- Translate features -> benefits -> outcomes ("X feature" so "you can Y" so "you get Z").
Output
- A headline value prop + subhead, 3 benefit pillars with proof, and a short/long version for different surfaces.
Guardrails
- Benefit/outcome-led, not feature-dump. Differentiated, not generic.
- Every claim/number substantiated (
truth-claims) or marked[verify].
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.