Competitor Alternatives
freekmurze/dotfiles
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
Install Competitor Alternatives
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills competitor-alternatives --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .claude/skills/competitor-alternatives && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .claude/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternativesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills competitor-alternatives --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .agents/skills/competitor-alternatives && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .agents/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills competitor-alternatives --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .cursor/skills/competitor-alternatives && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .cursor/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path marketing-skill/skills/competitor-alternatives--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills competitor-alternatives --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .gemini/skills/competitor-alternatives && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .gemini/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills competitor-alternativesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .github/skills/competitor-alternatives && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .github/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills competitor-alternatives --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing-skill/skills/competitor-alternatives .opencode/skills/competitor-alternatives && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "competitor-alternatives" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/competitor-alternatives into .opencode/skills/competitor-alternatives/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "competitor-alternatives", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
competitor-alternatives- GitHub stars
- 28k
- Used in
- 1 other repo
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,306 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
- Works in 4 steps: Honesty Builds Trust → Depth Over Surface → Help Them Decide → …
- Wants to create competitor comparison
- SKILL.md covers Initial Assessment, Core Principles, Page Formats and Essential Sections, plus 4 more sections
- Runs Python scripts from its folder; calls python3
What it does
Competitor Alternatives is an agent skill from alirezarezvani/claude-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,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and…
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/content-architecture.md`, `references/templates.md` and `scripts/comparison_matrix_builder.py`).
It sits in Marketing & SEO, covering Competitor analysis, Sales enablement and Landing pages. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Wants to create competitor comparison
- Alternative pages for SEO and sales enablement
- The user mentions alternative page
- Competitor comparison
Example prompts
- “alternative page,”
- “vs page,”
- “competitor comparison,”
- “/competitor-alternatives”
Requirements
- Python 3
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Competitor Alternatives loads about 2.8k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 145 tokens; SKILL.md has 1,306 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,306 words, ~2,784 tokens.
Download SKILL.mdSave it as
.claude/skills/competitor-alternatives/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- competitor-alternatives
- description
- 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,' 'switch from competitor,' or 'comparison content.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
- license
- MIT
- metadata.version
- 1.0.0
- metadata.author
- Alireza Rezvani
- metadata.category
- marketing
- metadata.updated
- 2026-03-06
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 .claude/product-marketing-context.md exists, 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.
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] |
Show full SKILL.md (519 more words)Show less
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?
Proactive Triggers
Proactively offer competitor page creation when:
- Competitor mentioned in conversation — Any time a specific competitor is named, ask if comparison or alternative pages exist; if not, offer to create a page set.
- Sales team friction — User mentions prospects comparing them to a specific tool; immediately offer a vs-page for sales enablement.
- SEO gap identified — Keyword research shows competitor-branded terms with no coverage; propose a full alternative page set with prioritized build order.
- Switcher testimonial available — When a customer quote about switching surfaces, offer to build a migration-focused alternative page around it.
- Pricing page review — When reviewing pricing, note that pricing comparison tables belong on dedicated competitor pages, not the pricing page itself.
Tools
| Tool | Invocation | Output |
|---|---|---|
| Comparison matrix builder | python3 scripts/comparison_matrix_builder.py --input competitors.json --markdown (no input = embedded demo; --json for pipelines) | Feature-by-feature comparison matrix ready to paste into the vs-page comparison table |
Feed it the Competitor Intelligence File data (features + pricing per competitor); its markdown output is the canonical comparison table for every Vs Page below — don't hand-build the table.
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| Competitor Intelligence File | YAML data file | Centralized competitor profile: pricing, features, weaknesses, review themes |
| Page Set Plan | Prioritized list | Ranked list of pages to build with target keywords and search volume estimates |
| Alternative Page (Singular) | Full page copy | Complete /[competitor]-alternative page with all sections |
| Vs Page | Full page copy | Complete /vs/[competitor] page with comparison table and CTA |
| Migration Guide Section | Markdown block | Reusable migration copy for inclusion across multiple pages |
Communication
All competitor page outputs should be factually accurate, legally safe (no false claims), and fair to competitors. Acknowledge genuine competitor strengths — pages that only disparage competitors lose credibility with evaluators. Reference marketing-context for ICP and positioning before writing any comparison copy. Quality bar: every claim must be verifiable from public sources or customer quotes.
Related Skills
- seo-audit — USE to validate that competitor pages meet on-page SEO requirements before publishing; NOT as a replacement for the keyword strategy built here.
- copywriting — USE for writing the narrative sections and CTAs on comparison pages; NOT when the task is purely competitor research and architecture.
- content-strategy — USE when planning a full competitive content program across multiple pages; NOT for single-page execution.
- competitive-intel — USE when C-level strategic competitive analysis is needed beyond page creation; NOT for tactical page writing.
- marketing-context — USE as foundation before any competitor page work to align positioning; always load first.
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in marketing-skill/skills/competitor-alternatives of alirezarezvani/claude-skills.
- SKILL.md
- references/content-architecture.md
- references/templates.md
- scripts/comparison_matrix_builder.py
Open the folder on GitHubat commit 19392f7
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Competitor Alternatives next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Competitor Alternatives this skillalirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Competitor Alternativesfreekmurze/dotfiles | 1k | 24 repos | ~2k | Automated safety check: Pass | None | |
| Competitorscoreyhaines31/marketingskills | 54k | — | ~3k | Automated safety check: Pass | MIT | |
| Competitor Teardownirinabuht12-oss/marketing-skills | 4k | — | ~1.6k | Automated safety check: Pass | None | |
| SEO Competitor Pagesseranking/seo-skills | 160 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Suede Competitor ProfilingJasonColapietro/suede-creator-skills | 127 | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Competitors
coreyhaines31/marketingskills
When the user wants to create competitor comparison or alternative pages for SEO and buyer-facing use.
Competitor Teardown
irinabuht12-oss/marketing-skills
Systematic competitive analysis covering positioning, messaging hierarchy, objection handling, and CTA strategy from landing page URLs or screenshots.
SEO Competitor Pages
seranking/seo-skills
Generate SEO-optimized "X vs Y" comparison and "alternatives to X" landing pages targeting comparative-intent keywords.
Suede Competitor Profiling
JasonColapietro/suede-creator-skills
Suede-owned competitive-intelligence discipline for evidence-backed profiles of positioning, pricing, messaging, product, proof, and public-market signals.
Suede Competitors
JasonColapietro/suede-creator-skills
Suede-owned comparison-page discipline for accurate, evidence-backed alternative, versus, and competitor-comparison content that wins evaluators and search intent.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Competitor Alternatives
What does Competitor Alternatives do?
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Competitor Alternatives is an agent skill from alirezarezvani/claude-skills. When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
When should I use Competitor Alternatives?
Competitor Alternatives fits situations like: wants to create competitor comparison; alternative pages for SEO and sales enablement; the user mentions alternative page; competitor comparison.
How do I install Competitor Alternatives in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a claude-code`. Or copy the skill folder (marketing-skill/skills/competitor-alternatives in alirezarezvani/claude-skills) into .claude/skills/competitor-alternatives in your project. Claude Code loads it when a task matches its description.
How do I install Competitor Alternatives in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a codex`. Or copy the skill folder (marketing-skill/skills/competitor-alternatives in alirezarezvani/claude-skills) into .agents/skills/competitor-alternatives in your project. Codex loads it when a task matches its description.
Can I use Competitor Alternatives in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill competitor-alternatives -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/competitor-alternatives, .gemini/skills/competitor-alternatives, .github/skills/competitor-alternatives and .opencode/skills/competitor-alternatives in your project.
What does Competitor Alternatives need to run?
Going by SKILL.md and its folder, Competitor Alternatives needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Competitor Alternatives access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Competitor Alternatives safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Competitor Alternatives use?
Competitor Alternatives is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Competitor Alternatives use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.
What are the alternatives to Competitor Alternatives?
Skills that share tags, products or a category with Competitor Alternatives: Competitor Alternatives (freekmurze/dotfiles, 1k stars), Competitors (coreyhaines31/marketingskills, 54k stars), Competitor Teardown (irinabuht12-oss/marketing-skills, 4k stars) and SEO Competitor Pages (seranking/seo-skills, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Competitor Alternatives?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,891 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.