New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

UX Product Auditor

by cbrock84 in cbrock84/headcount

Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity.

MITAuto-check passedFrontend & Design

Install UX Product Auditor

skills CLI
$ npx skills add cbrock84/headcount --skill ux-product-auditor -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount ux-product-auditor --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/product/skills/ux-product-auditor .claude/skills/ux-product-auditor && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ux-product-auditor
GitHub stars
2k
Token cost
~1.2k tokens
SKILL.md length
734 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity.

  • Tasks that involve UX design
  • SKILL.md covers Audit by walking the real path, Lenses, Severity and Finding format, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

UX Product Auditor is an agent skill from cbrock84/headcount. Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use interface-craft.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Frontend & Design, covering UX design. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve UX design

Example prompts

  • “Use the ux-product-auditor skill to audit a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every…”
  • “/ux-product-auditor”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

UX Product Auditor loads about 1.2k tokens when it runs, and up to ~2k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 734 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~107
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 734 words, ~1,245 tokens.

Download SKILL.mdSave it as .claude/skills/ux-product-auditor/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
ux-product-auditor
description
Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use `interface-craft`.

UX and product auditor

A finding that does not name a consequence is an opinion. Every item in an audit connects a specific friction to a specific outcome.

Audit by walking the real path

Do the actual task, on the actual device, as a first-time user with no context — not a tour of the screens. Most serious problems live in transitions between screens, which a screen-by-screen review never sees.

Then walk it again as a returning user, whose needs are opposite: speed over explanation, and recovery from whatever state they left in.

Lenses

Run each separately; combined, you find only what you were already looking for.

  • Comprehension — can a stranger tell what this does and whether it is for them?
  • First value — how many steps to the first genuinely useful moment, and how many are avoidable?
  • Friction — every field, click, decision, and wait. Which are load-bearing and which are habit?
  • Trust — does anything ask for more than it has earned at that point?
  • Recovery — what happens on error, empty, slow, offline, or wrong input?
  • Accessibility — contrast, keyboard reachability, target size, meaning carried by color alone. Below this floor, some people cannot use the product at all.

Severity

Assign one to every finding, and be strict — an audit where everything is critical has ranked nothing:

  • Critical — blocks the primary task, loses data, or excludes a group of users entirely.
  • High — measurably costs conversion or activation for many users.
  • Medium — friction with a workaround, or affects a narrower path.
  • Low — polish, inconsistency, or a preference.

Finding format

Each finding carries: where (the exact screen and step), what the user experiences, why it costs something, the consequence in business terms, severity, and the fix with rough effort.

"The signup form asks for company size before the account exists; users who do not know it guess or abandon; this sits before the only conversion event on the page" is a finding. "Form is too long" is a note.

Diagnosing low conversion or activation

Instrument the funnel to find where, then observe sessions to find why. Analytics say the step; only watching says the reason. Teams that skip the second half fix the wrong thing confidently.

Common causes, in rough order of frequency: asked for too much too early, value not visible before effort is required, an empty state with no path out of it, and a required integration the user cannot authorize.

Show full SKILL.md (336 more words)Show less

Scoring

Where a numeric score is useful — tracking over time, comparing surfaces, reporting to someone who did not read the audit — score each lens from one to five against stated criteria, and publish the criteria alongside the score. An unexplained score is unfalsifiable and will be argued with rather than acted on.

Use the same scale everywhere so scores are comparable between audits. Do not average the lenses into one headline number: a product that is excellent everywhere and inaccessible scores well on the average and is still unusable for some people.

Moving from findings to solutions

An audit that stops at problems transfers the hard part back. For each finding above medium severity, propose a specific fix — the actual change, not a direction — with rough effort and what it would improve.

Where several findings share a root cause, say so and propose the one change. Fifteen findings traceable to a missing design system is one finding.

Where the right fix is uncertain, propose the cheapest way to find out rather than guessing.

Prioritizing

Rank by users affected × severity ÷ effort. Then state the one thing to fix first, and be willing to say that most of the list is not worth doing yet. A prioritized audit is more useful than a complete one.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Report a finding without the path that produces it. A claim nobody can reproduce gets ignored.
  • Rank findings by how easy they are to fix. Rank by cost to the user, then note which ones are cheap.
  • Audit a staging build or a marketing page that real users never touch.
  • Call a preference a defect. Say what breaks and for whom, or leave it out.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/product/skills/ux-product-auditor of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

UX Product Auditor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

UX Product Auditor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UX Product Auditor this skillcbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Interface Design for Dashboards and Appsholaboss-ai/holaOS11k3 repos~6kAutomated safety check: PassMIT
Animategrowupanand/ConvoForm1026 repos~1.9kAutomated safety check: PassApache-2.0
Migrate Content Iadocker/docs4.7k—~5.1kAutomated safety check: PassApache-2.0
UX WalkthroughXiaoMi/hiui879—~1.3kAutomated safety check: PassMIT

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed

  • Interface Design for Dashboards and Apps

    holaboss-ai/holaOS

    Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Frontend & DesignAuto-check passed

  • Animate

    growupanand/ConvoForm

    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

    102 GitHub starsUsed in 6 repos~1.9k tokens
    Frontend & DesignAuto-check passed

  • Migrate Content Ia

    docker/docs

    Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated 2 days ago
    Frontend & DesignAuto-check passed

  • UX Walkthrough

    XiaoMi/hiui

    体验走查 skill。适用于代码库、URL、截图三种输入，输出结构化体验问题报告，并同步生成本地 docx 报告。触发词：体验走查、UX review、交互走查、界面审查、体验问题。

    879 GitHub stars~1.3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed

  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    748 GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 23 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 23 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 23 days ago
    Auto-check passed

  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 23 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 23 days ago
    Auto-check passed

Categories

Questions about UX Product Auditor

What does UX Product Auditor do?

Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. UX Product Auditor is an agent skill from cbrock84/headcount. Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity.

When should I use UX Product Auditor?

UX Product Auditor fits situations like: tasks that involve UX design.

How do I install UX Product Auditor in Claude Code?

Run `npx skills add cbrock84/headcount --skill ux-product-auditor -a claude-code`. Or copy the skill folder (plugins/product/skills/ux-product-auditor in cbrock84/headcount) into .claude/skills/ux-product-auditor in your project. Claude Code loads it when a task matches its description.

How do I install UX Product Auditor in Codex?

Run `npx skills add cbrock84/headcount --skill ux-product-auditor -a codex`. Or copy the skill folder (plugins/product/skills/ux-product-auditor in cbrock84/headcount) into .agents/skills/ux-product-auditor in your project. Codex loads it when a task matches its description.

Can I use UX Product Auditor in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill ux-product-auditor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ux-product-auditor, .gemini/skills/ux-product-auditor, .github/skills/ux-product-auditor and .opencode/skills/ux-product-auditor in your project.

What does UX Product Auditor need to run?

SKILL.md names no scripts, command-line tools or credentials: UX Product Auditor is instructions for the agent only.

Does UX Product Auditor access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is UX Product Auditor safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does UX Product Auditor use?

UX Product Auditor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does UX Product Auditor use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 708 tokens, read only when the agent opens those files.

What are the alternatives to UX Product Auditor?

Skills that share tags, products or a category with UX Product Auditor: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 102 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UX Product Auditor?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.