competitors guides an agent through creating comparison and alternative pages that rank for competitive search terms and help evaluators decide. It covers four page formats, the sections each needs, and a centralized competitor data file that every page draws from.
It also audits existing competitive assets. Each claim is re-checked, dated and marked current, changed, unverifiable or overclaimed, so a page never states more than the evidence supports.
What You Get
- Page structures for singular alternative, plural alternatives, you-vs-competitor and competitor-vs-competitor pages
- A competitor data file in YAML that holds positioning, pricing, strengths, weaknesses and migration notes in one place
- Page copy with URL, meta tags, comparison tables and calls to action
- A page set plan ordered by search volume
- An audit report that lists each competitor claim with its status and replacement wording
Common Use Cases
- Launching an X alternative page for the rival people most often switch from
- Checking old vs pages for pricing or feature claims that are now wrong
- Planning a set of comparison pages in priority order
- Writing a pricing comparison with a total cost for a sample team size
What Makes It Unique
Its evidence discipline treats a comparison page as a public claim about another company. A feature missing from a pricing page is written as not listed as of a date, motive is left out unless the rival stated it, and fact, interpretation and recommendation stay separate. A separate audit routine marks each existing claim as current, changed, unverifiable or overclaimed.
Under The Hood
The SKILL.md and two reference files (templates and content architecture) are loaded as context. It ships no scripts. When the agent can browse, the skill tells it to check competitor sites, docs, changelogs and review sites such as G2 and Capterra, and to re-verify claims against the current pages. Output is page copy and a YAML data file written by the agent into your project.