Competitor Alternatives
Structure centralized competitor YAML/markdown so you can scale honest comparison and alternative pages without duplicating research.
Overview
competitor-alternatives is an agent skill most often used in Idea (also Launch SEO) that defines centralized competitor profiles for scalable comparison and alternative content pages.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill competitor-alternativesWhat is this skill?
- Single competitor_data/ source of truth per rival (Notion, Airtable, etc.)
- YAML-style fields: pricing tiers, features 1–5, strengths, weaknesses, best-for
- Honest strengths/weaknesses sections for credible comparison copy
- Scalable pattern for many competitor alternative landing pages
- Separation of positioning, audience, and not-ideal-for qualifiers
- Per-competitor template with features rated on a 1–5 scale
- Documented sections: pricing model, strengths, weaknesses, best_for, not_ideal_for
Adoption & trust: 524 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your comparison pages drift because each competitor write-up lives in a different doc with inconsistent pricing, features, and positioning.
Who is it for?
Indie SaaS founders building programmatic SEO comparison pages who want one maintained dossier per competitor.
Skip if: Teams needing real-time competitor price scraping or deep technical tear-downs without any content publishing goal.
When should I use this skill?
User needs content architecture for competitor comparison pages, centralized competitor profiles, or scalable alternative-page data.
What do I get? / Deliverables
You get a repeatable competitor_data template per rival so alternative and versus pages stay accurate and on-brand as you add more URLs.
- competitor_data/ folder layout with per-rival profiles
- YAML or markdown competitor record following the template
- Reusable blocks for alternative and versus page generation
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Competitor architecture belongs in Idea because you define positioning and comparison data before pages go live in Launch. The template is explicitly for competitor intelligence and alternative-page scaffolding—not pricing experiments or prototype code.
Where it fits
Draft notion.md and airtable.md profiles with pricing and feature scores before picking a wedge.
Use not-ideal-for and best-for fields to narrow MVP scope against incumbent strengths.
Generate consistent alternative page sections from competitor_data without rewriting research.
Refresh weakness and pricing fields when rivals change plans for lifecycle email and blog updates.
How it compares
Content information architecture for comparisons—not a live competitive intelligence bot or PPC keyword tool.
Common Questions / FAQ
Who is competitor-alternatives for?
Solo builders and small marketing-led teams shipping SaaS or content products who need many competitor/alternative pages from one data model.
When should I use competitor-alternatives?
In Idea competitors research when mapping the market; in Validate scope when clarifying positioning; in Launch SEO when drafting versus and alternative landing pages from shared profiles.
Is competitor-alternatives safe to install?
It is editorial structure guidance only; review the Security Audits panel on this Prism page for the underlying skill package before enabling it in production content repos.
SKILL.md
READMESKILL.md - Competitor Alternatives
# Content Architecture for Competitor Pages How to structure and maintain competitor data for scalable comparison pages. ## Centralized Competitor Data Create a single source of truth for each competitor: ``` competitor_data/ ├── notion.md ├── airtable.md ├── monday.md └── ... ``` --- ## Competitor Data Template Per competitor, document: ```yaml name: Notion website: notion.so tagline: "The all-in-one workspace" founded: 2016 headquarters: San Francisco # Positioning primary_use_case: "docs + light databases" target_audience: "teams wanting flexible workspace" market_position: "premium, feature-rich" # Pricing pricing_model: per-seat free_tier: true free_tier_limits: "limited blocks, 1 user" starter_price: $8/user/month business_price: $15/user/month enterprise: custom # Features (rate 1-5 or describe) features: documents: 5 databases: 4 project_management: 3 collaboration: 4 integrations: 3 mobile_app: 3 offline_mode: 2 api: 4 # Strengths (be honest) strengths: - Extremely flexible and customizable - Beautiful, modern interface - Strong template ecosystem - Active community # Weaknesses (be fair) weaknesses: - Can be slow with large databases - Learning curve for advanced features - Limited automations compared to dedicated tools - Offline mode is limited # Best for best_for: - Teams wanting all-in-one workspace - Content-heavy workflows - Documentation-first teams - Startups and small teams # Not ideal for not_ideal_for: - Complex project management needs - Large databases (1000s of rows) - Teams needing robust offline - Enterprise with strict compliance # Common complaints (from reviews) common_complaints: - "Gets slow with lots of content" - "Hard to find things as workspace grows" - "Mobile app is clunky" # Migration notes migration_from: difficulty: medium data_export: "Markdown, CSV, HTML" what_transfers: "Pages, databases" what_doesnt: "Automations, integrations setup" time_estimate: "1-3 days for small team" ``` --- ## Your Product Data Same structure for yourself—be honest: ```yaml name: [Your Product] # ... same fields strengths: - [Your real strengths] weaknesses: - [Your honest weaknesses] best_for: - [Your ideal customers] not_ideal_for: - [Who should use something else] ``` --- ## Page Generation Each page pulls from centralized data: - **[Competitor] Alternative page**: Pulls competitor data + your data - **[Competitor] Alternatives page**: Pulls competitor data + your data + other alternatives - **You vs [Competitor] page**: Pulls your data + competitor data - **[A] vs [B] page**: Pulls both competitor data + your data **Benefits**: - Update competitor pricing once, updates everywhere - Add new feature comparison once, appears on all pages - Consistent accuracy across pages - Easier to maintain at scale --- ## Index Page Structure ### Alternatives Index **URL**: `/alternatives` or `/alternatives/index` **Purpose**: Lists all "[Competitor] Alternative" pages **Page structure**: 1. Headline: "[Your Product] as an Alternative" 2. Brief intro on why people switch to you 3. List of all alternative pages with: - Competitor name/logo - One-line summary of key differentiator vs. that competitor - Link to full comparison 4. Common reasons people switch (aggregated) 5. CTA **Example**: ```markdown ## Explore [Your Product] as an Alternative Looking to switch? See how [Your Product] compares to the tools you're evaluating: - **[Notion Alternative](/alternatives/notion)** — Better for teams who need [X] - **[Airtable Alternative](/alternatives/airtable)** — Better for teams who need [Y] - **[Monday Alternative](/alternatives/monday)** — Better for teams who need [Z] ``` --- ### Vs Comparisons Index **URL**: `/vs` or `/compare` **Purpose**: Lists all "You vs [Competitor]" and "[A] vs [B]" pages **Page structure**: 1. Headline: "Compare [Your Product]" 2. Section: "[Your Product] vs Competitors" — lis