From forager-skills
Maps competitive landscapes and positions products against competitors using web search and fetching. Two modes: market landscape ("who are the competitors in X") and competitive positioning ("how do we compare to Y").
How this skill is triggered — by the user, by Claude, or both
Slash command
/forager-skills:competitive-intelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill helps users understand competitive landscapes and position products
This skill helps users understand competitive landscapes and position products strategically. It's for people who are building or selling — not shopping.
There are two modes:
Detect the mode from the user's query. If they're asking "what's out there" or "who are the competitors", it's landscape. If they're asking "how do we compare" or "what are we missing vs X", it's positioning.
Use whatever search and fetch tools are available in your environment. In order of preference:
mcp__duckduckgo__search or mcp__duckduckgo__jina_fetch are
available, use those.WebSearch,
web_search, search) or a URL fetch tool (e.g., WebFetch, fetch), use those.uvx:uvx --python '>=3.10,<3.14' web-forager search "your query" --max-results 8 --output-format json
uvx cannot run the packaged CLI, run ddgs
through uv without touching the current project environment:uv run --no-project --python '>=3.10,<3.14' --with 'ddgs>=9.5.2' python - <<'PY'
from ddgs import DDGS
results = DDGS().text(query="your query", max_results=8)
for r in results:
print(r["title"], r["href"], r["body"])
PY
curl -s "https://r.jina.ai/https://example.com"
The skill works with any combination of search + fetch. You need at least one way to search the web and one way to read a URL's content.
Freshness matters. Markets move fast — a year-old comparison can miss new entrants, pricing changes, or pivots. Always include the current year in search queries. When fetching sources, prefer articles published within the last 12 months.
Use this mode when the user wants to understand a market — either because they have a product idea, are exploring an opportunity, or need to map the competitive terrain.
Before searching, clarify:
If the user gives enough context (like "I want to build a Notion competitor for engineers"), don't over-interview — start researching.
Search across these angles — each reveals a different layer of the market:
Player discovery:
Market dynamics:
Business models & pricing:
User sentiment & gaps:
Pick 5-8 URLs across angles. Prioritize:
Organize your findings into a clear picture:
Player categorization — group competitors by tier or approach:
Positioning analysis — how does each player position themselves? What's their primary value proposition? Who do they target? How do they price?
Gap analysis — based on user complaints, switching patterns, and underserved segments, where are the opportunities? What problems aren't being solved well?
Positioning map — identify the two most important axes that differentiate players in this market (e.g., general vs specialized, enterprise vs SMB, platform vs point solution). Plot the players on a 2x2 text diagram. This makes the white space — the underserved quadrant — immediately visible.
Use the Market Landscape Output Format below.
Use this mode when the user has a product (or a specific product concept) and wants to understand how it compares to named competitors.
Before searching, clarify:
Search with strategic intent — you're not just comparing specs, you're looking for competitive advantage and blind spots:
Head-to-head:
Feature & capability gaps:
Market perception:
Pricing intelligence:
Pick 4-6 URLs per competitor. Prioritize:
Go beyond a feature checklist. For each competitor, assess:
Use the Competitive Positioning Output Format below.
# Market Landscape: [Category/Market]
## Executive summary
[3-5 sentences: what this market looks like right now, how big it is (if data
available), key trends, and the most notable gap or opportunity]
## Market map
### Leaders
| Player | Positioning | Target audience | Pricing model | Est. scale |
|--------|-------------|-----------------|---------------|------------|
| [Name] | [one-line value prop] | [who they serve] | [free/freemium/$X/mo] | [users/revenue/funding if known] |
### Challengers
| Player | Positioning | Target audience | Pricing model | Est. scale |
|--------|-------------|-----------------|---------------|------------|
### Niche players
| Player | Positioning | Target audience | Pricing model | Est. scale |
|--------|-------------|-----------------|---------------|------------|
### Emerging
| Player | Positioning | Target audience | Pricing model | Est. scale |
|--------|-------------|-----------------|---------------|------------|
## Positioning map
[A text-based 2x2 matrix that plots players along the two axes most relevant to
this market. Choose axes that reveal where the white space is — e.g., "General
Purpose vs Specialized" and "Cloud-First vs Self-Hosted", or "Enterprise vs SMB"
and "Full Platform vs Point Solution". Place each player on the map and call out
where the gap is.]
## Pricing landscape
[Summary of how the market prices: what's the typical range? Free tier common?
Per-seat vs flat rate vs usage-based? Any pricing trends?]
## Gaps & opportunities
- [Underserved segment or unmet need, with evidence]
- [Common complaint about existing solutions]
- [Emerging trend that incumbents haven't addressed]
- ...
## Barriers to entry
- [What makes it hard to compete in this market — network effects, switching costs,
data moats, regulatory, etc.]
## Key takeaways
[2-3 actionable insights for someone considering entering or investing in this market]
## Sources
1. [Title](url) — [what this source contributed]
# Competitive Analysis: [Your Product] vs the Market
## Executive summary
[3-5 sentences: where you stand, your strongest differentiators, and the most
important competitive gap to address]
## Competitive matrix
| Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
|------------|---------------|----------------|----------------|----------------|
| [Key feature 1] | ... | ... | ... | ... |
| [Key feature 2] | ... | ... | ... | ... |
| Pricing (entry) | ... | ... | ... | ... |
| Pricing (pro/team) | ... | ... | ... | ... |
| Target audience | ... | ... | ... | ... |
## Per-competitor breakdown
### vs [Competitor A]
**Their positioning**: [how they describe themselves]
**Where they're stronger**: [honest assessment]
**Where you're stronger**: [with evidence]
**Their users complain about**: [real pain points from reviews/forums]
**Their recent moves**: [what they've shipped or announced recently]
**Threat level**: [High/Medium/Low — how much do they directly compete with you?]
### vs [Competitor B]
[Same structure]
## Pricing comparison
| Tier | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
|------|---------------|----------------|----------------|----------------|
| Free/Starter | ... | ... | ... | ... |
| Pro/Team | ... | ... | ... | ... |
| Enterprise | ... | ... | ... | ... |
[Commentary on pricing strategy: are you priced competitively? Is there a positioning
opportunity in pricing?]
## Your differentiators
[What genuinely sets you apart — not marketing claims, but real differences backed
by evidence from the research]
## Gaps to address
[Features or capabilities where competitors are ahead and users notice. Prioritized
by impact — what would move the needle most?]
## Strategic recommendations
1. [Actionable recommendation based on the analysis]
2. [Another recommendation]
3. [Another recommendation]
## Sources
1. [Title](url) — [what this source contributed]
Adapt both templates to fit the specific market and products being analyzed. The templates are starting points — add or remove sections based on what's relevant. A B2C consumer product comparison might not need "Enterprise pricing"; a developer tool comparison might need a "Developer experience" section.
The goal is actionable strategic intelligence, not a generic report. Every section should help the user make better decisions about where to invest, how to position, and what to build next.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub cyranob/web-forager --plugin forager-skills