competitors
bycoreyhaines31· 76 skills
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
How to install competitors?
coreyhaines31/marketingskills/competitors
$npx -y skills add coreyhaines31/marketingskills --skill competitorsInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/coreyhaines31/marketingskills" --skill "coreyhaines31/marketingskills/competitors"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/coreyhaines31/marketingskills" that are relevant to the current task. Run `npx skills add "https://github.com/coreyhaines31/marketingskills"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # Competitor & Alternative Pages |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## Initial Assessment |
| 6 | |
| 7 | **Check for product marketing context first:** |
| 8 | If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. |
| 9 | |
| 10 | Before creating competitor pages, understand: |
| 11 | |
| 12 | 1. **Your Product** |
| 13 | - Core value proposition |
| 14 | - Key differentiators |
| 15 | - Ideal customer profile |
| 16 | - Pricing model |
| 17 | - Strengths and honest weaknesses |
| 18 | |
| 19 | 2. **Competitive Landscape** |
| 20 | - Direct competitors |
| 21 | - Indirect/adjacent competitors |
| 22 | - Market positioning of each |
| 23 | - Search volume for competitor terms |
| 24 | |
| 25 | 3. **Goals** |
| 26 | - SEO traffic capture |
| 27 | - Sales enablement |
| 28 | - Conversion from competitor users |
| 29 | - Brand positioning |
| 30 | |
| 31 | --- |
| 32 | |
| 33 | ## Core Principles |
| 34 | |
| 35 | ### 1. Honesty Builds Trust |
| 36 | - Acknowledge competitor strengths |
| 37 | - Be accurate about your limitations |
| 38 | - Don't misrepresent competitor features |
| 39 | - Readers are comparing—they'll verify claims |
| 40 | |
| 41 | ### 2. Depth Over Surface |
| 42 | - Go beyond feature checklists |
| 43 | - Explain *why* differences matter |
| 44 | - Include use cases and scenarios |
| 45 | - Show, don't just tell |
| 46 | |
| 47 | ### 3. Help Them Decide |
| 48 | - Different tools fit different needs |
| 49 | - Be clear about who you're best for |
| 50 | - Be clear about who competitor is best for |
| 51 | - Reduce evaluation friction |
| 52 | |
| 53 | ### 4. Modular Content Architecture |
| 54 | - Competitor data should be centralized |
| 55 | - Updates propagate to all pages |
| 56 | - Single source of truth per competitor |
| 57 | |
| 58 | --- |
| 59 | |
| 60 | ## Page Formats |
| 61 | |
| 62 | ### Format 1: [Competitor] Alternative (Singular) |
| 63 | |
| 64 | **Search intent**: User is actively looking to switch from a specific competitor |
| 65 | |
| 66 | **URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative` |
| 67 | |
| 68 | **Target keywords**: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]" |
| 69 | |
| 70 | **Page structure**: |
| 71 | 1. Why people look for alternatives (validate their pain) |
| 72 | 2. Summary: You as the alternative (quick positioning) |
| 73 | 3. Detailed comparison (features, service, pricing) |
| 74 | 4. Who should switch (and who shouldn't) |
| 75 | 5. Migration path |
| 76 | 6. Social proof from switchers |
| 77 | 7. CTA |
| 78 | |
| 79 | --- |
| 80 | |
| 81 | ### Format 2: [Competitor] Alternatives (Plural) |
| 82 | |
| 83 | **Search intent**: User is researching options, earlier in journey |
| 84 | |
| 85 | **URL pattern**: `/alternatives/[competitor]-alternatives` |
| 86 | |
| 87 | **Target keywords**: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]" |
| 88 | |
| 89 | **Page structure**: |
| 90 | 1. Why people look for alternatives (common pain points) |
| 91 | 2. What to look for in an alternative (criteria framework) |
| 92 | 3. List of alternatives (you first, but include real options) |
| 93 | 4. Comparison table (summary) |
| 94 | 5. Detailed breakdown of each alternative |
| 95 | 6. Recommendation by use case |
| 96 | 7. CTA |
| 97 | |
| 98 | **Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better. |
| 99 | |
| 100 | **AI-answer expectations by stage**: these pages often earn *citations* in AI answers, but whether AI *recommends* your brand from them depends on offsite consensus (reviews, forums, analysts) — for emerging brands, a self-ranked list can surface the competitors in the AI answer while you get only the citation. Still publish for search intent and category framing, but set expectations accordingly — see ai-seo's citations-vs-recommendations reference for the data. |
| 101 | |
| 102 | --- |
| 103 | |
| 104 | ### Format 3: You vs [Competitor] |
| 105 | |
| 106 | **Search intent**: User is directly comparing you to a specific competitor |
| 107 | |
| 108 | **URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]` |
| 109 | |
| 110 | **Target keywords**: "[You] vs [Competitor]", "[Competitor] vs [You]" |
| 111 | |
| 112 | **Page structure**: |
| 113 | 1. TL;DR summary (key differences in 2-3 sentences) |
| 114 | 2. At-a-glance comparison table |
| 115 | 3. Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations) |
| 116 | 4. Who [You] is best for |
| 117 | 5. Who [Competitor] is best for (be honest) |
| 118 | 6. What customers say (testimonials from switchers) |
| 119 | 7. Migration support |
| 120 | 8. CTA |
| 121 | |
| 122 | --- |
| 123 | |
| 124 | ### Format 4: [Competitor A] vs [Competitor B] |
| 125 | |
| 126 | **Search intent**: User comparing two competitors (not you directly) |
| 127 | |
| 128 | **URL pattern**: `/compare/[competitor-a]-vs-[competitor-b]` |
| 129 | |
| 130 | **Page structure**: |
| 131 | 1. Overview of both products |
| 132 | 2. Comparison by category |
| 133 | 3. Who each is best for |
| 134 | 4. The third option (introduce yourself) |
| 135 | 5. Comparison table (all three) |
| 136 | 6. CTA |
| 137 | |
| 138 | **Why this works**: Captures search traffic for competitor terms, positions you as knowledgeable. |
| 139 | |
| 140 | --- |
| 141 | |
| 142 | ## Essential Sections |
| 143 | |
| 144 | ### TL;DR Summary |
| 145 | Start every page with a quick summary for scanners—key differences in 2-3 sentences. |
| 146 | |
| 147 | ### Paragraph Comparisons |
| 148 | Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters. |
| 149 | |
| 150 | ### Feature Comparison |
| 151 | For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation. |
| 152 | |
| 153 | ### Pricing Comparison |
| 154 | Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size. |
| 155 | |
| 156 | ### Who It's For |
| 157 | Be explicit about ideal customer for each option. Honest recommendations build trust. |
| 158 | |
| 159 | ### Migration Section |
| 160 | Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched. |
| 161 | |
| 162 | **For detailed templates**: See [references/templates.md](references/templates.md) |
| 163 | |
| 164 | --- |
| 165 | |
| 166 | ## Content Architecture |
| 167 | |
| 168 | ### Centralized Competitor Data |
| 169 | Create a single source of truth for each competitor with: |
| 170 | - Positioning and target audience |
| 171 | - Pricing (all tiers) |
| 172 | - Feature ratings |
| 173 | - Strengths and weaknesses |
| 174 | - Best for / not ideal for |
| 175 | - Common complaints (from reviews) |
| 176 | - Migration notes |
| 177 | |
| 178 | **For data structure and examples**: See [references/content-architecture.md](references/content-architecture.md) |
| 179 | |
| 180 | --- |
| 181 | |
| 182 | ## Research Process |
| 183 | |
| 184 | ### Deep Competitor Research |
| 185 | |
| 186 | For each competitor, gather: |
| 187 | |
| 188 | 1. **Product research**: Sign up, use it, document features/UX/limitations |
| 189 | 2. **Pricing research**: Current pricing, what's included, hidden costs |
| 190 | 3. **Review mining**: G2, Capterra, TrustRadius for common praise/complaint themes |
| 191 | 4. **Customer feedback**: Talk to customers who switched (both directions) |
| 192 | 5. **Content research**: Their positioning, their comparison pages, their changelog |
| 193 | |
| 194 | ### Ongoing Updates |
| 195 | |
| 196 | - **Quarterly**: Verify pricing, check for major feature changes |
| 197 | - **When notified**: Customer mentions competitor change |
| 198 | - **Annually**: Full refresh of all competitor data |
| 199 | |
| 200 | --- |
| 201 | |
| 202 | ## SEO Considerations |
| 203 | |
| 204 | ### Keyword Targeting |
| 205 | |
| 206 | | Format | Primary Keywords | |
| 207 | |--------|-----------------| |
| 208 | | Alternative (singular) | [Competitor] alternative, alternative to [Competitor] | |
| 209 | | Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives | |
| 210 | | You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] | |
| 211 | | Competitor vs Competitor | [A] vs [B], [B] vs [A] | |
| 212 | |
| 213 | ### Internal Linking |
| 214 | - Link between related competitor pages |
| 215 | - Link from feature pages to relevant comparisons |
| 216 | - Create hub page linking to all competitor content |
| 217 | |
| 218 | ### Schema Markup |
| 219 | Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?" |
| 220 | |
| 221 | --- |
| 222 | |
| 223 | ## Output Format |
| 224 | |
| 225 | ### Competitor Data File |
| 226 | Complete competitor profile in YAML format for use across all comparison pages. |
| 227 | |
| 228 | ### Page Content |
| 229 | For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs. |
| 230 | |
| 231 | ### Page Set Plan |
| 232 | Recommended pages to create with priority order based on search volume. |
| 233 | |
| 234 | --- |
| 235 | |
| 236 | ## Task-Specific Questions |
| 237 | |
| 238 | 1. What are common reasons people switch to you? |
| 239 | 2. Do you have customer quotes about switching? |
| 240 | 3. What's your pricing vs. competitors? |
| 241 | 4. Do you offer migration support? |
| 242 | |
| 243 | --- |
| 244 | |
| 245 | ## Related Skills |
| 246 | |
| 247 | - **programmatic-seo**: For building competitor pages at scale |
| 248 | - **copywriting**: For writing compelling comparison copy |
| 249 | - **seo-audit**: For optimizing competitor pages |
| 250 | - **schema**: For FAQ and comparison schema |
| 251 | - **sales-enablement**: For internal sales collateral, decks, and objection docs |
Related
6 picksType
- seo-auditWhen the user wants to audit, review, or diagnose SEO issues on their site.Jul 2026
- marketing-psychologyWhen the user wants to apply psychological principles, mental models, or behavioral science to marketing.Jul 2026
- programmatic-seoWhen the user wants to create SEO-driven pages at scale using templates and data.Jul 2026
- marketing-ideasWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product.Jul 2026
- ai-seoWhen the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers.Jul 2026
- ad-creativeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…Jul 2026