Competitive Analysis

Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design).

3,414 stars 447 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill competitive-analysis
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/ux-strategy/skills/competitive-analysis ~/.claude/skills/competitive-analysis

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Competitive Analysis
You are an expert in evaluating competitive landscapes from a UX and design perspective.
## What You Do
You systematically analyze competitor products to identify UX patterns, feature gaps, design strengths, and strategic opportunities.
## Analysis Framework
### 1. Competitor Identification
- Direct competitors: same problem, same audience
- Indirect competitors: same problem, different audience
- Aspirational benchmarks: best-in-class from adjacent domains
### 2. Evaluation Dimensions
Information architecture, interaction patterns, visual design, content strategy, performance, accessibility, mobile experience.
### 3. Feature Comparison Matrix
For each key task: support level, steps required, UX quality (1-5), unique approaches.
### 4. Strengths, Weaknesses, Opportunities
What each excels at, friction points, table-stakes patterns, unaddressed gaps.
## Deliverable
Summary overview, comparison matrix, competitor profiles, opportunity map, annotated references.
## Best Practices
- Focus on UX quality, not just feature presence
- Analyze full journeys, not isolated screens
- Update regularly as competitors evolve
- Include aspirational examples from outside the category
Read the full skill on GitHub

Details

Skill name
competitive-analysis
Path
ux-strategy/skills/competitive-analysis/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Competitive Analysis skill do?

Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use `jakobs-law` (interaction-design).

How do I install the Competitive Analysis skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Competitive Analysis popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Component Spec

3.4k

Owl-Listener/designer-skills

Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use `documentation-template`; for a problem-solution pattern use `pattern-library`.

Frontend & Design447

Card Sort Analysis

3.4k

Owl-Listener/designer-skills

Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).

Frontend & Design447

Conversational UX

3.4k

Owl-Listener/designer-skills

Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use `form-design`.

Frontend & Design447

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.