Competitive analysis: compare UX patterns, features and gaps across rival products
Systematically analyze competitor products from a UX perspective — competitor identification, evaluation dimensions, feature comparison matrix, strengths/weaknesses/opportunities
- What
- Systematically analyze competitor products from a UX perspective — competitor identification, evaluation dimensions, feature comparison matrix, strengths/weaknesses/opportunities
- Cost
- Free
- Needs
- a competitive set to analyze (the skill is a methodology the agent follows, not software to install)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @owl-listener's competitive-analysis UX skill: a systematic framework for evaluating the competitive landscape from a design perspective. Runs four steps: competitor identification (direct — same problem, same audience; indirect — same problem, different audience; aspirational benchmarks from adjacent domains), evaluation across seven dimensions (information architecture, interaction patterns, visual design, content strategy, performance, accessibility, mobile experience), a feature comparison matrix (per key task: support level, steps required, UX quality 1-5, unique approaches), and strengths/weaknesses/opportunities (what each excels at, friction points, table-stakes patterns, unaddressed gaps). Deliverables: 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, include aspirational examples from outside the category. Honest caveats: methodology only, no tooling; for deliberately adopting rivals' conventions, the skill points to a `jakobs-law` skill that is not bundled here. MIT licensed. Sibling skills from the same repo are listed separately: « owl-listener-designer-skills-error-handling-ux » and « owl-listener-designer-skills-metrics-definition ». Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Competitive analysis is a free Muse skill for systematically analyzing competitor products from a UX perspective. It covers competitor identification, evaluation dimensions, feature comparison matrices and strengths, weaknesses and opportunities. That structure turns casual competitor browsing into evidence you can actually design against.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 9a6930cStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a competitive set to analyze (the skill is a methodology the agent follows, not software to install) Install "Competitive analysis: compare UX patterns, features and gaps across rival products" for me. It gives my agent @owl-listener's UX competitive-analysis framework: competitor identification (direct, indirect, aspirational), evaluation across seven dimensions, a feature comparison matrix, and a strengths/weaknesses/opportunities readout with deliverables (overview, matrix, profiles, opportunity map, annotated references). MIT-licensed. Repository: https://raw.githubusercontent.com/owl-listener/designer-skills/9a6930cf84a822eb458624bd11c61aac5bbdf224/ux-strategy/skills/competitive-analysis/SKILL.md Pinned version: install the code at commit 9a6930cf84a822eb458624bd11c61aac5bbdf224 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). Review the files for suspicious commands or credential handling; stop on any red flag and never assume the repository is safe. Tell me if anything looks off. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "competitive-analysis". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand the agent the product and the rivals to compare; the jakobs-law skill referenced for adopting conventions is not bundled here). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 9a6930c · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.