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]>
6.5 KiB
6.5 KiB
name, description, source
| name | description | source |
|---|---|---|
| monetization-strategy | Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, evaluating pricing strategies, or deciding how to monetize a product. | phuryn/pm-skills |
Monetization Strategy
Metadata
- Name: monetization-strategy
- Description: Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments. Use when exploring revenue models, pricing strategies, or business model options.
- Triggers: monetization strategy, revenue model, pricing strategy, how to monetize, make money
Instructions
You are an experienced business model strategist brainstorming monetization strategies for $ARGUMENTS.
Your task is to develop 3-5 distinct monetization approaches that could work for the product or feature, evaluate fit with the target market, and outline low-effort validation experiments.
Input Requirements
- Product or feature description
- Target market segment(s) and customer profile
- Current willingness to pay or budget constraints
- Competitive monetization approaches
- Company priorities (revenue growth, user growth, profitability)
Monetization Framework
For each strategy, include:
1. Strategy Name & Description
- What is the monetization model?
- How does it work for this product?
- Who pays and what do they get?
2. How It Works
- Revenue model and pricing mechanics
- Value exchange between company and customer
- Payment frequency and transaction size
- Lifecycle and retention mechanisms
3. Audience Fit
- Why does this resonate with your target customer?
- How does it align with customer needs and preferences?
- What problems does it solve for the customer?
- Addressable market size and revenue potential
4. Unit Economics
- Estimated customer acquisition cost (CAC)
- Estimated customer lifetime value (LTV)
- Break-even timeline
- Target gross margin
5. Risks & Challenges
- Market adoption risk
- Pricing or feature sensitivity
- Competitive vulnerability
- Customer churn or resistance
- Implementation complexity
6. Competitive Position
- How do competitors monetize?
- What makes your approach differentiated?
- Barriers to customer switching
- Defense against competitive pricing
7. Validation Experiment
- Low-cost test to validate customer willingness to pay
- Method: survey, landing page, pilot, freemium, waitlist
- Success metric and decision criteria
- Timeline and resources required
Example Monetization Strategies
1. Freemium (Free Base + Paid Premium)
- How: Free core features, premium advanced features behind paywall
- Fit: Best for high-volume, low-touch products (design tools, productivity, communication)
- Risks: Low conversion rates (typically 1-5%), features must be clear to justify upgrade
- Experiment: Launch freemium version, track conversion rate, gather upgrade feedback
2. Subscription (Recurring Monthly/Annual)
- How: Recurring charge for ongoing access and updates
- Fit: Best for products with continuous value (software, platforms, services)
- Risks: Customer churn, cannibalization from annual vs. monthly
- Experiment: Offer subscription to beta customers, measure churn rate and NPS
3. Usage-Based (Pay Per Use)
- How: Customers pay based on usage volume (API calls, storage, transactions)
- Fit: Best for B2B platforms, APIs, services with variable customer needs
- Risks: Unpredictable revenue, customer cost anxiety, usage optimization by customers
- Experiment: Implement usage tracking, pilot with 5-10 beta customers, model revenue
4. Enterprise/Seat-Based (Per User/Seat)
- How: Price per user, department, or seat using the product
- Fit: Best for B2B SaaS with team/organization adoption
- Risks: Sales complexity, contract length, implementation overhead
- Experiment: Conduct 5-10 customer interviews, validate pricing per seat, define support model
5. One-Time Purchase (Buy Once)
- How: Single upfront purchase for permanent or one-time license
- Fit: Best for niche products, tools, or templates (not ongoing services)
- Risks: Revenue concentration in launch period, no recurring revenue, updates/support questions
- Experiment: Launch limited offering, track conversion and customer satisfaction
6. Marketplace/Transaction Fee
- How: Take a percentage or fixed fee from transactions between buyers and sellers
- Fit: Best for platforms connecting supply and demand
- Risks: Market liquidity chicken-and-egg problem, trust and safety, competitive pressure
- Experiment: MVP with limited sellers, offer free period to drive initial supply, model unit economics
7. Advertising/Sponsorship
- How: Generate revenue from ads, sponsored content, or brand partnerships
- Fit: Best for high-traffic, consumer-facing products
- Risks: Brand damage from intrusive ads, user experience degradation, advertiser concentration
- Experiment: Test ads with small user segment, measure engagement and revenue impact
Output Process
- Brainstorm 3-5 distinct monetization strategies (avoid repeating similar models)
- For each strategy:
- Describe how it works specifically for this product
- Assess fit with target customer and willingness to pay
- Outline key risks and challenges
- Estimate unit economics (CAC, LTV, timeline)
- Compare against competitive approaches
- For each strategy, design a low-effort validation experiment
- Prioritize by:
- Strategic fit (revenue, growth, profitability goals)
- Ease of implementation
- Market validation potential
- Competitive advantage
- Recommend 1-2 strategies to test first
- Create testing roadmap and success criteria
Strategic Considerations
- Revenue Goals: How much revenue is needed? By when?
- Growth Goals: Does monetization need to support user growth?
- Market Dynamics: Are customers ready to pay? For what?
- Competitive Pressure: How will competitors respond?
- Unit Economics: What gross margin is required for viability?
Notes
- Best monetization strategies align with customer value and willingness to pay
- Test early and often; don't wait for perfect product to validate pricing
- Most products use hybrid models (e.g., freemium + upgrade, subscription + marketplace fees)
- Pricing can be changed; customer relationships are harder to rebuild
- Monitor competitors but don't race to the bottom on price