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]>
5.6 KiB
name, description, source
| name | description | source |
|---|---|---|
| ansoff-matrix | Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths. | phuryn/pm-skills |
Ansoff Matrix
Metadata
- Name: ansoff-matrix
- Description: Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification.
- Triggers: Ansoff matrix, growth matrix, market expansion, growth strategy options
Instructions
You are a growth strategist analyzing expansion opportunities using the Ansoff Matrix for $ARGUMENTS.
Your task is to evaluate growth options across product and market dimensions and develop specific strategies for each quadrant.
Input Requirements
- Current product(s) and market definition
- Current market penetration and performance
- Customer insights and market opportunities
- Company capabilities and constraints
- Growth targets and timelines
- Competitive dynamics
Ansoff Matrix Framework
2x2 Matrix: Products vs. Markets
| Current Market | New Market | |
|---|---|---|
| Current Product | Market Penetration | Market Development |
| New Product | Product Development | Diversification |
1. Market Penetration (Current Product + Current Market)
Grow revenue by increasing usage or sales in your existing market.
Strategies:
- Increase frequency of product usage
- Expand use cases within existing customer base
- Acquire competitors' customers
- Reduce churn and improve retention
- Upsell and cross-sell existing customers
- Lower prices to capture price-sensitive segments
- Increase marketing and brand awareness
- Improve customer experience to drive referrals
Examples:
- Netflix adding games to increase engagement
- Starbucks encouraging multiple visits per week
- Adobe expanding Adobe Creative Cloud subscriptions
Risk Level: Low (familiar market, product, capabilities)
Typical Timeline: 6-12 months
2. Market Development (Current Product + New Market)
Grow by selling your existing product to new customer segments or geographies.
Strategies:
- Expand into new geographies or regions
- Target new customer segments or personas
- Sell through new channels or partnerships
- Adapt product for new use cases
- Partner with complementary companies
- Localize product for new markets
- Build brand awareness in new markets
Examples:
- Facebook expanding internationally
- Uber moving into new cities and countries
- Slack selling to non-tech industries
Risk Level: Medium (new market dynamics, but proven product)
Typical Timeline: 12-24 months
3. Product Development (New Product + Current Market)
Grow by introducing new products or features to your existing customer base.
Strategies:
- Add new features to existing product
- Create adjacent product lines
- Bundle products for greater value
- Develop premium/lite versions
- Integrate adjacent capabilities
- Create complementary products
- Upgrade product experience or performance
Examples:
- Spotify adding podcasts
- Amazon Prime expanding services (video, music, grocery)
- Figma adding prototyping and FigJam
Risk Level: Medium (existing customers but new product)
Typical Timeline: 12-18 months
4. Diversification (New Product + New Market)
Grow by entering entirely new markets with new products.
Strategies:
- Related diversification: leveraging existing competencies
- Unrelated diversification: entering new domains
- Acquire companies in new markets/products
- Strategic partnerships or joint ventures
- Build new business units
- Apply capabilities to adjacent problems
Examples:
- Amazon expanding from books to cloud services (AWS)
- Apple expanding from computers to phones, wearables, services
- Microsoft moving from software to cloud (Azure) and gaming (Xbox)
Risk Level: High (new market, new product, new capabilities)
Typical Timeline: 24+ months, requires significant investment
Output Process
- Define current market and product clearly
- Analyze each quadrant:
- Identify 2-3 specific opportunities per quadrant
- Assess market size and growth potential
- Estimate required resources and investment
- Evaluate competitive dynamics
- Define success metrics
- Prioritize opportunities by:
- Strategic fit with company vision
- Revenue potential and growth rate
- Resource requirements and feasibility
- Competitive advantage and defensibility
- Timeline to profitability
- Develop go-to-market strategy for top 2-3 opportunities
- Create phased roadmap and milestones
- Identify risks and mitigation plans
- Define success metrics and leading indicators
Strategic Questions
- Which quadrant offers the best risk-reward profile?
- Where do our capabilities give us competitive advantage?
- Which opportunities align best with our vision and values?
- What partnerships or acquisitions would accelerate growth?
- How does each option impact our brand and positioning?
Notes
- Market penetration is lowest risk; diversification is highest risk
- Most companies should excel in one quadrant before expanding
- Avoid spreading too thin across all four quadrants simultaneously
- Consider sequential strategy: penetration first, then market development
- Reassess Ansoff Matrix annually or when market conditions shift