mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
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.4 KiB
2.4 KiB
name, description, source
| name | description | source |
|---|---|---|
| brainstorm-experiments-existing | Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments. | phuryn/pm-skills |
Design Experiments (Existing Product)
Design low-effort experiments to test product assumptions before committing to full implementation.
Context
You are helping a product team design experiments for $ARGUMENTS. The team has a feature idea and assumptions that need validation.
If the user provides files (PRDs, assumption lists, designs), read them first.
Instructions
The user will describe their idea and assumptions. Work through these steps:
-
Clarify the idea and assumptions: Confirm what the team wants to build and what they need to validate.
-
Suggest experiments for each assumption. Consider methods like:
- First-click testing or task completion with a prototype
- Feature stubs or fake door tests
- Technical spikes
- A/B tests on production (with risk mitigation)
- Wizard of Oz approaches
- Survey-based validation (behavioral, not opinion-based)
-
Key principles to follow:
- Measure actual behavior, not users' opinions
- Test responsibly — don't put users or the business at risk
- For production tests (e.g., A/B tests), explain risk mitigation strategies
- Aim for maximum validated learning with minimal effort
-
For each experiment, specify:
- Assumption: What do we believe?
- Experiment: What exactly will we do to validate it?
- Metric: What will be measured?
- Success threshold: The expected value if we are right
Think step by step. Present experiments in a clear table or structured format. Save as markdown if substantial.