Files
skills/commands/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

2.8 KiB

description, argument-hint, source
description argument-hint source
Design a value proposition using the 6-part JTBD template — Who, Why, What before, How, What after, Alternatives <product or feature> phuryn/pm-skills

/value-proposition -- Value Proposition Design

Design a clear, compelling value proposition for a product or feature using the 6-part JTBD template. An alternative to Strategyzer's Value Proposition Canvas that starts with the customer and focuses on practical outcomes.

Invocation

/value-proposition AI writing tool for non-native English speakers
/value-proposition [upload pitch deck, PRD, or competitive analysis]
/value-proposition                    # asks about your product

Workflow

Step 1: Understand the Product and Market

Accept context from:

  • Product description (verbal or written)
  • Uploaded documents (pitch decks, PRDs, competitive analyses)
  • Existing value propositions to refine

Ask key questions:

  • What does the product do? Who is it for?
  • What alternatives or workarounds exist today?
  • What customer insights or research do you have?

Step 2: Build the Value Proposition

Apply the value-proposition skill to produce the 6-part template:

## Value Proposition: [Product]

### For [Segment]:

1. **Who**: [target user profile and characteristics]
2. **Why**: [the job they're trying to do, desired outcomes]
3. **What Before**: [their current painful reality — existing tools, friction, workarounds]
4. **How**: [your solution — specific features and capabilities that deliver value]
5. **What After**: [the improved outcome — what becomes possible]
6. **Alternatives**: [what they'd use without you, and why you're better]

### Value Proposition Statement
[One sentence: For [who] who [need], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator].]

### Value Proposition Statements (Reusable)
- Marketing: [...]
- Sales: [...]
- Onboarding: [...]

If the user has multiple segments, create a separate value proposition for each.

Step 3: Save and Offer Next Steps

Save as markdown. Offer:

  • "Want me to compare this against competitors with a Value Curve?"
  • "Should I build a full strategy around this value proposition?"
  • "Want me to create a Lean Canvas or Startup Canvas using this?"
  • "Should I generate marketing messaging from these value prop statements?"

Notes

  • This template starts with the customer (Who/Why) and works toward the solution — unlike Strategyzer's canvas which places the product on the left
  • Each value proposition is segment-specific — different segments get different value props
  • Use a Value Curve (Blue Ocean Strategy) to visually compare your offering against competitors across key factors
  • Value Proposition is one element of product strategy — use /strategy for the full picture