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]>
2.3 KiB
name, description, source
| name | description | source |
|---|---|---|
| prioritize-assumptions | Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas. | phuryn/pm-skills |
Prioritize Assumptions
Triage assumptions using an Impact × Risk matrix and suggest targeted experiments.
Context
You are helping prioritize assumptions for $ARGUMENTS.
If the user provides files with assumptions or research data, read them first.
Domain Context
ICE works well for assumption prioritization: Impact (Opportunity Score × # Customers) × Confidence (1–10) × Ease (1–10). Opportunity Score = Importance × (1 − Satisfaction), normalized to 0–1 (Dan Olsen). RICE splits Impact into Reach × Impact separately: (R × I × C) / E. See the prioritization-frameworks skill for full formulas and templates.
Instructions
The user will provide a list of assumptions to prioritize. Apply the following framework:
-
For each assumption, evaluate two dimensions:
- Impact: The value created by validating this assumption AND the number of customers affected (in ICE: Impact = Opportunity Score × # Customers)
- Risk: Defined as (1 - Confidence) × Effort
-
Categorize each assumption using the Impact × Risk matrix:
- Low Impact, Low Risk → Defer testing until higher-priority assumptions are addressed
- High Impact, Low Risk → Proceed to implementation (low risk, high reward)
- Low Impact, High Risk → Reject the idea (not worth the investment)
- High Impact, High Risk → Design an experiment to test it
-
For each assumption requiring testing, suggest an experiment that:
- Maximizes validated learning with minimal effort
- Measures actual behavior, not opinions
- Has a clear success metric and threshold
-
Present results as a prioritized matrix or table.
Think step by step. Save as markdown if the output is substantial.