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:
Install
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://github.com/owl-listener/designer-skills/blob/main/ux-strategy/skills/competitive-analysis/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.