csh/playbook
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

📦 deps(thirdparty): update snapshots

Browse Source
This commit is contained in:
ci[bot]
2026-07-01 16:02:41 +00:00
parent 8301f01888
commit c824ba9d7b
2449 changed files with 555104 additions and 9259 deletions
Download Patch File Download Diff File Expand all files Collapse all files
antigravity-awesome-skills/skills/alternatives-pages/README.md
+46
View File
@@ -0,0 +1,46 @@
# Alternatives Pages
Create "[Competitor] alternative" and comparison pages for developer tools that rank for competitive keywords and convert developers honestly.
## What This Skill Covers
- SEO research for alternative and comparison keywords
- Page structure that converts without being sleazy
- Building honest, verifiable comparison tables
- Migration content and addressing switching concerns
- When to name competitors vs stay general
- Legal considerations for competitive content
- Ongoing content maintenance
## Recommended Tools
- **Social listening tools** — Monitor competitor conversations and developer pain points
- **SEO tools** (Ahrefs, Semrush) — Keyword research and search volume
## Quick Start
1. Research competitor pain points and comparison patterns using social listening
2. Prioritize pages based on search volume and competitive overlap
3. Create honest, detailed comparison content
4. Include migration guidance and support
5. Set up monitoring for content freshness triggers
6. Establish quarterly review cadence
## Page Types
**Alternatives pages:** "[Competitor] Alternative" - Target developers looking to switch
**Comparison pages:** "[You] vs [Them]" - Target developers actively evaluating
**Category pages:** "Best [Category] Tools" - Target category researchers
## Key Principles
- Be honest - developers fact-check everything
- Be helpful - even if they don't choose you
- Be specific - vague comparisons waste time
- Be current - date comparisons and keep them fresh
## Related Skills
- competitor-tracking
- developer-listening
- seo-for-devtools
antigravity-awesome-skills/skills/alternatives-pages/SKILL.md
+376
View File
@@ -0,0 +1,376 @@
---
name: alternatives-pages
description: 'Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor comparison",...'
risk: unknown
source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/alternatives-pages
source_repo: jonathimer/devmarketing-skills
source_type: community
date_added: 2026-07-01
license: MIT
license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
---
# Alternatives Pages
## When to Use
Use this skill when you need create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor comparison",...
Create effective "[Competitor] alternative" and comparison pages that rank for competitive keywords, convert developers honestly, and support your competitive positioning.
## Overview
Alternatives pages and comparison content are high-intent SEO plays. Developers searching for "[competitor] alternative" or "[your product] vs [competitor]" are actively evaluating solutions. Done well, this content captures demand, educates prospects, and positions your product effectively. Done poorly, it damages trust and brand perception.
The key principles:
- Be honest - developers will fact-check you
- Be helpful - even if they don't choose you
- Be specific - vague comparisons waste everyone's time
- Be current - outdated comparisons are worse than none
## SEO Research for Competitive Keywords
### Keyword Categories
**Alternative keywords:**
- "[Competitor] alternative"
- "[Competitor] alternatives"
- "Alternative to [competitor]"
- "Best [competitor] alternatives"
- "[Competitor] replacement"
**Comparison keywords:**
- "[Competitor] vs [your product]"
- "[Your product] vs [competitor]"
- "[Competitor] vs [other competitor]" (consider if you should play here)
- "[Competitor] comparison"
- "Compare [category] tools"
**Migration keywords:**
- "Migrate from [competitor]"
- "Switch from [competitor]"
- "[Competitor] to [your product]"
- "Moving away from [competitor]"
**Problem-aware keywords:**
- "[Competitor] pricing too expensive"
- "[Competitor] limitations"
- "[Competitor] [specific problem]"
- "Frustrated with [competitor]"
### Research Developer Conversations
Use social listening tools to identify which competitive keywords have real search intent based on developer conversations. Search for:
- "[competitor] alternative" or "alternative to [competitor]"
- "[competitor] vs"
- Negative sentiment mentions of competitors
Look for patterns in:
- Which competitors developers frequently compare
- What problems drive people away from competitors
- What features developers ask about when evaluating
- Migration concerns and blockers
### Prioritizing Which Pages to Create
**High priority:**
- Direct competitors with significant search volume
- Competitors you frequently encounter in deals
- Competitors developers organically compare you to
**Medium priority:**
- Indirect competitors in adjacent categories
- Competitors you can clearly beat on specific use cases
**Lower priority:**
- Competitors in different market segments
- Competitors with minimal overlap
## Page Structure That Converts
### Alternatives Page Structure
**1. Hero Section**
- Clear headline: "[Your product]: A [Competitor] Alternative for [Use Case]"
- One-sentence value proposition
- Quick social proof (logos, stats)
- Primary CTA
**2. Why Developers Switch Section**
- Common pain points with competitor (from social listening research)
- Be specific and factual, not snarky
- Cite real developer feedback when possible
**3. Key Differences Section**
- 3-5 major differentiators
- Focus on things that matter to your ICP
- Be honest about where you're similar or worse
**4. Comparison Table**
- Feature-by-feature comparison
- Include pricing comparison
- Honest checkmarks (don't claim features you don't have)
- Date the comparison ("Last updated: [date]")
**5. Migration Section**
- How hard is it to switch?
- Migration guide or resources
- Data portability information
- Support available during migration
**6. Social Proof**
- Case studies from companies who switched
- Testimonials mentioning the switch
- Quantified results if available
**7. FAQ Section**
- Address common concerns
- SEO opportunity for long-tail keywords
- Objection handling
**8. CTA Section**
- Primary: Start trial/demo
- Secondary: Migration guide, comparison deep-dive
### Comparison Page Structure (You vs Them)
**1. Hero**
- "[Your Product] vs [Competitor]: [Key Differentiator]"
- Neutral, informative tone
- Both logos (don't be weird about it)
**2. Quick Comparison**
- At-a-glance summary for scanners
- 3-4 key differences highlighted
- Who each product is best for
**3. Detailed Comparison Table**
- Comprehensive feature comparison
- Categorize features logically
- Include pricing
- Include subjective but fair assessments
**4. Detailed Analysis Sections**
- Deep dive on major difference areas
- Use cases where each excels
- Developer experience comparison
**5. Migration Information**
- If relevant, how to switch between them
- Bidirectional if you want to seem fair
**6. Verdict/Recommendation**
- "Choose [Your Product] if..."
- "Choose [Competitor] if..."
- Be honest about competitor's strengths
## Honest Comparison Tables
### Table Best Practices
**Do:**
- Include features you don't have that competitor does
- Use nuanced indicators (full support, partial, beta, not available)
- Date your comparison prominently
- Link to sources/docs for verification
- Include pricing transparency
**Don't:**
- Cherry-pick only features you win on
- Use misleading indicators
- Ignore major competitor features
- Let comparisons get stale
### Comparison Indicators
Instead of simple checkmarks:
- "Full support" / "Partial" / "Beta" / "Roadmap" / "Not available"
- Include hover/click for details
- Link to relevant documentation
### Handling Subjective Comparisons
Some comparisons are subjective (developer experience, ease of use). Handle these by:
- Being explicit that it's subjective
- Citing external sources when possible
- Inviting developers to evaluate themselves
- Including quotes from developers who've used both
## Addressing Migration
### Migration Content Types
**Migration guide:**
- Step-by-step technical guide
- Data export from competitor
- Data import to your product
- Configuration mapping
- Testing and validation
**Migration assessment:**
- Help developers evaluate effort
- What migrates easily vs needs work
- Timeline expectations
- Support available
**Migration support offer:**
- Dedicated migration help
- Data import services
- Onboarding assistance
### Migration Concerns to Address
Common developer concerns when switching:
- How much work is the migration?
- Will I lose data or history?
- What's the learning curve?
- Can I migrate incrementally?
- What if the migration fails?
- Is there a rollback option?
## When to Name Competitors vs Stay General
### Name Competitors When:
- They're well-known and developers search for them
- You have a clear, honest differentiator
- You can be specific about differences
- You're prepared to keep the content updated
- You have permission to use their trademark fairly
### Stay General When:
- Competitor is much smaller (looks petty)
- Your comparison would be dishonest
- You'd rather own the category than specific comparisons
- Legal concerns about trademark usage
- The market is too fragmented to name everyone
### General Alternative Content
"Best [Category] Tools" type content:
- Position yourself within the category
- Compare multiple options including yourself
- Be genuinely helpful in evaluation
- Let your product stand on its merits
## Legal Considerations
### Trademark Usage
**Generally acceptable:**
- Using competitor names in factual comparisons
- "[Competitor] alternative" type phrases
- Accurate feature comparisons
**Avoid:**
- Using competitor logos without permission (grey area)
- Implying endorsement or partnership
- Making false claims about competitors
- Trademark usage in domains (usually problematic)
- Competitive keyword bidding on brand terms (policy varies)
### Defamation and False Claims
- All claims must be factually accurate
- Document sources for claims
- Date comparisons and keep them updated
- When in doubt, be more generous to competitor
### Consult Legal When:
- Making any claims that could be seen as disparaging
- Using competitor visual assets
- Creating comparison advertising
- Competitor has sent C&D or complained
## Research for Competitive Content
### Research Phase
Use social listening tools to research:
- **Developer pain points:** Negative sentiment mentions of competitors
- **Common comparisons:** "[competitor] vs" or "compare [competitor]"
- **Migration conversations:** "switch from [competitor]" or "migrate from [competitor]"
### Validation Phase
Before publishing, verify:
- Your differentiators resonate in real conversations
- You've addressed common misconceptions
- Your claims are factually accurate
### Ongoing Monitoring
Set up alerts to track:
- Comparison conversations mentioning your product vs competitor
- Competitor announcements that might require content updates
## Content Maintenance
### Update Triggers
- Competitor launches major feature
- Your product launches relevant feature
- Competitor changes pricing
- Industry/category shifts
- Quarterly review regardless
### Update Process
1. Review all claims for accuracy
2. Update comparison tables
3. Refresh screenshots if used
4. Update "last updated" date
5. Re-check SEO optimization
6. Update internal links
### Deprecation
When competitors become irrelevant:
- Don't delete (keep URL equity)
- Add notice: "This comparison may be outdated"
- Consider redirecting to category page
## Tools
### Research Queries
Use social listening tools to set up searches for:
- Competitor pain points: [competitor] + negative sentiment
- Comparison intent: "[competitor] vs"
- Migration signals: "alternative OR migrate OR switch" + competitor name
- Your comparison pages in conversations
### Other Tools
**SEO Tools:**
- Keyword research for search volume
- Competitor page ranking analysis
- Backlink analysis for competitor comparison pages
**Archive.org:**
- Research competitor historical positioning
- Track competitor feature launches for timeline
**Testimonial Sources:**
- G2, Capterra reviews for switching stories
- Twitter for public praise after switching
- Case study interviews
## Related Skills
- **competitor-tracking** - Ongoing competitive intelligence
- **developer-listening** - Understanding developer sentiment
- **seo-for-devtools** - SEO optimization for technical content
- **landing-pages** - Conversion optimization for comparison pages
## Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.