flpbalada/fb-skills

value-realization

Check whether users can discover, understand, believe, and experience product value.

First seen May 4, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill value-realization

Summary

  • Check whether users can discover, understand, believe, and experience product value.
  • Use when evaluating concepts, activation, onboarding, adoption, messaging, time-to-value, or unclear product direction; avoid for business-model economics, JTBD motivation research, or CTA-level optimization.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,559 B
  • docs SUMMARY.md 318 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

Value Realization

Goal

Determine whether users can discover, understand, believe, and experience product value.

Rules

  • Analyze end-user value, not only buyer value.
  • Separate value clarity from value delivery.
  • Check the time needed to feel value.
  • Look for invisible value that users cannot notice.
  • Tie recommendations to evidence or assumptions.
  • Do not fix messaging when the product value is missing.

Four Dimensions

  • Clarity: users understand what value is offered.
  • Timeline: users know when value appears and can reach it soon enough.
  • Perception: users believe the value matters and is credible.
  • Discovery: users can find the path to value.

Flow

  1. Define target user and job.
  2. State promised value.
  3. Score clarity, timeline, perception, and discovery.
  4. Identify where users drop off or misunderstand.
  5. Map value moments in the product journey.
  6. Recommend highest-impact fixes.
  7. Define metrics.

Signals

  • Users cannot explain product value.
  • First useful outcome takes too long.
  • Messaging describes features, not outcomes.
  • Users miss key actions.
  • Value appears only after setup.
  • Buyer value differs from daily user value.

Metrics

  • Activation rate.
  • Time to first value.
  • Feature adoption.
  • Retention by first value reached.
  • Qualitative value recall.
  • Conversion from onboarding step to core action.

Progressive Disclosure

This skill provides detailed examples through context files. Load them when needed:

Context File When to Load
context/decision-flow.md Scoring trade-offs, journey stage analysis, ready-to-ship criteria
context/enterprise-guide.md B2B/B2E products with separate buyer/end-user analysis
context/examples.md Real-world success/failure case studies
references/real-cases.md Optional deeper product case studies

Output

## Value Realization Analysis
- Target user:
- Promised value:
- Clarity score:
- Timeline score:
- Perception score:
- Discovery score:
- Main gaps:
- Recommended fixes:
- Metrics: