Files
skills/public/value-proposition.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
Four MIT collections ported — growthOS, openclaw-marketing-skills,
Marketing-Skills and pm-skills — as 160 skills, 12 agents and 45
commands, each naming its origin in its own frontmatter so the tree can
be checked against THIRD_PARTY_NOTICES rather than trusted. Sixteen names
appeared in more than one collection and none of the copies were
identical; the longest wins, which lands on the more developed text where
they genuinely diverge.

A fifth collection is deliberately absent. awesome-growth-hacking-skills
carries NO licence, which leaves its author every right by default — and
it is a list of links rather than a collection of skills, so there is
nothing in it to port and no permission to port it with. It is cited as a
directory to read.

THE CONNECTOR SKILLS ARE REWRITTEN, not ported. They arrived installing
vendor SDKs, running OAuth flows of their own, and ending with long-lived
credentials in JSON files under .agents/ and ~/.growthos/ at mode 600.
That is a secret on a disk with no rotation path, protected from other
users and not from the agent — and one auth implementation per skill.
Hanzo holds these connectors in Go, per user, sealed in KMS, so `connect`
is the one home for the flow and the platform skills defer to it by
provider id: google_ads, meta_ads, x. It is reachable as HTTP or as MCP
tools at api.hanzo.ai/v1/mcp — the same routes, typed once in Go, so a
tool and a curl cannot disagree.

Two had nothing real behind them and now say so. There is no
search_console provider, so that skill names what does answer the same
questions (google_analytics, google_bigquery) and states that the remedy
is a provider in hanzoai/cloud rather than a vendor SDK here. And
getxapi-connect was a wrapper around a paid reseller of X's public data
with the vendor's key in an env var; it is `listen` now, on our own x
connector — a skill named after a vendor makes the vendor the capability
and dies with it.

The skills referenced paths that only existed inside the source repo, so
the shared material they read is ported to reference/ and the paths
rewritten. Three skills need the growthOS APPLICATION rather than its
data; per the estate's own split an application belongs in hanzoai/ads,
social, email or sms as a cloud plugin, so those three say what they need
instead of carrying an import that resolves to nothing.

Third-party product names are out of our prose and kept in the notices,
which is where the licence requires them and the only place they belong.
A skill's persona names a role, not somebody else's product.


Co-authored-by: Hanzo Dev <[email protected]>
2026-09-15 01:27:26 -07:00

5.7 KiB

name, description, source
name description source
value-proposition Design a detailed value proposition using a 6-part JTBD template — Who, Why, What before, How, What after, Alternatives. Use when creating a value proposition, analyzing customer value delivery, or articulating why customers should choose your product. phuryn/pm-skills

Value Proposition

Metadata

  • Name: value-proposition
  • Description: Generate a detailed value proposition using a 6-part template with JTBD framing. Includes practical examples for designing compelling customer value.
  • Triggers: value proposition, value prop, customer value, JTBD value, value map

Instructions

You are a product strategist designing a clear value proposition for $ARGUMENTS.

Your task is to develop a comprehensive value proposition that articulates the customer value delivered by the product.

Input Requirements

  • Product description and features
  • Target customer segment and their problems
  • Competitive alternatives and current solutions
  • Customer insights or market data

Value Proposition Template

6-Part Structure

1. Who

  • Who is this value proposition for?
  • What customer segment are we addressing?
  • What are their characteristics and constraints?

2. Why (Problem)

  • What is the customer's core problem or need?
  • What's the Job to Be Done (JTBD)?
  • What desired outcomes are they trying to achieve?

3. What Before

  • What is the customer's current situation?
  • What are they using today to solve this problem?
  • What friction or pain exists in the current approach?

4. How (Solution)

  • How does the product solve the problem?
  • What specific features or capabilities deliver value?
  • Why is this solution better than alternatives?

5. What After

  • What is the improved outcome or future state?
  • How does the customer's life/work change?
  • What becomes possible that wasn't before?

6. Alternatives

  • What other solutions could customers use?
  • Why would they choose us instead?
  • What's the switching cost or friction from alternatives?

Example: Canva

  • Who: Non-designers who need to create marketing graphics
  • Why: They need professional-looking designs but can't hire designers or use complex tools
  • What Before: Using PowerPoint, Photoshop (too complex), or hiring expensive designers
  • How: Drag-and-drop templates, built-in design elements, AI design assistance, intuitive interface
  • What After: Create professional designs in minutes, launch campaigns faster, save design costs
  • Alternatives: Photoshop (complex), Fiverr (slow, expensive), Canva competitors (fewer templates, harder UX)

Output Process

  1. Identify and profile the target customer segment
  2. Define the core problem and JTBD
  3. Describe the current state and friction points
  4. Articulate how the product solves the problem
  5. Envision the improved outcome
  6. Compare against competitive alternatives
  7. Create a concise value prop statement (1-2 sentences)
  8. Develop a positioning statement for marketing use

Domain Context

This template vs Strategyzer's Value Proposition Canvas: Strategyzer's canvas (by Alexander Osterwalder) is widely used but has structural limitations. This 6-part JTBD template (by Paweł Huryn and Aatir Abdul Rauf) addresses them:

  • Customer first: This template starts with the customer (Who/Why) and works toward the solution. Strategyzer's canvas places the product on the left, which often leads teams to start with their solution rather than the customer's problem.
  • One segment at a time: This template is designed for one segment per pass. Strategyzer's canvas encourages mapping multiple products/services simultaneously, which dilutes focus.
  • Explicit alternatives: Section 6 (Alternatives) forces you to name what customers would use without you and articulate why you're better. Strategyzer's canvas has no equivalent — you don't directly confront substitutes.
  • Simpler structure: "What before → How → What after" is easier to fill out than separating Customer Jobs, Pains, and Gains on one side and Pain Relievers, Gain Creators, and Products on the other. The separation often creates confusion about where things go.
  • Actionable output: The final Value Proposition Statement is ready for marketing, sales, and onboarding. Strategyzer's canvas doesn't produce a reusable statement.

Use Strategyzer's Value Proposition Canvas when you need a detailed pains/gains decomposition for a mature product with complex customer needs. Use this 6-part template for clarity, speed, and actionable output.

Notes

  • Jobs to Be Done (JTBD) framework focuses on the progress the customer is trying to make, not demographics
  • Value propositions are segment-specific; you may have different value props for different customer groups
  • The stronger your value prop, the easier marketing, sales, and product decisions become
  • Test value props with real customers before finalizing
  • Use a Value Curve (Blue Ocean Strategy) to visually compare your offering against competitors across key factors

Templates


Further Reading