SkillAgentSearch skills...

competitor-alternatives

Create competitor comparison and alternative pages for SEO and sales enablement

Install / Use

npx skills add borghei/Claude-Skills --skill competitor-alternatives

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Category

Marketing

Supported Platforms

Universal

Tags

Our assessment of competitor-alternatives

competitor-alternatives scores 89/100 on our quality scale, 291st of 646 Marketing skills we index (top 46%).

Its SKILL.md is 19 KB long, well organised into 45 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so competitor-alternatives is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

competitor-alternatives compared with similar skills

All 4 of these similar skills score higher than competitor-alternatives; compare them before choosing.

SkillScoreStarsUpdatedFormat
competitor-alternatives (this skill)by borghei8981757d agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install competitor-alternatives?
Run npx skills add borghei/Claude-Skills --skill competitor-alternatives. The install tabs above show the steps for each supported agent.
Which AI agents does competitor-alternatives work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is competitor-alternatives safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is competitor-alternatives still maintained?
The repository was last updated about 2 months ago, so competitor-alternatives is actively maintained.

name: competitor-alternatives description: > Create competitor comparison and alternative pages for SEO and sales enablement. Use when building alternative pages, vs pages, or competitor-vs-competitor pages, planning comparison content, or managing competitor data. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: - competitive-content - seo - comparison-pages - alternative-pages - sales-enablement

Competitor & Alternative Pages

Production-grade framework for creating competitor comparison and alternative pages. Covers 4 page formats, centralized competitor data architecture, deep research methodology, SEO optimization, content templates, and ongoing maintenance strategy. Designed for both SEO traffic capture and sales enablement.


Table of Contents


When to Use

| Trigger | Action | |---------|--------| | Prospects comparing you to competitors | Create vs-pages for top 3 competitors | | Search volume exists for "[competitor] alternative" | Create singular alternative pages | | Sales team needs battle card content | Create vs-pages with objection handling | | Competitor has comparison pages about you | Create counter-comparison pages | | SEO gap on competitor-branded keywords | Build full alternative page set |


Clarify First

Before writing the comparison content, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Page format — singular alternative, plural alternatives, you-vs-competitor, or competitor-vs-competitor (selects the page structure template)
  • [ ] Primary goal — SEO traffic capture vs sales enablement (changes tone, depth, and whether to include objection handling)
  • [ ] Target competitor + data freshness — who, and how recent the pricing/feature data is (every claim must be verifiable)
  • [ ] Honest positioning — who you genuinely win for and who the competitor wins for (drives the trust-building "who it's for" sections)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the page.

Core Principles

1. Honesty Builds Trust

  • Acknowledge competitor strengths explicitly
  • Be accurate about your own limitations
  • Readers are actively comparing -- they will verify your claims
  • A dishonest comparison page damages your brand more than no page at all

2. Help Them Decide (Not Just Sell)

  • Different tools genuinely fit different needs
  • Be explicit about who you are best for AND who the competitor is best for
  • Reduce evaluation friction -- save prospects research time

3. Depth Over Checkbox Tables

  • Go beyond feature checklists (every competitor does those)
  • Explain WHY differences matter for specific use cases
  • Include real scenarios and workflows
  • Show, do not just tell

4. Single Source of Truth

  • Centralize competitor data -- do not maintain facts across 10 pages
  • Updates propagate to all pages automatically
  • Track last-verified date per data point

The 4 Page Formats

Format 1: [Competitor] Alternative (Singular)

Intent: User is actively looking to switch FROM a specific competitor.

URL: /alternatives/[competitor] or /[competitor]-alternative

Keywords: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"

Page Structure:

1. Why people look for alternatives (validate their pain, 2-3 paragraphs)
2. TL;DR: You as the alternative (quick positioning, 3-4 bullets)
3. Detailed comparison (features, pricing, support -- paragraph format, not just tables)
4. Who should switch (and who should NOT -- be honest)
5. Migration path (what transfers, what needs reconfiguration)
6. Testimonials from customers who switched
7. CTA: Start free trial or request demo

Format 2: [Competitor] Alternatives (Plural)

Intent: User is researching options broadly, earlier in the buying journey.

URL: /alternatives/[competitor]-alternatives or /best-[competitor]-alternatives

Keywords: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"

Page Structure:

1. Why people look for alternatives (common pain points, 2-3 paragraphs)
2. What to look for in an alternative (evaluation criteria framework)
3. List of 5-7 alternatives (you first, but include real options)
4. Summary comparison table
5. Detailed breakdown of each alternative (150-200 words each)
6. Recommendation by use case ("Best for [X]: [Tool]")
7. CTA

Important: Include 5-7 REAL alternatives. Being genuinely helpful ranks better and builds trust.

Format 3: You vs [Competitor]

Intent: User is directly comparing you to a specific competitor.

URL: /vs/[competitor] or /compare/[you]-vs-[competitor]

Keywords: "[You] vs [Competitor]", "[Competitor] vs [You]"

Page Structure:

1. TL;DR summary (key differences in 2-3 sentences)
2. At-a-glance comparison table (8-12 dimensions)
3. Detailed comparison by category (paragraph format per category):
   - Features
   - Pricing
   - Ease of use / UX
   - Support and documentation
   - Integrations
   - Security and compliance
4. Who [You] is best for (3-4 bullets)
5. Who [Competitor] is best for (3-4 bullets -- be honest)
6. What customers say (testimonials from switchers)
7. Migration support
8. CTA

Format 4: [Competitor A] vs [Competitor B]

Intent: User is comparing two competitors (neither is you directly).

URL: /compare/[competitor-a]-vs-[competitor-b]

Page Structure:

1. Overview of both products (neutral, factual)
2. Comparison by category (same categories as Format 3)
3. Who each is best for
4. "Consider a third option" (introduce yourself naturally)
5. Three-way comparison table (both competitors + you)
6. CTA

Why this works: Captures competitor-branded search traffic, positions you as a knowledgeable authority, and introduces you to buyers who might not have considered you.


Content Architecture

Centralized Competitor Data

Create a single data file per competitor that feeds all comparison pages.

Competitor Data Structure:

Competitor: [Name]
Last Verified: [Date]
Website: [URL]

Positioning:
  - Tagline: [Their tagline]
  - Target audience: [Who they target]
  - Primary differentiator: [What they claim is unique]

Pricing:
  - Free tier: [Yes/No, details]
  - Entry price: [$X/mo]
  - Mid-tier price: [$X/mo]
  - Enterprise: [Custom / $X/mo]
  - Billing: [Monthly, Annual, Both]
  - Trial: [Length, CC required?]

Features:
  - [Category 1]: [Rating 1-5, notes]
  - [Category 2]: [Rating 1-5, notes]
  - [Category 3]: [Rating 1-5, notes]

Strengths:
  - [Strength 1 with evidence]
  - [Strength 2 with evidence]

Weaknesses:
  - [Weakness 1 with evidence source]
  - [Weakness 2 with evidence source]

Best For: [Description of ideal customer]
Not Ideal For: [Description of poor fit]

Common Complaints (from reviews):
  - [Complaint 1] (source: G2/Capterra/etc.)
  - [Complaint 2]
  - [Complaint 3]

Migration Notes:
  - Data export: [Available? Format?]
  - API migration: [Available?]
  - Switching time: [Estimated]

Research Methodology

Deep Research Process

For each competitor:

  1. Sign up and use the product -- Create a real account, go through onboarding, test core workflows. There is no substitute for hands-on experience.
  2. Pricing verification -- Screenshot current pricing page. Note what is included at each tier. Check for hidden costs.
  3. Review mining -- Read 50+ reviews on G2, Capterra, TrustRadius. Categorize into praise themes, complaint themes, and feature requests.
  4. Customer feedback -- Talk to your customers who switched from (or to) this competitor. Capture switching reasons and experience quotes.
  5. Content audit -- Review their positioning, their comparison pages about you (if any), their changelog, their blog.
  6. Financial/growth signals -- Check Crunchbase for funding, LinkedIn for employee count trends, job postings for strategic direction.

Verification Schedule

| Frequency | What to Verify | |-----------|---------------| | Monthly | Pricing (check for changes) | | Quarterly | Feature set, major product updates | | When notified | Customer reports competitor change | | Annually | Full refresh of all competitor data |


Essential Content Sections

TL;DR Summary

Every comparison page starts with a 2-3 sentence summary for scanners. This is the most-read section.

Template: "[Your product] is the better choice if you need [differentiator 1] and [differentiator 2]. [Competitor] is better if [their strength]. The biggest differences are [difference 1] and [difference 2]."

Paragraph Comparisons (Not Just Tables)

For each comparison dimension, write a paragraph explaining:

  • How each product handles this area
  • Why the differences matter
  • Who the difference matters most to

Tables complement paragraphs. They do not replace them.

Pricing Comparison

Include:

  • Tier-by-tier price comparison
  • What is included at each tier (not just the name)
  • Hidden costs (setup fees, overage charges, add-on pricing)
  • Total cost calculation for a sample team size (e.g., "For a team of 10")

Who It Is For

Be explicit about ideal customer for each option:

| Product | Best For | Not Ideal For | |---------|----------|---------------| | Your product | [Specific persona/use case] | [Honest admission of limitations] | | Competitor | [Specific persona/use case] | [Their documented weaknesses] |

Migration Section

| Element | Content | |---------|---------| | What transfers | Data, settings, integrations that migrate | | What needs reconfiguration | What must be set up fresh | | Support offered | Migration assistance, documentation | | Estimated time | "Most teams migrate in [timeframe]" | | Customer quote | Quote from someone who switched |


SEO Strategy

Keyword Targeting

| Format | Primary Keywords | Secondary Keywords | |--------|-----------------|-------------------| | Singular alternative | "[Competitor] alternative" | "switch from [Competitor]", "replace [Competitor]" | | Plural alternatives | "[Competitor] alternatives" | "best [Competitor] alternatives", "tools like [Competitor]" | | Vs page | "[You] vs [Competitor]" | "[Competitor] vs [You]", "[You] or [Competitor]" | | Competitor vs competitor | "[A] vs [B]" | "[B] vs [A]", "[A] or [B]" |

On-Page SEO

  • Title tag: "[Your Product] vs [Competitor]: Detailed Comparison [Year]"
  • Meta description: Summarize the key difference and who each is best for
  • H1: Match the primary keyword
  • Schema: Consider FAQPage schema for comparison questions

Internal Linking

  • Link between all competitor pages (alternative <-> vs page for same competitor)
  • Link from feature pages to relevant comparisons
  • Link from blog posts mentioning competitors
  • Create a hub page: /compare/ or /alternatives/ linking to all comparison content

Maintenance and Updates

Update Triggers

| Trigger | Action | Priority | |---------|--------|----------| | Competitor changes pricing | Update pricing comparison on all affected pages | High | | Competitor launches major feature | Update feature comparison + add "Recent Changes" note | High | | Your product launches feature that closes a gap | Update comparison to reflect new advantage | High | | New customer s

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryMarketing
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium