Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Competitive Analysis

ASecurity

Conduct a competitive analysis. Use when the user says "competitive analysis", "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas", "what does [competitor] do", "compare us to X", "positioning analysis", "value curve", or wants to understand how a product or feature compares to alternatives - even if they don't explicitly say "competitive analysis".

20 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentsgodocumentation

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add qa-aman/claude-skills --skill competitive-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Competitive Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Competitive Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qa-aman-competitive-analysis/badge)](https://www.skillsdirectory.com/skills/qa-aman-competitive-analysis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: competitive-analysis
description: >
  Conduct a competitive analysis. Use when the user says "competitive analysis",
  "how do competitors handle X", "market landscape", "blue ocean", "strategy canvas",
  "what does [competitor] do", "compare us to X", "positioning analysis", "value curve",
  or wants to understand how a product or feature compares to alternatives
  - even if they don't explicitly say "competitive analysis".
---

## Overview

Based on **"Blue Ocean Strategy"** by W. Chan Kim & Renee Mauborgne. Most competitive analysis maps what competitors do and tries to do it better - this is red ocean thinking. Blue Ocean Strategy asks a different question: what can we eliminate, reduce, raise, or create to make competition irrelevant?

## Workflow

### Step 1: Define the scope
- Is this for a specific feature or the whole product?
- What decision will this analysis inform?
- Who are the direct and indirect competitors?

Cap at 5-7 competitors. More dilutes the analysis.

### Step 2: Build the Strategy Canvas
Plot competitors on a graph:
- **X-axis:** Competing factors (price, speed, features, support, UX, etc.)
- **Y-axis:** Offering level (low to high) for each factor

This is the "as-is" state. Where do all competitors cluster? That cluster is the red ocean.

### Step 3: Apply the Four Actions Framework
For each competing factor, ask:

| Action | Question | Example |
|--------|----------|---------|
| **Eliminate** | What do all competitors offer that adds no real value? | Eliminate: complex onboarding wizards |
| **Reduce** | What can we offer well below industry standard? | Reduce: feature count, focus on core use case |
| **Raise** | What should we raise well above the industry standard? | Raise: response time, documentation quality |
| **Create** | What should we offer that no competitor does? | Create: role-based install, book-grounded methodology |

### Step 4: Draw the "to-be" value curve
Plot where your product sits after applying the four actions. A differentiated value curve:
- Has a different shape than competitors
- Focuses on a few factors rather than spreading thin
- Has a compelling tagline: "The only X that does Y for Z"

### Step 5: Identify non-customers
Blue Ocean insight: the biggest opportunity is often in people who don't use any competitor today. Who are the non-customers, and why aren't they buying? Three tiers:
- **Tier 1:** Soon-to-be non-customers (use reluctantly, would switch)
- **Tier 2:** Refusing non-customers (consciously chose alternatives)
- **Tier 3:** Unexplored non-customers (never considered this category)

### Step 6: State implications
"Given this analysis, we should consider..." - 2-3 concrete takeaways. No implications = just research, not strategy.

## Anti-Patterns

**1. Red ocean thinking**
Bad: "Competitor X has feature Y, so we need feature Y."
Good: Apply the four actions. Maybe feature Y should be eliminated or reduced.

**2. Competing on all dimensions**
Bad: Value curve that tries to be high on every factor.
Good: A focused curve that excels on 2-3 factors and consciously deprioritizes others.

**3. Ignoring non-customers**
Bad: Analysis only covers existing market users.
Good: Tier 1/2/3 non-customer analysis often reveals larger opportunities than competing for existing users.

**4. No strategy canvas**
Bad: Bullet list of what competitors do.
Good: Visual strategy canvas that makes the competitive landscape scannable.

## Quality Checklist

- [ ] Scope defined - feature vs. product, decision it informs
- [ ] Strategy canvas built with competing factors on X-axis
- [ ] Four Actions Framework applied: eliminate, reduce, raise, create
- [ ] "To-be" value curve drawn and differentiated from competitors
- [ ] Non-customer tiers considered
- [ ] Analysis ends with concrete implications

Attribution

qa-amanqa-aman
View sourceSee grades on GitHubMore from qa-aman →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →