SEO Competitor Comparison Pages
AgriciDaniel/claude-seo
Generates X vs Y comparison pages, alternatives-to-X pages, best-tools roundups and feature-matrix tables, with schema markup and verifiable data rules.
Create or update objective website comparison pages and head-to-head pages from the comparison canon.
Install Comparison Page
$ npx skills add debuglebowski/slayzone --skill comparison-page -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install debuglebowski/slayzone comparison-page --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/debuglebowski/slayzone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/comparison-page .claude/skills/comparison-page && 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 "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .claude/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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/debuglebowski/slayzone/tree/main/.agents/skills/comparison-pageType 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 debuglebowski/slayzone --skill comparison-page -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install debuglebowski/slayzone comparison-page --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/comparison-page .agents/skills/comparison-page && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .agents/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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 debuglebowski/slayzone --skill comparison-page -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install debuglebowski/slayzone comparison-page --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/comparison-page .cursor/skills/comparison-page && 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 "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .cursor/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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/debuglebowski/slayzone.git --path .agents/skills/comparison-page--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 debuglebowski/slayzone --skill comparison-page -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install debuglebowski/slayzone comparison-page --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/comparison-page .gemini/skills/comparison-page && 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 "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .gemini/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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 debuglebowski/slayzone comparison-pageInstalls 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 debuglebowski/slayzone --skill comparison-page -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/comparison-page .github/skills/comparison-page && 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 "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .github/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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 debuglebowski/slayzone --skill comparison-page -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install debuglebowski/slayzone comparison-page --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/debuglebowski/slayzone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/comparison-page .opencode/skills/comparison-page && 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 "comparison-page" agent skill from https://github.com/debuglebowski/slayzone/tree/main/.agents/skills/comparison-page into .opencode/skills/comparison-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "comparison-page", 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
comparison-page- GitHub stars
- 191
- Token cost
- ~1.2k tokens
- SKILL.md length
- 637 words
- Files
- 1
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Create or update objective website comparison pages and head-to-head pages from the comparison canon.
- Works in 5 steps: Title card with → Pick SlayZone if... and Pick if... → One section per product → …
- SlayZone vs competitor pages with quick verdict
- SKILL.md covers Load First, Non-Negotiables, Required Page Structure and Writing Rules, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Comparison Page is an agent skill from debuglebowski/slayzone. Create or update objective website comparison pages and head-to-head pages from the comparison canon. Use for SlayZone vs competitor pages with quick verdict, last-checked freshness, top-of-page side-by-side screenshots, pick-X-if blocks, balanced strengths/weaknesses for both products, an at-a-glance feature table, and a full matrix below.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Programmatic SEO and Competitor analysis. The licence is GPL-3.0.
When your agent uses it
- SlayZone vs competitor pages with quick verdict
- Last-checked freshness
- Top-of-page side-by-side screenshots
- Pick-X-if blocks
Example prompts
- “/comparison-page”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Title card with
- Pick SlayZone if... and Pick if...
- One section per product
- At-a-glance table
- Full matrix table
What it can do on your machine
Read from SKILL.md and the folder at commit e912716. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Comparison Page loads about 1.2k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 637 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from debuglebowski/slayzone at commit e912716, republished under its GPL-3.0 licence (© debuglebowski). 637 words, ~1,247 tokens.
Download SKILL.mdSave it as
.claude/skills/comparison-page/SKILL.md (or your agent's skills folder).- name
- comparison-page
- description
- Create or update objective website comparison pages and head-to-head pages from the comparison canon. Use for SlayZone vs competitor pages with quick verdict, last-checked freshness, top-of-page side-by-side screenshots, pick-X-if blocks, balanced strengths/weaknesses for both products, an at-a-glance feature table, and a full matrix below.
- trigger
- auto
Create or update objective public comparison pages.
Use this skill when task is to build, revise, or refresh a website comparison page or head-to-head page such as SlayZone vs Superset.sh.
Load First
- Read
comparison/COMPETITOR_GUIDE.md. - Read relevant canonical competitor folder in
comparison/<slug>/. - Read current website comparison implementation in
website/src/pages/andwebsite/src/components/comparison/. - Read existing SlayZone website copy for claims that need to be stated about SlayZone.
Only use comparison/_legacy/ if canonical record does not exist and user explicitly accepts stopgap output.
Non-Negotiables
- page is comparison, not sales page
- treat both products as capable tools with real tradeoffs
- always name strengths and weaknesses of both sides
- never assume SlayZone wins every axis
- if competitor is stronger on an axis, say so plainly
- if SlayZone is weaker or unclear, say so plainly
- use structured canon fields for table truth
- do not invent facts from prose vibes
- if evidence is weak, say
unknown, lower confidence, or surface gap
Required Page Structure
Build page in this order unless user explicitly overrides:
- Title card with:
- page title
- side-by-side screenshots at top: one SlayZone, one competitor
Last checkedfreshness near top- quick verdict
Pick SlayZone if...andPick <competitor> if...- One section per product:
- what it is
- core strengths
- core weaknesses
- At-a-glance table:
- short, high-signal subset of rows
- include jump link to full matrix if page supports anchor links
- Full matrix table:
- broader axis coverage
- same truth source as at-a-glance table
Do not create separate mid-page "visual proof" section. Visual comparison belongs at top.
Writing Rules
- quick verdict must be balanced, short, evidence-backed
- avoid loaded winner language like "obliterates", "crushes", "obviously better"
- prefer "best if", "stronger when", "weaker on", "better fit for"
- keep product descriptions symmetrical in ambition and scrutiny
- do not hide ugly facts for either side
- call out architectural differences, not only feature checklist differences
- distinguish:
- verified facts
- structured axis verdicts
- editorial recommendation
Visual Rules
- top visuals must compare like-with-like as much as possible
- give both screenshots similar weight and framing
- captions should clarify what each screenshot demonstrates
- visuals support orientation; they do not carry factual burden alone
- if one side lacks a good screenshot, say so and avoid fake symmetry
Show full SKILL.md (277 more words)Show less
Freshness Rules
- always show
Last checked - if page depends on multiple freshness dates, do not collapse them into misleading single date
- prefer:
- one date if both sides were checked together
- two explicit dates if freshness differs materially
- if canon is stale, surface that before publishing confident claims
Table Rules
- at-a-glance table = decisive subset of full matrix, not separate truth
- full matrix rows must map to explicit structured axes or equally explicit website-side constants
- use consistent verdict vocabulary across page
- row labels should be concrete and comparable
- notes should explain why row matters, not repeat product marketing
- if two products are both strong on row, show that; do not force artificial differentiation
Workflow
- Read competitor canon and current website implementation.
- Build fact baseline for both products.
- Pick 5-8 decisive rows for at-a-glance table.
- Build full matrix from structured axes.
- Draft balanced quick verdict.
- Draft
Pick X if...blocks from fit, not hype. - Write one neutral strengths/weaknesses section per product.
- Place screenshots in hero/title card.
- Verify tables, freshness labels, and verdict language stay consistent.
- Build/test page on desktop and mobile.
Stop Conditions
Pause and call out gap when:
- competitor canon is stale or missing key axes
- SlayZone claim is not grounded in current site/product truth
- screenshots are missing for one side and user has not approved asymmetric fallback
- quick verdict starts sounding like ad copy
- at-a-glance rows disagree with full matrix truth
Output Goal
Ship page that helps reader decide which product fits them.
Reader should leave understanding:
- what each product is for
- where each product is stronger
- where each product is weaker
- which one fits their workflow better
© debuglebowski, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/comparison-page of debuglebowski/slayzone.
Open the folder on GitHubat commit e912716
Compare with similar skills
Comparison Page 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 |
|---|---|---|---|---|---|---|
| Comparison Page this skilldebuglebowski/slayzone | 191 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| SEO Competitor Comparison PagesAgriciDaniel/claude-seo | 18k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Competitor Alternativesfreekmurze/dotfiles | 1k | 23 repos | ~2k | Automated safety check: Pass | None | |
| AI SEOtech-leads-club/agent-skills | 7k | — | ~5.5k | Automated safety check: Pass | Custom licence | |
| Competitor Pagesindranilbanerjee/digital-marketing-pro | 854 | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Competitor Alternativesalirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
Competitor Alternatives
freekmurze/dotfiles
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
AI SEO
tech-leads-club/agent-skills
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production.
Competitor Pages
indranilbanerjee/digital-marketing-pro
Build competitor comparison and alternatives pages — X-vs-Y head-to-heads, alternatives-to-X lists, category roundups, and feature-matrix pages — delivering a 1,500+ word page template, comparison…
Competitor Alternatives
alirezarezvani/claude-skills
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement.
Alternatives Pages
sickn33/agentic-awesome-skills
Create "[Competitor] alternative" and comparison pages for developer tools.
More from debuglebowski/slayzone
All 16 skills in this repoSlay Artifacts
debuglebowski/slayzone
Manage task artifacts (files, folders) via the slay CLI. An agent skill from debuglebowski/slayzone.
Slay Automations
debuglebowski/slayzone
Create and manage automations via the slay CLI. An agent skill from debuglebowski/slayzone.
Slay Orchestrate
debuglebowski/slayzone
Supervise a set of slay tasks through planning, execution, and verification
Slay Context
debuglebowski/slayzone
Ensure root instruction files include SlayZone environment context
Slay Pty
debuglebowski/slayzone
Interact with PTY terminal sessions via the slay CLI. An agent skill from debuglebowski/slayzone.
Commit
debuglebowski/slayzone
Commit the changes that has been worked on in this session. An agent skill from debuglebowski/slayzone.
Related
Categories
Questions about Comparison Page
What does Comparison Page do?
Create or update objective website comparison pages and head-to-head pages from the comparison canon. Comparison Page is an agent skill from debuglebowski/slayzone. Create or update objective website comparison pages and head-to-head pages from the comparison canon.
When should I use Comparison Page?
Comparison Page fits situations like: slayZone vs competitor pages with quick verdict; last-checked freshness; top-of-page side-by-side screenshots; pick-X-if blocks.
How do I install Comparison Page in Claude Code?
Run `npx skills add debuglebowski/slayzone --skill comparison-page -a claude-code`. Or copy the skill folder (.agents/skills/comparison-page in debuglebowski/slayzone) into .claude/skills/comparison-page in your project. Claude Code loads it when a task matches its description.
How do I install Comparison Page in Codex?
Run `npx skills add debuglebowski/slayzone --skill comparison-page -a codex`. Or copy the skill folder (.agents/skills/comparison-page in debuglebowski/slayzone) into .agents/skills/comparison-page in your project. Codex loads it when a task matches its description.
Can I use Comparison Page 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 debuglebowski/slayzone --skill comparison-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/comparison-page, .gemini/skills/comparison-page, .github/skills/comparison-page and .opencode/skills/comparison-page in your project.
What does Comparison Page need to run?
SKILL.md names no scripts, command-line tools or credentials: Comparison Page is instructions for the agent only.
Does Comparison Page 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 Comparison Page 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. Review the folder before installing.
What licence does Comparison Page use?
Comparison Page is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Comparison Page use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Comparison Page?
Skills that share tags, products or a category with Comparison Page: SEO Competitor Comparison Pages (AgriciDaniel/claude-seo, 18k stars), Competitor Alternatives (freekmurze/dotfiles, 1k stars), AI SEO (tech-leads-club/agent-skills, 7k stars) and Competitor Pages (indranilbanerjee/digital-marketing-pro, 854 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Comparison Page?
debuglebowski (a GitHub user) maintains it in debuglebowski/slayzone, which has 191 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 3, 2026.
Source: debuglebowski/slayzone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.