
Competitor Alternatives
Create alternative, comparison, and vs pages that rank for competitive queries and support sales positioning with honest differentiation.
Overview
Competitor Alternatives is an agent skill most often used in Launch (also Idea, Grow) that drafts SEO comparison and alternative pages with structured competitive positioning.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill competitor-alternativesWhat is this skill?
- Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor
- Reads `.agents/product-marketing-context.md` first to avoid redundant discovery questions
- Initial assessment for product value prop, ICP, pricing, strengths, and honest weaknesses
- Maps competitive landscape before drafting positioning pages
- Pairs with sales-enablement skill for sales-specific competitor docs
- Four comparison page formats: singular alternative, plural alternatives, you vs competitor, competitor vs competitor
- Skill metadata version 1.1.0
Adoption & trust: 54.4k installs on skills.sh; 32.4k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Evaluators search “[your product] vs [competitor]” or “[competitor] alternative” but you have no credible page that ranks or answers how you really compare.
Who is it for?
SaaS or product-led solo builders launching competitive SEO pages and enablement copy who already know their differentiators and want honest comparisons.
Skip if: Pure internal sales battle cards with no public SEO goal—use sales-enablement instead; skip if you lack basic product positioning to assess.
When should I use this skill?
User mentions alternative page, vs page, competitor comparison, battle card, competitor teardown, or how you compare to a named product.
What do I get? / Deliverables
You get format-matched competitor or alternative page drafts grounded in product and landscape assessment, ready to publish for search and sales conversations.
- Competitor or alternative page draft in chosen format
- Positioning outline grounded in ICP and pricing
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch/SEO is the canonical shelf because the skill optimizes for ranking on competitive search terms and evaluator-ready comparison content. SEO subphase covers alternative pages, vs pages, and battle-card-style web content aimed at high-intent competitive keywords.
Where it fits
Draft a honest strengths-and-weaknesses matrix before committing to which rivals merit dedicated vs URLs.
Publish “Acme alternative” and “Acme vs Beta” pages mapped to the four supported formats.
Refresh plural alternatives roundup when new entrants change the category narrative.
Use competitor framing to narrow MVP scope against what incumbents already solve well.
How it compares
Structured SEO comparison pages skill, not a generic blog writer or automated SERP scraper.
Common Questions / FAQ
Who is competitor-alternatives for?
Indie SaaS founders and marketers creating public comparison or alternative URLs and related competitive positioning content.
When should I use competitor-alternatives?
During Launch for SEO vs and alternative URLs, during Idea when teardown informs positioning, or during Grow when refreshing competitive content for lifecycle campaigns.
Is competitor-alternatives safe to install?
It guides content strategy in your workspace; review the Security Audits panel on this Prism page and fact-check claims before publishing competitive statements.
SKILL.md
READMESKILL.md - Competitor Alternatives
# Competitor & Alternative Pages You are an expert in creating competitor comparison and alternative pages. Your goal is to build pages that rank for competitive search terms, provide genuine value to evaluators, and position your product effectively. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before creating competitor pages, understand: 1. **Your Product** - Core value proposition - Key differentiators - Ideal customer profile - Pricing model - Strengths and honest weaknesses 2. **Competitive Landscape** - Direct competitors - Indirect/adjacent competitors - Market positioning of each - Search volume for competitor terms 3. **Goals** - SEO traffic capture - Sales enablement - Conversion from competitor users - Brand positioning --- ## Core Principles ### 1. Honesty Builds Trust - Acknowledge competitor strengths - Be accurate about your limitations - Don't misrepresent competitor features - Readers are comparing—they'll verify claims ### 2. Depth Over Surface - Go beyond feature checklists - Explain *why* differences matter - Include use cases and scenarios - Show, don't just tell ### 3. Help Them Decide - Different tools fit different needs - Be clear about who you're best for - Be clear about who competitor is best for - Reduce evaluation friction ### 4. Modular Content Architecture - Competitor data should be centralized - Updates propagate to all pages - Single source of truth per competitor --- ## Page Formats ### Format 1: [Competitor] Alternative (Singular) **Search intent**: User is actively looking to switch from a specific competitor **URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative` **Target keywords**: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]" **Page structure**: 1. Why people look for alternatives (validate their pain) 2. Summary: You as the alternative (quick positioning) 3. Detailed comparison (features, service, pricing) 4. Who should switch (and who shouldn't) 5. Migration path 6. Social proof from switchers 7. CTA --- ### Format 2: [Competitor] Alternatives (Plural) **Search intent**: User is researching options, earlier in journey **URL pattern**: `/alternatives/[competitor]-alternatives` **Target keywords**: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]" **Page structure**: 1. Why people look for alternatives (common pain points) 2. What to look for in an alternative (criteria framework) 3. List of alternatives (you first, but include real options) 4. Comparison table (summary) 5. Detailed breakdown of each alternative 6. Recommendation by use case 7. CTA **Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better. --- ### Format 3: You vs [Competitor] **Search intent**: User is directly comparing you to a specific competitor **URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]` **Target keywords**: "[You] vs [Competitor]", "[Competitor] vs [Y