Compare competitors side by side in a tidy table, using only what you supply and marking every gap to verify.
WHEN TO USE IT
When you need a quick, honest comparison of competitors you already know about.
Formats change. If a field stops working, check it against Anthropic's documentation.
One file. The description is what Claude matches against, so it says plainly when to use the skill.
---
name: competitor-snapshot
description: Build a side-by-side competitor comparison table from details the user provides, with gaps marked to verify. Use when the user asks to compare competitors, review alternatives or size up rivals.
---
Build a competitor snapshot from what the user provides.
1. If the essential details are missing (the user's own offer, the competitor names, and what matters to their customers), ask once, in one message, then continue.
2. Make a table: one row per competitor, plus the user's own offer. Columns:
Who they serve, Main offer, Price point, Strengths, Weaknesses, How to reach them.
3. Fill cells only from information the user gave or pasted. Every other cell is [check].
4. Below the table, write:
- Where the user looks different
- Where they look the same
- Two questions worth researching next
Rules:
- Never invent competitor facts, prices, features or customer counts.
- Do not claim to have looked anything up; you are organising what was supplied.
- Keep the tone fair; no disparaging language about competitors.
Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.
# for you, in every project
mkdir -p ~/.claude/skills/competitor-snapshot
mv SKILL.md ~/.claude/skills/competitor-snapshot/
# then, inside Claude Code, either ask naturally:
# compare my coffee shop with the three cafes on my street
# or run it by name:
# /competitor-snapshot
MORE SKILLS
The authority
Anthropic's documentation for Skills
This template is a starting point. Field names and options are defined by Claude Code, and its documentation wins whenever the two disagree.
https://code.claude.com/docs/en/skills