AI SummaryThis skill provides a philosophical framework and analytical methods for evaluating whether end users can "know" what value they can achieve through a product. It guides analysis from a value discovery perspective, rather than providing checklists. End users adopt products when they know what value
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "value-realization" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/value-realization && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/value-realization/SKILL.md "https://raw.githubusercontent.com/Done-0/value-realization/main/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Analyze whether end users will discover clear value in product ideas. Use when: discussing product concepts, evaluating features, planning marketing strategies, analyzing user adoption problems, or when the user expresses uncertainty about product direction (e.g., 'evaluate this product idea', 'will users adopt this', 'why aren't users retaining', 'analyze the value proposition', 'product-market fit', 'user adoption analysis').
Overview
This skill provides a philosophical framework and analytical methods for evaluating whether end users can "know" what value they can achieve through a product. It guides analysis from a value discovery perspective, rather than providing checklists. What this skill provides: • Framework to evaluate product ideas when certainty is lacking • Analysis methods for assessing end user value discovery • Patterns from real product successes and failures • Analysis methods for product design and positioning Core question: Can end users clearly understand what value they'll achieve through the product - even if that value takes time to achieve? Key terminology: • User: The person using this skill (product creator, PM, designer, entrepreneur, etc.) • End user: The person who will use the product being discussed • Value: The outcomes end users achieve through the product (such as identity, financial gain, capability enhancement, time savings, etc.) • Features: The product's technical capabilities Core distinction: • Features are not value • Features are what the product can do, value is the outcomes end users gain • Analysis must translate features into specific end user outcomes
Value Realization Philosophy
Status: Production Ready ✅ Version: 1.1.7 Last Updated: 2026-02-24 Type: Analytical Framework
Core Insight
End users adopt products when they know what value they'll get. This "knowing" is critical: • If end users know they'll achieve something valuable (even long-term), they'll use it • If end users don't know what they'll achieve, they won't use it - no matter how good the product is What "knowing" means: • End users can explain to themselves or others why they're using the product • End users can describe what they'll achieve (not just what features exist) • End users understand the outcome, even if it takes time to achieve Observed patterns: • When end users can articulate clear value → higher adoption rates • When end users cannot articulate value → adoption challenges, even with innovative features • Some end users adopt without full clarity, then discover value through use (progressive discovery) Value types end users seek (but aren't limited to): • Identity and belonging • Financial gain • Short-term benefits • Long-term benefits • Status and recognition • Capability enhancement • Time savings • Problem resolution
The Challenge
Most product creators face a hidden problem: end users often don't know what they actually want, and how they articulate it may be wrong. The job isn't just to build what end users ask for - it's to help end users discover what value they're actually seeking.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster