skills/competitor-alternatives/SKILL.md
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.
npx skillsauth add coreyhaines31/marketingskills competitor-alternativesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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:
Your Product
Competitive Landscape
Goals
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:
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:
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
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 [You]"
Page structure:
Search intent: User comparing two competitors (not you directly)
URL pattern: /compare/[competitor-a]-vs-[competitor-b]
Page structure:
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
Be explicit about ideal customer for each option. Honest recommendations build trust.
Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
For detailed templates: See references/templates.md
Create a single source of truth for each competitor with:
For data structure and examples: See references/content-architecture.md
For each competitor, gather:
| Format | Primary Keywords | |--------|-----------------| | Alternative (singular) | [Competitor] alternative, alternative to [Competitor] | | Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives | | You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] | | Competitor vs Competitor | [A] vs [B], [B] vs [A] |
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Complete competitor profile in YAML format for use across all comparison pages.
For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
Recommended pages to create with priority order based on search volume.
tools
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.
tools
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
tools
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
data-ai
When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI. Also use when the user mentions 'influencer marketing,' 'creator partnerships,' 'sponsorships,' 'YouTube sponsorships,' 'podcast sponsorships,' 'brand ambassador,' 'ambassador program,' 'creator program,' 'UGC creators,' 'B2B influencers,' 'thought leader ads,' 'gifting,' 'product seeding,' 'whitelisting creator content,' 'how much to pay an influencer,' or 'FTC disclosure.' For affiliate/referral payout mechanics, see referrals. For community-led advocacy, see community-marketing. For turning creator content into paid ads, see ad-creative.