Files
skills/commands/competitive-analysis.md
zeekayandHanzo Dev 65c3b27843 160 marketing, growth and PM skills, on our own connectors
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]>
2026-09-15 01:27:26 -07:00

3.5 KiB

description, argument-hint, source
description argument-hint source
Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities <your product or market> phuryn/pm-skills

/competitive-analysis -- Competitive Landscape Analysis

Research and analyze your competitive landscape. Identifies direct and indirect competitors, maps positioning, and surfaces differentiation opportunities.

Invocation

/competitive-analysis AI-powered project management tools
/competitive-analysis Our product vs Notion, Asana, and Monday.com
/competitive-analysis [upload a competitor list or market brief]

Workflow

Step 1: Understand the Competitive Context

Ask:

  • What is your product? What category does it compete in?
  • Any specific competitors you want analyzed? Or should I identify them?
  • What's the lens? (feature comparison, positioning, pricing, go-to-market)
  • What will you use this analysis for? (strategy, sales enablement, investor pitch, product roadmap)

Step 2: Identify Competitors

Apply the competitor-analysis skill:

  • Identify 5 direct competitors (same category, same buyer)
  • Identify 2-3 indirect competitors (different approach, same job-to-be-done)
  • Note emerging/disruptive players if relevant
  • Use web research to gather current information

Step 3: Analyze Each Competitor

For each competitor:

  • Positioning: How they describe themselves, target audience, key messaging
  • Strengths: What they do well, where they win
  • Weaknesses: Where they fall short, common complaints
  • Pricing: Model and price points (if public)
  • Market traction: Funding, team size, customer base signals
  • Recent moves: New features, partnerships, pivots

Step 4: Generate Competitive Analysis

## Competitive Analysis: [Your Product/Market]

**Date**: [today]
**Analyzed**: [count] competitors

### Market Overview
[2-3 sentences on market dynamics, trends, and where it's heading]

### Competitive Landscape
| Competitor | Category | Target | Positioning | Strength | Weakness |
|-----------|----------|--------|------------|----------|----------|

### Feature Comparison Matrix
| Capability | Your Product | Competitor A | Competitor B | Competitor C |
|-----------|-------------|-------------|-------------|-------------|

### Positioning Map
[2x2 matrix showing competitive positioning on key dimensions]

### Differentiation Opportunities
1. **[Opportunity]** — [why it's defensible and valuable]
2. ...

### Competitive Threats
1. **[Threat]** — [what to watch for, recommended response]
2. ...

### Recommendations
- **Double down on**: [your unique advantages]
- **Close the gap on**: [table-stakes features you're missing]
- **Ignore**: [competitor moves that aren't worth responding to]

Save as markdown.

Step 5: Offer Next Steps

  • "Want me to create a battlecard for sales against a specific competitor?"
  • "Should I develop positioning that differentiates from the top competitors?"
  • "Want me to identify feature gaps to close and add to the roadmap?"

Notes

  • Web research is used for current competitor data — results are as fresh as available sources
  • Distinguish between "table stakes" (must-have to compete) and "differentiators" (must-have to win)
  • Don't just list features — analyze why competitors make the choices they make
  • Pricing intelligence should note whether pricing is public, usage-based, or requires sales contact
  • Update this analysis quarterly — competitive landscapes shift fast