competitor-alternatives
by coreyhaines31competitor-alternatives helps teams create SEO-focused alternative and vs pages with clear structure, honest tradeoffs, and reusable templates. Includes guidance on the four page formats, key files to read, product marketing context checks, and practical workflow for consistent competitor comparison content.
This skill scores 82/100, which means it is a solid directory listing candidate for agents that need to create competitor comparison, alternative, and vs pages with more structure than a generic prompt. Repository evidence shows strong trigger language, substantial workflow content, reusable section templates, and evals that clarify expected behavior, though adoption would be easier with a tighter quick-start and more explicit execution steps.
- Highly triggerable: the description names many concrete phrases like "alternative page," "vs page," "battle card," and "[Product] alternative," making correct invocation easier.
- Good reusable leverage: the skill covers four page formats and is backed by reference docs for content architecture and section templates, not just a one-off prompt.
- Trust-building evidence: evals specify expected outputs such as checking product-marketing context first, using comparison sections, and positioning differentiators honestly.
- Operational flow is still somewhat document-heavy: structural signals show only limited explicit workflow guidance, so agents may need to infer sequencing from prose.
- No install command or runnable support files are provided, so directory users must rely on the markdown guidance rather than executable scaffolding.
Overview of competitor-alternatives skill
What competitor-alternatives skill does
The competitor-alternatives skill helps you create competitor comparison pages and alternative pages for SEO and sales enablement. It is designed for jobs like [Competitor] alternatives, [Your Product] vs [Competitor], [Competitor] vs [Competitor], and broader competitor comparison content that needs to rank, convert, and still feel credible.
Who this skill is best for
This skill fits product marketers, content marketers, founders, growth teams, and AI-assisted writers who need structured competitive content fast. It is especially useful if you already know your product position and want a repeatable framework instead of improvising every comparison page from scratch.
The real job to be done
Most teams do not need “a blog post about a competitor.” They need a page that helps evaluators make a decision, captures high-intent search traffic, and explains tradeoffs honestly enough to build trust. The competitor-alternatives skill is built around that practical outcome, not just keyword insertion.
What makes competitor-alternatives different
The main differentiator is structure. The skill covers four distinct page types, pushes you to check product marketing context first, and emphasizes honest strengths and weaknesses instead of shallow “we win everything” copy. It also includes references for scalable content architecture and section templates, which is useful if you need more than one page.
What users usually care about before installing
Before using competitor-alternatives, most users want to know:
- whether it works for SEO-oriented comparison pages
- whether it helps with actual page structure, not just messaging
- whether it can support many competitors consistently
- whether it is suitable for battle-card-style positioning without turning into obvious fluff
On those points, the skill is strong: it gives a clear trigger scope, practical page formats, and supporting reference docs that reduce guesswork.
When this skill is a poor fit
Skip competitor-alternatives if you only need a generic landing page, a pure sales battle card, or broad market research with no publishing goal. It is also not the best fit if you cannot provide real product differentiators, pricing context, or audience fit; without that, the output becomes generic no matter how good the framework is.
How to Use competitor-alternatives skill
competitor-alternatives install context
Install the skill from the repository with:
npx skills add https://github.com/coreyhaines31/marketingskills --skill competitor-alternatives
Because the skill lives inside a larger repository, the practical reading path matters more than a one-line install. After adding it, open the skill folder and review the files that shape how the workflow actually works.
Files to read first
Read these in this order:
skills/competitor-alternatives/SKILL.mdskills/competitor-alternatives/references/content-architecture.mdskills/competitor-alternatives/references/templates.mdskills/competitor-alternatives/evals/evals.json
That sequence gives you scope, scalable data design, section-level writing patterns, and concrete examples of what “good output” should include.
What input the skill needs
The competitor-alternatives skill works best when you provide:
- your product name and category
- target competitor or comparison keyword
- the page format you want
- your ideal customer profile
- key differentiators
- honest weaknesses and tradeoffs
- pricing context
- evidence or claims you can defend
If you leave out pricing, audience, or product tradeoffs, the page will usually read like generic positioning copy instead of a useful comparison.
The four page formats it supports
The skill explicitly covers four common formats:
- singular alternative page
- plural alternatives page
- your product vs competitor
- competitor vs competitor
This matters because structure changes by intent. A “best alternatives” page needs a broader comparison set and stronger “who it’s best for” framing, while a direct You vs Competitor page should go deeper on decision criteria.
Start by checking product marketing context
The repository instructs the agent to check for .agents/product-marketing-context.md or .claude/product-marketing-context.md first. This is one of the highest-value details in the skill because it reduces repetitive questioning and keeps the comparison aligned with your real positioning.
If your team uses this skill often, creating that context file is one of the fastest ways to improve consistency.
Turn a rough request into a strong prompt
Weak request:
Write an Asana alternatives page for us.
Stronger request:
Create a "Best Asana Alternatives" page for our project management tool. Our target audience is small teams of 5-20 people. We compete on simplicity and price: we are $8/user, while Asana is typically $24/user on the plan customers compare most often. Include a TL;DR, feature comparison, pricing comparison, who each option is best for, and honest cases where Asana is stronger.
Why this is better:
- it identifies the format
- it supplies audience and positioning
- it gives concrete pricing
- it asks for trust-building honesty
- it maps to the section patterns in the references and evals
Suggested workflow for competitor-alternatives usage
A practical workflow:
- Confirm the page format and target keyword.
- Load any product marketing context file.
- Gather your product facts and competitor facts.
- Draft the page structure before drafting copy.
- Write the TL;DR and comparison sections.
- Add pricing, feature, and “best for” guidance.
- Check honesty: where is the competitor genuinely better?
- Review against
evals/evals.jsonfor missing elements.
This sequence prevents the common failure mode of writing persuasive copy first and only later realizing the page lacks comparison depth.
Use the reference docs as production scaffolding
references/content-architecture.md is useful if you plan to create many comparison pages. It recommends centralized competitor data, which is the right move when you want consistency across dozens of pages.
references/templates.md is useful when your first draft feels too table-heavy or too fluffy. It pushes beyond simple checkmarks into explanatory paragraphs, pricing framing, support comparison, and “who it’s for” guidance.
What high-quality output should include
Based on the skill and evals, strong competitor-alternatives output usually includes:
- a scanner-friendly TL;DR
- clear comparison paragraphs, not only tables
- feature comparison with specifics
- pricing comparison with context
- “who it’s best for” guidance
- honest strengths and limitations on both sides
- positioning that matches the search intent of the page
If your draft skips these, it is underusing the skill.
Practical tips that change output quality
A few details materially improve results:
- Give one primary keyword, not a bundle of loosely related keywords.
- State the compared pricing tier, not just “we’re cheaper.”
- Name the customer segment precisely, such as “SMBs with 10-50 seats.”
- Include one or two cases where the competitor is genuinely better.
- Ask for modular sections so you can reuse or update them later.
These inputs make the output more credible and easier to maintain.
competitor-alternatives skill FAQ
Is competitor-alternatives for Competitive Analysis only?
No. The competitor-alternatives skill is for competitive content production, not just raw competitive analysis. It helps turn competitive inputs into publishable pages or enablement-style assets. If you only need internal research with no content output, another workflow may fit better.
Is this better than a normal prompt?
Usually, yes, if the task is comparison-page creation. A normal prompt can generate copy, but this skill gives clearer trigger conditions, page-type distinctions, reference structures, and evaluation examples. That means less drift and fewer missing sections.
Is competitor-alternatives beginner-friendly?
Yes, with one caveat: beginners can use it, but they still need real product and competitor facts. The framework is approachable; the hard part is not writing, it is bringing enough truthful input to produce a page that feels informed.
Does it support scalable programmatic content work?
Partly, yes. The strongest sign is references/content-architecture.md, which recommends centralized competitor profiles. If you plan to create many alternative or versus pages, that reference is one of the most useful assets in the skill.
When should I not use competitor-alternatives?
Do not use competitor-alternatives when:
- you need generic product copy
- you lack defensible comparison data
- the page is actually a category explainer, not a competitor page
- your team wants aggressive one-sided copy with no tradeoffs
The skill works best when trust and evaluator usefulness matter.
Does it help with SEO or only messaging?
It helps with both, but in a practical way. The skill is oriented around search-driven page types and the sections those pages need to satisfy evaluators. It is not a full technical SEO system; it is a content-structure and positioning aid for comparison intent.
How to Improve competitor-alternatives skill
Give competitor-alternatives sharper factual inputs
The fastest way to improve competitor-alternatives output is to provide more specific inputs:
- exact competitor name
- target keyword
- audience segment
- price points
- product strengths
- product weaknesses
- evidence-backed claims
Vague inputs create vague positioning. Sharp facts create pages that can actually persuade.
Add honest weaknesses for both sides
One of the best ideas in the skill is honesty. Lean into it. If you provide your own constraints and the competitor’s real advantages, the page becomes more believable and often more useful for buyers. It also prevents the lifeless tone common in AI-written comparison pages.
Build a reusable competitor data library
If you will use the competitor-alternatives skill more than once, create the centralized competitor records suggested in references/content-architecture.md. That reduces inconsistency across pages and makes updates easier when pricing, features, or positioning change.
Use evals to self-check before publishing
Open evals/evals.json and compare your output to the expected patterns. This is one of the most practical quality-control steps in the repository. It helps you catch missing pieces like:
- no TL;DR
- no pricing context
- no “best for” guidance
- weak differentiation
- failure to identify the correct page format
Strengthen prompts with output constraints
You will usually get better results if you specify expected sections and tone constraints up front. For example, ask the skill to:
- position your product prominently but not dishonestly
- include situations where the competitor wins
- avoid unsupported superlatives
- explain who each option is best for
That produces more decision-useful content than “write a competitor page.”
Common failure modes to watch for
The biggest failure modes are:
- generic claims with no supporting detail
- table-heavy pages with little explanation
- pretending all users should choose you
- mixing page formats
- comparing on features only and ignoring audience fit or pricing
Most of these are fixed by better inputs and by following the reference templates more closely.
Iterate after the first draft
After the first output, do not just edit wording. Ask for targeted improvements such as:
- stronger differentiation in the TL;DR
- clearer pricing framing
- more nuance in the “best for” section
- a fairer explanation of competitor strengths
- modular sections reusable across related pages
That kind of iteration improves usefulness more than surface-level polishing.
Pair the skill with your internal positioning docs
competitor-alternatives gets better when paired with product positioning, customer objections, and win-loss notes from your team. The repository already points toward a product marketing context file; use that idea seriously. It is the bridge between a good framework and a page that actually sounds like your company.