Skip to main content
skill CX Codex

competitive-analysis · owl-listener — Claude Code skill: UX competitor breakdown

A skill that compares rival products on UX: patterns, features, gaps and opportunities. Useful when you need to know what competitors actually do.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill competitive-analysis -a claude-code
Open on GitHub

What competitive-analysis does

The skill gives the agent a design-side framework for competitive analysis. It sorts competitors into direct, indirect and aspirational benchmarks from adjacent domains. Then it walks the evaluation dimensions: information architecture, interaction patterns, visual design, content strategy, performance, accessibility, mobile experience.

Next comes a matrix for each key task — support level, steps required, a 1-5 UX score and any unique approaches. Strengths, weaknesses, friction points, table-stakes patterns and unaddressed gaps get their own pass. The deliverable is a summary overview, the comparison matrix, competitor profiles, an opportunity map and annotated references.

The skill advises analyzing full journeys rather than isolated screens, and refreshing the work as competitors evolve. If your goal is to deliberately adopt someone else's conventions instead of studying the market, the author points to jakobs-law in interaction-design.

What it helps with

  • sort rivals into direct, indirect and aspirational benchmarks
  • compare key tasks by step count and UX quality
  • spot unaddressed gaps in the category
  • check competitors' accessibility and mobile experience
  • build a feature matrix and opportunity map for the team

Example prompts for the agent

  • analyze our onboarding against three competitors
  • build a feature comparison matrix for the top rivals
  • compare the checkout journey across our product and theirs

How to install competitive-analysis

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill competitive-analysis -a claude-code

2Manually: put the files in place

~/.claude/skills/competitive-analysis/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competitive-analysis/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competitive-analysis

How do I install competitive-analysis in Claude?

Run npx skills add Owl-Listener/designer-skills --skill competitive-analysis -a claude-code. The skill lands at ~/.claude/skills/competitive-analysis/SKILL.md.

What does competitive-analysis do?

It compares competitor products on UX: patterns, features, strengths and gaps. You get an overview, a comparison matrix, competitor profiles and an opportunity map.

How is it different from jakobs-law?

competitive-analysis studies what competitors do. jakobs-law from interaction-design is for when you decide to adopt their conventions on purpose.

Source text

SKILL.md · MIT
---
name: competitive-analysis
description: 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).
---
# 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

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

competitive-analysis by other authors comes first.

competitive-analysis official anthropics A framework for building competitor analysis decks in PowerPoint or chat. It clarifies project scope, then builds verified slides once the outline is approved. CX Codex +1 2,400installs competitive-analysis claude-office-skills Builds competitor profiles, feature matrices, SWOT summaries, and market positioning maps. Useful when planning go-to-market moves or updating sales battle cards. CX Codex +1 5,100installs discover-competitive-analysis product-on-purpose Builds a structured teardown of 3–5 direct and indirect competitors: features, pricing, positioning, a 2x2 map and strategic calls. CX Codex +1 832installs competitive-analysis-process deanpeters Orchestrates competitor research through a structured six-stage workflow tied to strategic choices. It produces battle cards, matrices, and threat assessments. CX Codex +1 1,200installs firecrawl-competitive-intel firecrawl Monitors competitor pricing, feature releases, and changelogs using Firecrawl. Useful for ongoing market tracking and generating structured intelligence reports. CX Codex +1 31,300installs competitive-landscape Seth Hobson This skill compares competitors, finds open positioning gaps, and shapes competitive strategy for startup analysis or an investor pitch. CX Codex 11,034installs competitive-battlecard phuryn Creates sales battlecards for a named competitor, covering positioning, features, objections and deal patterns. Use it before calls or when preparing comparison material. CX Codex +1 2,800installs competitive-teardown Alireza Rezvani Runs a competitor teardown step by step: pricing, review, job-posting and SEO signals, a 12-dimension scorecard, then matrices, SWOT and an action plan. 658installs

From the same set109

user-persona This skill builds 2-4 research-grounded personas from interview transcripts, surveys, or analytics. It helps teams align design decisions with observed user behavior. CX Codex +1 2,100installs gesture-patterns Designs touch and pointer gestures such as swipes, dragging and long presses. Use it when an interface relies on gestural input. CX Codex +1 2,100installs feedback-patterns Gives the agent a method for designing how a system answers a user action: toasts, progress, badges, notifications. Useful when the interface goes silent after a click. CX Codex +1 2,100installs design-brief Drafts a project brief covering problem space, audience, constraints, and success criteria. Built for kicking off a specific task or feature. CX Codex +1 2,100installs prototype-strategy Decide what kind of prototype to build and how detailed it should be, before you start building it. CX Codex +1 2,100installs theming-system Designs a three-layer token architecture to support brand variants, color modes, and interface density in a single component library. CX Codex +1 2,100installs journey-map This skill maps one persona's end-to-end experience: stages, touchpoints, emotions and pain points. Useful when you're improving something that already exists. CX Codex +1 2,100installs component-spec This skill writes a full spec for one design-system component: anatomy, variants, states, accessibility and usage rules. Useful when a library grows and the API needs pinning down. CX Codex +1 2,100installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor