$npx -y skills add MoizIbnYousaf/marketing-cli --skill competitor-alternativesCreates high-converting 'X vs Y' and 'X alternatives' SEO pages that capture comparison search traffic. Researches competitors, writes honest comparison content, and adds schema markup (FAQPage, ItemList). Use when someone needs alternatives pages, comparison content, or says 'al
| 1 | # Competitor Alternatives Pages |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | People searching "[Competitor] alternatives" or "[Product] vs [Competitor]" have high purchase intent. They already know the category — they're choosing. This skill captures that traffic with structured comparison content that ranks and converts. |
| 6 | |
| 7 | ## On Activation |
| 8 | |
| 9 | 1. Read `brand/` directory: load `competitors.md`, `positioning.md`, `voice-profile.md`, `audience.md` if present. |
| 10 | 2. Show what loaded: |
| 11 | ``` |
| 12 | Brand context loaded: |
| 13 | ├── Competitors ✓/✗ ({N} competitors profiled) |
| 14 | ├── Positioning ✓/✗ ("{primary angle}") |
| 15 | ├── Voice Profile ✓/✗ |
| 16 | └── Audience ✓/✗ |
| 17 | ``` |
| 18 | 3. If `competitors.md` is missing: suggest running `/competitive-intel` first, or ask user to provide competitor names, pricing, and key differentiators. |
| 19 | 4. If `positioning.md` is missing: ask for the product's primary value prop and target audience. |
| 20 | 5. Ask which competitors to create pages for (or "all" from competitors.md). |
| 21 | 6. Read `brand/landscape.md` if it exists — check the Claims Blacklist before making ecosystem or competitive claims. If stale (>14 days) or missing, warn that market claims may be outdated. |
| 22 | |
| 23 | ## Reads |
| 24 | |
| 25 | - `brand/competitors.md` — Known competitors, their positioning, pricing, weaknesses |
| 26 | - `brand/positioning.md` — Your product's unique value props, differentiators, target audience |
| 27 | - `brand/voice-profile.md` — Tone for comparison copy |
| 28 | - `brand/audience.md` — Who is choosing between you and competitors |
| 29 | |
| 30 | ## Depends On |
| 31 | |
| 32 | - `competitive-intel` — Should have competitor research completed first (not hard-blocked — can proceed with user-provided data) |
| 33 | |
| 34 | ## Workflow |
| 35 | |
| 36 | ### Step 1: Identify Comparison Queries |
| 37 | |
| 38 | Pull from `competitors.md` and generate the full keyword set: |
| 39 | |
| 40 | - `[competitor] alternatives` (highest volume) |
| 41 | - `[competitor] vs [your product]` (branded) |
| 42 | - `[your product] vs [competitor]` (branded reverse) |
| 43 | - `best [category] tools` (category) |
| 44 | - `[competitor] review` (review intent) |
| 45 | - `[competitor] pricing` (price-sensitive) |
| 46 | |
| 47 | Prioritize by: search volume estimate > purchase intent > your win rate against that competitor. |
| 48 | |
| 49 | ### If Web Search Is Unavailable |
| 50 | |
| 51 | Use data from brand/competitors.md if it exists. Ask the user directly for: competitor pricing, key strengths/weaknesses, and notable reviews or complaints they've seen. Note limitation: 'Competitor data is based on provided context, not live research. Verify current pricing and features before publishing.' |
| 52 | |
| 53 | ### Step 2: Research Each Competitor |
| 54 | |
| 55 | For each competitor page, gather: |
| 56 | |
| 57 | - **Core product** — What they actually do (one sentence) |
| 58 | - **Pricing** — Free tier, paid plans, enterprise |
| 59 | - **Strengths** — 3-5 genuine strengths (be honest, builds credibility) |
| 60 | - **Weaknesses** — 3-5 real weaknesses (factual, not snarky) |
| 61 | - **Best for** — Their ideal customer profile |
| 62 | - **Not ideal for** — Where they fall short (your opportunity) |
| 63 | - **Key reviews** — G2, Capterra, Reddit sentiment summary |
| 64 | |
| 65 | ### Step 3: Write the Comparison Page |
| 66 | |
| 67 | Structure for each page: |
| 68 | |
| 69 | ```markdown |
| 70 | --- |
| 71 | title: "[Competitor] vs [Your Product]: Honest Comparison [Year]" |
| 72 | description: "Comparing [Competitor] and [Your Product] on features, pricing, and ease of use. See which is right for your needs." |
| 73 | slug: /compare/[competitor]-vs-[your-product] |
| 74 | schema: ComparisonPage |
| 75 | --- |
| 76 | |
| 77 | ## TL;DR |
| 78 | |
| 79 | [2-3 sentence verdict. Be specific about WHO should pick which tool.] |
| 80 | |
| 81 | ## Quick Comparison |
| 82 | |
| 83 | | Feature | [Your Product] | [Competitor] | |
| 84 | |---------|---------------|--------------| |
| 85 | | [Feature 1] | [Status/Detail] | [Status/Detail] | |
| 86 | | [Feature 2] | [Status/Detail] | [Status/Detail] | |
| 87 | | Pricing starts at | $X/mo | $Y/mo | |
| 88 | | Free tier | Yes/No | Yes/No | |
| 89 | | Best for | [Audience] | [Audience] | |
| 90 | |
| 91 | ## [Your Product] Overview |
| 92 | [2-3 paragraphs. Lead with your strong |