competitive-analysis

competitive-analysis is a skill for Claude Code from Owl-Listener/designer-skills. It costs 44 tokens per session (285 once invoked), scanned A, original, MIT.

A structured comparison of competing products, including their features, user experience, strengths, and gaps.

In plain words
What is it for?
Use it to compare user journeys, identify common patterns, find weaknesses, and uncover opportunities for improvement.
Why use it?
It replaces guesses about competitors with evidence about what they actually offer and how their products work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ux-strategy plugin — 12 skills, 3 commands shipped together

Good fit Use it to compare user journeys, identify common patterns, find weaknesses, and uncover opportunities for improvement.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/designer-skills/competitive-analysis
About the project

Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.

Owl-Listener/designer-skills · 3,116 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Owl-Listener/designer-skills --skill competitive-analysis
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/designer-skills

Made for: Claude Code.

Or install ux-strategy, the plugin that ships this one along with the rest of its 12 skills, 3 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for competitive-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/designer-skills/competitive-analysis/github.svg)](https://agentmods.dev/skills/owl-listener/designer-skills/competitive-analysis)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/competitive-analysis"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/competitive-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for competitive-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/designer-skills/competitive-analysis"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/competitive-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.00285
Opus 5.5 $0.00018 $0.00114
Sonnet 5.5 $0.00009 $0.00057
Haiku 4.5 $0.00004 $0.00028

Measured 1mo ago against content hash ebbcaf0e4f2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

competitive-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

ux-strategy/skills/competitive-analysis/SKILL.md · 27 lines

What it actually says

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
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 27 lines · 44 tokens per session scan A ebbcaf0e4f2b

Subscribe to this mod's changes

competitive-analysis is a skill published in the GitHub repository Owl-Listener/designer-skills (3,116 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 285 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

ui-review

Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.

LiHongwei-cn/lihongwei-cn · 26 tokens

design-craft

Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…

WrongStack/WrongStack · 63 tokens

design-critique

Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…

WrongStack/WrongStack · 110 tokens

design-reference-read

Read a reference website or screenshot the way a designer does — by measuring it. Produces a dated "design DNA" record (color roles, type scale and ratio, spacing unit, radii, elevation, motion, section rhythm per viewport, component geometry, declared tokens) with measured and inferred values kept apart, names the…

WrongStack/WrongStack · 174 tokens

anti-slop-frontend

A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…

BlackBeltTechnology/pi-agent-dashboard · 147 tokens

design-to-code

Implement a supplied Figma design, screenshot, live reference site or design specification as a working interface, and prove the match with measured fidelity scores per axis (color, type, space, shape, layout, motion) instead of eyeballing. Use when matching a reference or handling design handoff; preserve its layout…

WrongStack/WrongStack · 72 tokens