competitors
Skill870 starsChanged 3 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
11 rules. 10 are common, 0 are distinctive, and 1 is very specific to this project.
10
Common
Most of the 12 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Common: line 17
Before creating competitor pages, understand:
- Common: line 30
Search volume for competitor terms
- Common: line 45
Don't misrepresent competitor features
- Common: line 152
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
- Common: line 176
Create a single source of truth for each competitor with:
- Common: line 203
Quarterly: Verify pricing, check for major feature changes
- Common: line 223
Create hub page linking to all competitor content
- Common: line 226
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
- Common: line 246
Do you have customer quotes about switching?
- Common: line 248
Do you offer migration support?
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitor & Alternative Pages
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.
Initial Assessment
Check for product marketing context first:
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.
Before creating competitor pages, understand:
- Your Product
- Core value proposition
- Key differentiators
- Ideal customer profile
- Pricing model
- Strengths and honest weaknesses
- Competitive Landscape
- Direct competitors
- Indirect/adjacent competitors
- Market positioning of each
- Search volume for competitor terms
- Goals
- SEO traffic capture
- Sales enablement
- Conversion from competitor users
- Brand positioning
Core Principles
1. Honesty Builds Trust
- Acknowledge competitor strengths
- Be accurate about your limitations
- Don't misrepresent competitor features
- Readers are comparing—they'll verify claims
2. Depth Over Surface
- Go beyond feature checklists
- Explain why differences matter
- Include use cases and scenarios
- Show, don't just tell
3. Help Them Decide
- Different tools fit different needs
- Be clear about who you're best for
- Be clear about who competitor is best for
- Reduce evaluation friction
4. Modular Content Architecture
- Competitor data should be centralized
- Updates propagate to all pages
- Single source of truth per competitor
Page Formats
Format 1: [Competitor] Alternative (Singular)
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:
- Why people look for alternatives (validate their pain)
- Summary: You as the alternative (quick positioning)
- Detailed comparison (features, service, pricing)
- Who should switch (and who shouldn't)
- Migration path
- Social proof from switchers
- CTA
Format 2: [Competitor] Alternatives (Plural)
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:
- Why people look for alternatives (common pain points)
- What to look for in an alternative (criteria framework)
- List of alternatives (you first, but include real options)
- Comparison table (summary)
- Detailed breakdown of each alternative
- Recommendation by use case
- CTA
Important: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
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.
Format 3: You vs [Competitor]
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:
- TL;DR summary (key differences in 2-3 sentences)
- At-a-glance comparison table
- Detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations)
- Who [You] is best for
- Who [Competitor] is best for (be honest)
- What customers say (testimonials from switchers)
- Migration support
- CTA
Format 4: [Competitor A] vs [Competitor B]
Search intent: User comparing two competitors (not you directly)
URL pattern: /compare/[competitor-a]-vs-[competitor-b]
Page structure:
- Overview of both products
- Comparison by category
- Who each is best for
- The third option (introduce yourself)
- Comparison table (all three)
- CTA
Why this works: Captures search traffic for competitor terms, positions you as knowledgeable.
Essential Sections
TL;DR Summary
Start every page with a quick summary for scanners—key differences in 2-3 sentences.
Paragraph Comparisons
Go beyond tables. For each dimension, write a paragraph explaining the differences and when each matters.
Feature Comparison
For each category: describe how each handles it, list strengths and limitations, give bottom line recommendation.
Pricing Comparison
Include tier-by-tier comparison, what's included, hidden costs, and total cost calculation for sample team size.
Who It's For
Be explicit about ideal customer for each option. Honest recommendations build trust.
Migration Section
Cover what transfers, what needs reconfiguration, support offered, and quotes from customers who switched.
For detailed templates: See references/templates.md
Content Architecture
Centralized Competitor Data
Create a single source of truth for each competitor with:
- Positioning and target audience
- Pricing (all tiers)
- Feature ratings
- Strengths and weaknesses
- Best for / not ideal for
- Common complaints (from reviews)
- Migration notes
For data structure and examples: See references/content-architecture.md
Research Process
Deep Competitor Research
For each competitor, gather:
- Product research: Sign up, use it, document features/UX/limitations
- Pricing research: Current pricing, what's included, hidden costs
- Review mining: G2, Capterra, TrustRadius for common praise/complaint themes
- Customer feedback: Talk to customers who switched (both directions)
- Content research: Their positioning, their comparison pages, their changelog
Ongoing Updates
- Quarterly: Verify pricing, check for major feature changes
- When notified: Customer mentions competitor change
- Annually: Full refresh of all competitor data
SEO Considerations
Keyword Targeting
| 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] |
Internal Linking
- Link between related competitor pages
- Link from feature pages to relevant comparisons
- Create hub page linking to all competitor content
Schema Markup
Consider FAQ schema for common questions like "What is the best alternative to [Competitor]?"
Output Format
Competitor Data File
Complete competitor profile in YAML format for use across all comparison pages.
Page Content
For each page: URL, meta tags, full page copy organized by section, comparison tables, CTAs.
Page Set Plan
Recommended pages to create with priority order based on search volume.
Task-Specific Questions
- What are common reasons people switch to you?
- Do you have customer quotes about switching?
- What's your pricing vs. competitors?
- Do you offer migration support?
Related Skills
- programmatic-seo: For building competitor pages at scale
- copywriting: For writing compelling comparison copy
- seo-audit: For optimizing competitor pages
- schema: For FAQ and comparison schema
- sales-enablement: For internal sales collateral, decks, and objection docs
Other versions30 projects use a version of this.
Word for word · 13
- open-fox/agents★ 55100% same
- TommyBez/skillsboard★ 10100% same
- agrivisionai/claude-skills★ 1100% same
- ngothanhtung/claude-code-skills★ 1100% same
- patinaproject/skills★ 1100% same
- productionx-in/Core-Skills★ 1100% same
- xeroc/skills★ 1100% same
- chaakresh/claude-skills★ 0100% same
- claude1cryptwareinfotech-star/Claude-Skill★ 0100% same
- FelipeCVelame/claude-skills★ 0100% same
3 more not listed
Edited · 11
- coreyhaines31/marketingskills★ 58k66% same
- Cesarjoquin/Marketing-Skills★ 19099% same
- SZcalligrapher/slash-skills-subscription★ 3299% same
- anis-dr/skills★ 366% same
- Shri-Phnx/claude-skills★ 230% same
- AayanHetam/chess-coach-ai★ 099% same
- AbdelrhmanAlquran/claude-skills★ 099% same
- Gopyr/gopyr-skills-hub★ 080% same
- itaymizzz/claude-skills★ 099% same
- masterpeteworld/claude-skills★ 066% same
1 more not listed
Wrote their own version · 6
- LOGIN-TB/claude-skills★ 80same name
- scayver/marketing-skills★ 8same name
- aya-taleb/biz-ready-skills★ 1same name
- david-corroy/skills-marketing-fr★ 1same name
- LOGIN-TB/hermes-toolbox★ 1same name
- marcus-at-localhost/market-context-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use events, remotion-best-practices and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
agenkinSkillevents
Schema discovery — list every event name firing for the current TelemetryDeck app with 7-day and 30-day counts side by side.
Also in 4 projects that use this
VercelSkillremotion-best-practices
Best practices for Remotion - Video creation in React
Also in 4 projects that use this
VercelSkillemil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 6 projects that use this
JetBrainsSkillbrand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Also in 3 projects that use this
In this repository30 other files it gives its agents.
- AGENTS.MDAGENTS.md
- ai-seoSkill
- analyticsSkill
- attributionSkill
- churn-preventionSkill
- co-marketingSkill
- community-marketingSkill
- competitor-profilingSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- croSkill
- customer-researchSkill
- imageSkill
- influencer-marketingSkill
- launchSkill
- marketing-councilSkill
- marketing-ideasSkill
- marketing-loopsSkill
- marketing-planSkill
- marketing-psychologySkill
- offersSkill
- onboardingSkill
- pricingSkill
- product-marketingSkill
- programmatic-seoSkill
- seo-auditSkill
- seoSkill
- site-architectureSkill
- videoSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

