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

4.0 KiB

description, argument-hint, source
description argument-hint source
Design sustainable growth mechanisms — growth loops and GTM motions for product-led and sales-led strategies <product or growth challenge> phuryn/pm-skills

/growth-strategy -- Growth Loops & GTM Motions

Identify and design the growth mechanisms that will drive sustainable traction. Evaluates five growth loop types and seven GTM motions to build a balanced acquisition and expansion strategy.

Invocation

/growth-strategy B2B collaboration tool — growth has stalled at 5K users
/growth-strategy Consumer fitness app looking for viral growth
/growth-strategy [upload product metrics or growth data]

Workflow

Step 1: Understand Growth Context

Ask:

  • What is the product? Who uses it?
  • Current growth metrics: user count, growth rate, acquisition channels
  • What's working? What's not?
  • Business model: how does revenue relate to user growth?
  • Team and budget: what resources can you put toward growth?

Step 2: Evaluate Growth Loops

Apply the growth-loops skill:

Analyze five growth loop types for your product:

  1. Viral Loop: Users invite others as part of natural product use
  2. Usage Loop: More usage creates more value, bringing users back
  3. Collaboration Loop: Product becomes more valuable when used with others
  4. User-Generated Content Loop: Users create content that attracts new users
  5. Referral Loop: Satisfied users actively recommend to others

For each applicable loop: mechanism, requirements, expected impact, implementation effort.

Step 3: Evaluate GTM Motions

Apply the gtm-motions skill:

Assess seven GTM approaches:

  1. Inbound: Content, SEO, thought leadership
  2. Outbound: Sales, cold outreach, account-based
  3. Paid Digital: SEM, social ads, display, retargeting
  4. Community: Forums, events, user groups, developer relations
  5. Partners: Integrations, resellers, co-marketing
  6. ABM (Account-Based Marketing): Targeted enterprise acquisition
  7. PLG (Product-Led Growth): Free tier, self-serve, product virality

For each: fit for your product, expected CAC, timeline to results, tools needed.

Step 4: Design Growth Strategy

## Growth Strategy: [Product]

**Date**: [today]
**Current state**: [user count, growth rate, key channels]
**Growth goal**: [target]

### Recommended Growth Loops
| Loop Type | Mechanism | Fit | Impact | Effort | Priority |
|----------|-----------|-----|--------|--------|----------|

### Primary Growth Loop: [Type]
**How it works**: [step-by-step mechanism]
**Requirements**: [what needs to be true/built]
**Key metrics**: [how to measure loop health]
**Implementation plan**: [concrete next steps]

### Secondary Growth Loop: [Type]
[same format]

### GTM Motion Mix
| Motion | Investment | Expected ROI | Timeline | Tools |
|--------|-----------|-------------|----------|-------|

### Growth Experiments
| # | Experiment | Tests What | Effort | Expected Learning |
|---|-----------|-----------|--------|------------------|

### Growth Metrics Framework
- **North Star**: [growth metric]
- **Loop health**: [metrics per loop]
- **CAC by channel**: [tracking approach]
- **Payback period**: [target]

### 90-Day Growth Plan
**Month 1**: [focus areas and experiments]
**Month 2**: [scale what works, cut what doesn't]
**Month 3**: [optimize and systematize]

Save as markdown.

Step 5: Offer Next Steps

  • "Want me to plan a specific launch campaign?"
  • "Should I create marketing content for the inbound motion?"
  • "Want me to set up metrics to track growth loop health?"
  • "Should I design a referral program based on the referral loop?"

Notes

  • Growth loops compound; growth tactics don't — prioritize loops over one-off campaigns
  • The best growth loop uses the product itself as the channel (PLG, viral, collaboration)
  • Not every loop works for every product — a B2B analytics tool won't go viral on TikTok
  • Budget should follow learning: invest small in experiments, then scale what proves out
  • CAC should be < 1/3 of LTV for sustainable growth — flag if projected CAC is too high