Value Curve logo

Value Curve

Community
phuryn
value-curve

Comparing a product with competitors or choosing what to be best at: a value curve on one segment's top needs, plus price.

Overview

Publisherphuryn
Repositoryproduct-engineering
Skill namevalue-curve
Stars
189
Forks
27
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by phuryn on GitHub. Read the source before you install it.

Installation

Install the Value Curve AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/phuryn/product-engineering/tree/main/product/skills/value-curve
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/phuryn/product-engineering.git /tmp/product-engineering
mkdir -p .claude/skills
cp -r /tmp/product-engineering/product/skills/value-curve .claude/skills/value-curve
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Value Curve in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Value Curve on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Value Curve is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Value Curve

A value curve compares offerings on the factors one customer segment values. It comes from Blue Ocean Strategy (W. Chan Kim and Renée Mauborgne). Used here, it answers one question: does our offering meet this segment's specific needs far better than anything else they can use? A good strategy competes to be unique, not the best at everything.

It is a starting point, not the whole answer. It feeds the Alternatives part of the value proposition (the value-proposition skill), and the value proposition needs all six parts.

Before you start

  • One segment per curve. Needs differ between segments, so a curve that mixes them shows no focus. If the segment isn't chosen yet, find clusters of customers with similar underserved needs first (market-segments, then beachhead-segment).
  • The factors are the segment's needs, not your features. Phrase each as an outcome the customer wants ("find live sports events", "content for kids"), solution-agnostic, the way jobs to be done are phrased.
  • Evidence comes from customers. For every need, interviews ask how important it is and how satisfied they are with what they use today. They also ask which competitors' products they use, and what they would pay relative to those (a Van Westendorp price survey is one way). About 10-15 interviews per segment.
  • With no interviews yet (only websites, reviews, the owner's own knowledge), the curve can still be drawn, but label every score an assumption and name its source. Its first output is then what to test with customers.

Steps

  1. Score every need for the segment. For each one, opportunity to add value = importance × (1 − satisfaction), with both on a 0-1 scale. This is Dan Olsen's formula from The Lean Product Playbook: simple, and it agrees with the jobs-to-be-done opportunity score where it matters most (high importance, low satisfaction).
  2. Pick 5-7 factors.
    • The needs with the highest opportunity scores.
    • Must-haves: needs this segment rates highly important even though today's products already satisfy them. Their low opportunity score doesn't make them optional; dropping one loses the customer.
    • Leave out needs this segment doesn't rate as important, even if competitors compete hard on them.
    • Add relative price as a factor, scored so a lower price scores higher. Then every factor reads the same way: higher is better for the customer.
  3. List the offerings. Your product (as planned, or as it is), the 2-4 competitors the segment actually uses, and at least one substitute: the spreadsheet, the agency, the manual workaround, doing nothing.
  4. Score each offering 0-100 on each factor from what customers said and what reviews show, not from feature lists. A feature that exists but doesn't serve the need scores low.
  5. Draw it. Factors on the horizontal axis, ordered by importance to the segment; score on the vertical axis; one line per offering, with a legend. Keep the table of scores beside the chart, with the source of each score.
  6. Read it, and write the reading down in a few sentences:
    • Where we must be far ahead: the segment's top-opportunity needs. If our line isn't clearly above everyone else's there, there is no reason to switch.
    • Where parity is enough: the must-haves.
    • What we deliberately don't compete on: factors where we sit at or below competitors because this segment doesn't care. Saying it out loud is the strategy.
    • Lines that look the same: if our curve has the same shape as a competitor's, we're competing on degree, not difference. Blue Ocean's four actions help reshape it: which factors to eliminate, reduce, raise, or create.

Output

  • The segment the curve is for, in one line.
  • The table: factors × offerings, each score with its source (an interview count, a review, or "assumption").
  • The chart.
  • The reading (step 6), and the Alternatives line it gives the value proposition: our unique value against each competitor and substitute, and the relative price.
  • The weakest assumptions behind it, as what to test next.

Example

A streaming service for one segment: people who care about live sports events and concerts, and whose needs today's services underserve. The scores are illustrative.

FactorOur productCompetitor ACompetitor B
Sports events954030
Concerts903545
Content for kids (must-have)707570
Movies309085
Relatively low price605065
  • We aim to be the best at what this segment needs most: sports events and concerts.
  • Content for kids stays at parity. Customers are already satisfied with it, but it matters to them.
  • Movies are left low on purpose: this segment doesn't rate them as important.

Mistakes

  • Scoring features instead of needs, which turns the curve into a feature comparison.
  • Too many factors. Past seven, the shape stops saying anything.
  • Factors the segment doesn't care about, kept because competitors fight over them.
  • Trying to beat every competitor on every factor. That is the opposite of a strategy, and usually unaffordable.
  • One curve for several segments.
  • Treating assumed scores as findings. Unlabelled guesses look exactly like evidence on a chart.

How you can tell it worked

The curve is for one segment, every score has a source or is labelled an assumption, and the reading says where the product must be far ahead and what it deliberately doesn't compete on.

Frequently asked questions

What does the Value Curve AI skill do?

Comparing a product with competitors or choosing what to be best at: a value curve on one segment's top needs, plus price.

Why use Value Curve on TypingMind?

Because you install it once and use it with any model. Value Curve is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Value Curve in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/phuryn/product-engineering/tree/main/product/skills/value-curve. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Value Curve?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Value Curve?

As many as you like. As long as a model supports skills, you can use Value Curve with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Value Curve AI skill free?

Yes. It is published on GitHub by phuryn under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇