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

3.9 KiB

description, argument-hint, source
description argument-hint source
Define your North Star Metric and supporting input metrics — classify the business game and validate against best practices <product or business> phuryn/pm-skills

/north-star -- North Star Metric Definition

Identify the single metric that best captures the value your product delivers, plus the input metrics that drive it. Classifies your business game and validates against proven criteria.

Invocation

/north-star B2B SaaS for team collaboration
/north-star Consumer fitness app monetized through subscriptions
/north-star Help me fix our North Star — we're tracking DAU but it doesn't feel right

Workflow

Step 1: Understand the Product

Ask:

  • What is the product? What value does it deliver to users?
  • What's the business model? (subscription, transaction, advertising, marketplace)
  • Current metrics being tracked (if any)
  • Why is this needed now? (new product, existing metric feels wrong, team alignment)

Step 2: Classify the Business Game

Apply the north-star-metric skill:

Identify which game the product is playing:

  • Attention: Revenue from user time/engagement (media, social, ad-supported)
  • Transaction: Revenue from purchases (e-commerce, marketplace)
  • Productivity: Revenue from efficiency gains (SaaS, tools, B2B)

The game determines what kind of North Star makes sense.

Step 3: Define the North Star

  • Propose 2-3 North Star candidates
  • Validate each against 7 criteria:
    1. Expresses value delivered to customers
    2. Is a leading indicator of revenue
    3. Is measurable and trackable
    4. Is understandable by the whole team
    5. Is actionable (teams can influence it)
    6. Is not a vanity metric
    7. Is not gameable without delivering real value
  • Recommend the strongest candidate with rationale

Step 4: Define Input Metrics

For the selected North Star, identify 3-5 input metrics:

  • Each input metric should be a lever that directly drives the North Star
  • Each should be ownable by a specific team
  • Together, inputs should be MECE in explaining North Star movement

Step 5: Generate Metrics Framework

## North Star Framework: [Product]

**Business Game**: [Attention / Transaction / Productivity]

### North Star Metric
**Metric**: [precise name]
**Definition**: [formula or measurement method]
**Why this metric**: [explains value, leads revenue, is actionable]
**Current value**: [if known]
**Target**: [goal]

### Validation
| Criterion | Pass? | Notes |
|----------|-------|-------|
| Expresses value | [Y/N] | [explanation] |
| Leading indicator | [Y/N] | [explanation] |
| Measurable | [Y/N] | [explanation] |
| Understandable | [Y/N] | [explanation] |
| Actionable | [Y/N] | [explanation] |
| Not vanity | [Y/N] | [explanation] |
| Not gameable | [Y/N] | [explanation] |

### Input Metrics
| Input Metric | Drives North Star By | Owner | Current | Target |
|-------------|---------------------|-------|---------|--------|

### Metrics Constellation
[Visual tree showing North Star → Input Metrics → Team Actions]

### Counter-Metrics
| Metric | Protects Against |
|--------|-----------------|

### Anti-Patterns Avoided
[Why we didn't choose DAU, revenue, or other common but flawed metrics]

Save as markdown.

Step 6: Offer Next Steps

  • "Want me to build a full metrics dashboard around this?"
  • "Should I create OKRs based on these metrics?"
  • "Want me to write SQL queries to compute these metrics?"

Notes

  • The North Star should measure value delivered, not just activity — "daily active users" is only good if active use = value delivery
  • Revenue is never a good North Star — it's a lagging indicator that doesn't capture user value
  • Input metrics are what make the framework actionable — without them, the North Star is just a vanity dashboard
  • Revisit the North Star annually or when the business model changes significantly
  • Counter-metrics prevent Goodhart's Law — when a metric becomes a target, it ceases to be a good metric