Skip to content
TrustedSkillsbeta
Back to all skills

Ux Friction Analyzer

Checked
erichowens·vlatest·frontend·MIT

Identifies usability roadblocks and suggests improvements within digital interfaces based on user interaction data.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add curiositech/some_claude_skills --skill ux-friction-analyzer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

erichowens

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned erichowens/some_claude_skills at 6713fc7a64.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
6713fc7a64
Manifest
.claude/skills/ux-friction-analyzer/SKILL.md
Scanned
1 file, 404 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The ux-friction-analyzer skill identifies and resolves points of friction in user experiences, helping AI agents streamline workflows and improve satisfaction. It specifically targets obstacles that hinder users from achieving their goals efficiently within digital environments.

When to use it

  • Diagnosing why users abandon a specific step in a multi-stage process.
  • Optimizing conversational flows to reduce repetitive clarifications or errors.
  • Identifying confusing navigation patterns or unclear instructions in an interface.
  • Analyzing feedback loops where user input leads to unexpected system responses.

Key capabilities

  • Pinpoints exact locations where user effort increases unnecessarily.
  • Suggests actionable improvements to remove identified barriers.
  • Evaluates the clarity and effectiveness of current interaction designs.

Example prompts

"Analyze this checkout flow and highlight every point where a user might get stuck." "What are the main sources of friction preventing users from completing their profile setup?" "Review the error messages in this form and suggest changes to reduce user confusion."

Tips & gotchas

Ensure you provide clear context about the user journey or specific interface elements being analyzed for accurate results. This skill works best when paired with concrete examples of user behavior or feedback data.