- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add borghei/Claude-Skills --skill competitor-alternatives -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add borghei/Claude-Skills --skill competitor-alternatives -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add borghei/Claude-Skills --skill competitor-alternatives -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add borghei/Claude-Skills --skill competitor-alternatives -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/borghei/Claude-Skills/tree/HEAD/business-growth/competitor-alternativesDel publicador
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.
Before writing the comparison content, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
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
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.
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
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.
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]
For each competitor:
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]."
For each comparison dimension, write a paragraph explaining:
Tables complement paragraphs. They do not replace them.
Include:
Be explicit about ideal customer for each option:
/compare/ or /alternatives/ linking to all comparison contentPurpose: Generate a prioritized comparison page plan from competitor data with keyword targets and estimated search volume.
python scripts/comparison_page_planner.py competitors.json
python scripts/comparison_page_planner.py competitors.json --json
Purpose: Track and manage centralized competitor data files with staleness detection and update reminders.
python scripts/competitor_data_tracker.py competitor_profiles/
python scripts/competitor_data_tracker.py competitor_profiles/ --json
python scripts/competitor_data_tracker.py competitor_profiles/ --stale-days 60
Purpose: Score existing comparison page content against quality and SEO best practices.
python scripts/comparison_content_scorer.py page_content.json
python scripts/comparison_content_scorer.py page_content.json --json
>
---name: competitor-alternativesdescription: >---# business-growth/competitor-alternatives/SKILL.mdPreguntas frecuentes
Descarga business-growth/competitor-alternatives/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/borghei/Claude-Skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.