Sponsor Suno AI Music arrow_forward
Slash Command

Competitor Scan

Analyze the competitive landscape and identify gaps

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Competitor Scan is

Competitor Scan is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Competitor Scan gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Competitor Scan

Claude Code

  1. Download competitor-scan.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/productivity/pm-ai-partner/commands/pm/competitor-scan.md, shared under the repository's MIT license. Read the full file on GitHub.

Help me analyze the competitive landscape for: $ARGUMENTS

Instructions

Conduct a structured competitive analysis. The goal is not a feature checklist — it's identifying where competitors are genuinely better, where we're differentiated, and what we should actually do about it.

Process

  1. Map the landscape — Identify direct competitors, indirect alternatives, and "do nothing" options users have
  2. Analyze positioning — How does each competitor position themselves? What do they claim vs. deliver?
  3. Compare with insight — Feature comparison with "so what?" for each gap
  4. Assess and recommend — Classify each competitive gap as Ignore / Monitor / Respond / Lead

Tools to Use

  • Use web fetch to pull competitor websites, pricing pages, and changelogs
  • Search for competitor reviews, G2/Capterra ratings, and app store feedback
  • Look for competitor engineering blogs or public repos for technical insight
  • Check social media and community forums for user sentiment

Output Format

# Competitive Analysis: [Market/Competitor]

## Landscape Map
| Player | Type | Positioning | Target Audience |
|--------|------|-------------|-----------------|

## Positioning Map
[Mermaid quadrant or description of how players position on key axes]

## Feature Comparison (with insight)
| Capability | Us | Competitor A | Competitor B | Insight |
|---|---|---|---|---|
| [Feature] | [status] | [status] | [status] | [Why this matters or doesn't] |

## Strengths to Defend
1. **[Strength]** — Why it matters, evidence it's real

## Gaps to Evaluate
…

Principles

  • Objective, not defensive — If a competitor is genuinely better at something, say so
  • Jobs-to-be-done framing — Competitors are whoever solves the same user need, not just the same category
  • "Why haven't they?" is as important as "why have they?" — Missing features may signal constraints, not ignorance
  • Feature parity is a trap — Only recommend matching features that demonstrably drive competitor advantage

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Competitor Scan?

Competitor Scan is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Analyze the competitive landscape and identify gaps

How do I install Competitor Scan in Claude Code?

Download competitor-scan.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Competitor Scan in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Competitor Scan safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.