agentleFS
miguelclavelmiguelclavel/ux-research-skills/skills/competitive-analysis/SKILL.md

competitive-analysis

Skill1 starsChanged 37 days agoMITView on GitHub

Run a competitive UX analysis of how other products handle a specific flow, as patterns and gaps rather than a feature list. Use when someone wants a competitor review, a UX benchmark, inspiration from other products, or to understand conventions for a flow.

54 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use onboarding-flow, lead-scoring and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Dragoon0xSkill

    onboarding-flow

    Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.

    Also in 3 projects that use this

  • shawnpangSkill

    lead-scoring

    When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.

    Also in 3 projects that use this

  • nicepkgSkill

    user-research-synthesis

    Synthesize qualitative and quantitative user research into structured insights and opportunity areas. Use when analyzing interview notes, survey responses, support tickets, or behavioral data to identify themes, build personas, or prioritize opportunities.

    Also in 4 projects that use this

  • claude-office-skillsSkill

    email-marketing

    Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics

    Also in 3 projects that use this

  • AnthropicSkill

    user-research

    Plan, conduct, and synthesize user research. Trigger with "user research plan", "interview guide", "usability test", "survey design", "research questions", or when the user needs help with any aspect of understanding their users through research.

    Also in 3 projects that use this

  • walternateSkill

    go-to-market

    Build a go-to-market (GTM) strategy for launching a product or entering a new market. Use when planning how to reach customers, position your product, choose channels, set pricing, and execute launch. Covers market entry strategy, customer segmentation, positioning, channel strategy, and GTM execution plan. Trigger on "go-to-market", "GTM strategy", "market entry", "launch strategy", "how to reach customers", "GTM plan".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look at how others solve the same job, so you know what people already expect and where nobody does it well.

    line 8
  2. Distinctive:

    Pick the flow and the job,: not the whole product ("getting a first car insurance price").

    line 12
  3. Distinctive:

    Don't copy a pattern just because a big company uses it.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Competitive analysis

Look at how others solve the same job, so you know what people already expect and where nobody does it well.

Steps

  1. Pick the flow and the job, not the whole product ("getting a first car insurance price").
  2. Pick five to eight products: direct competitors, one or two adjacent ones that solve a similar job well, and a best in class example from another industry.
  3. Walk the flow in each as a new user, capturing screenshots of every step.
  4. Compare on the same criteria: how it starts, steps before the first useful result, what personal information is asked and how it's explained, how errors and edge cases are handled, trust signals, accessibility basics, mobile experience.
  5. Separate: conventions (most do it, so users expect it), differentiators (one does it notably well), and gaps (nobody does it well).

Output

A comparison table (product by criteria) with screenshots, then conventions, differentiators and gaps, and one to three ideas worth testing. Every cell is something you can point to; if you couldn't see it, write "not visible".

Don't

  • Don't copy a pattern just because a big company uses it. Don't create accounts with real personal data to get through a flow.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.