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]>
4.1 KiB
4.1 KiB
description, argument-hint, source
| description | argument-hint | source |
|---|---|---|
| Create a comprehensive product strategy using the 9-section Strategy Canvas — from vision to defensibility | <product or company> | phuryn/pm-skills |
/strategy -- Product Strategy Canvas
Build a complete product strategy document using the 9-section Product Strategy Canvas. Covers vision, segments, value propositions, trade-offs, metrics, growth, capabilities, and defensibility.
Invocation
/strategy AI-powered design tool for non-designers
/strategy [upload existing strategy doc, pitch deck, or business plan]
/strategy # asks about your product
Workflow
Step 1: Understand the Product
Accept context from:
- Product description (verbal or written)
- Uploaded documents (strategy decks, pitch decks, PRDs, business plans)
- Existing strategy to refine or challenge
Ask key questions:
- What does the product do? Who is it for?
- What stage is it in? (idea, MVP, growth, mature)
- What's the business model?
- What triggered the need for a strategy document? (new product, pivot, annual planning, fundraise)
Step 2: Build the Strategy Canvas
Apply the product-strategy and product-vision skills:
Work through all 9 sections of the Strategy Canvas:
- Vision: Inspiring north star that motivates the team
- Target Segments: Who you serve (and who you don't)
- Pain Points & Value: Problems you solve and the value you create
- Value Propositions: JTBD-framed value for each segment
- Strategic Trade-offs: What you choose NOT to do (as important as what you do)
- Key Metrics: How you measure success
- Growth Engine: How you acquire and expand users
- Core Capabilities: What you need to build and maintain
- Defensibility: What makes this hard to copy (network effects, data, brand, switching costs)
For each section, provide specific content — not generic advice.
Step 3: Generate Strategy Document
## Product Strategy: [Product Name]
**Date**: [today]
**Stage**: [idea / MVP / growth / mature]
**Author**: [user]
### 1. Vision
[Inspiring, achievable, emotional — 2-3 sentences max]
### 2. Target Segments
| Segment | Size | Pain Level | Current Alternative | Priority |
|---------|------|-----------|-------------------|----------|
**Primary segment**: [who and why]
**Explicitly not serving**: [who and why]
### 3. Pain Points & Value Created
[For each segment: the problem, current cost, and value your solution delivers]
### 4. Value Propositions
**For [Segment A]**: When [situation], they want [motivation], so they can [outcome]
**For [Segment B]**: When [situation], they want [motivation], so they can [outcome]
### 5. Strategic Trade-offs
| We Choose | Over | Because |
|-----------|------|---------|
### 6. Key Metrics
- **North Star**: [metric]
- **Input Metrics**: [3-5 levers]
- **Health Metrics**: [guardrails]
### 7. Growth Engine
[How you acquire, activate, and expand — specific mechanisms, not generic]
### 8. Core Capabilities
| Capability | Build / Buy / Partner | Investment Level | Timeline |
|-----------|---------------------|-----------------|----------|
### 9. Defensibility
[What creates a moat — be specific about which type: network effects, data, brand, switching costs, economies of scale]
### Strategic Risks
[Top 3 things that could invalidate this strategy]
### Next Steps
[What to do with this strategy — socialize, test, build]
Save as markdown.
Step 4: Offer Next Steps
- "Want me to build a Lean Canvas or Business Model Canvas for this?"
- "Should I create a roadmap aligned to this strategy?"
- "Want me to run a macro environment scan to stress-test assumptions?"
- "Should I define OKRs based on Section 6?"
Notes
- A good strategy is more about what you say NO to than what you say YES to — push hard on trade-offs
- Vision should be emotional and memorable, not a corporate statement
- Defensibility is the hardest section — most products don't have a real moat yet, and that's OK to acknowledge
- If the product is early-stage, some sections will be hypotheses — label them as such
- Strategy should fit on one page for executives — offer a condensed version