CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-agent-ux-designer

UX designer and UI specialist. Use when the user asks to talk to Sally or requests the UX designer

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bmad-agent-ux-designer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-sequenced, highly actionable activation procedure with concrete commands, explicit error-recovery branches, and a final completion checkpoint. Its main weaknesses are moderate redundancy in the persona-persistence and icon-prefix instructions, and one densely written document-locating step in Step 5. Structure and disclosure are solid for a self-contained single-file skill.

Suggestions

State the persona-persistence and icon-prefix rules once (Step 3 or the closing paragraph) instead of repeating them in both places.

Rewrite Step 5's ticket-locating bullet as a short numbered list or decision rule so the document-discovery order is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly lean procedural directives with concrete commands, but it repeats itself — persona persistence is stated in Step 3 and again in the closing paragraph, and the icon-prefix rule appears in both Step 6 and the closing — and includes filler like "Fully embody this persona so the user gets the best experience". This fits anchor 3 (mostly efficient, some unnecessary explanation or tightening possible) rather than 4's minor-instances standard.

3 / 5

Actionability

Guidance is largely executable: copy-paste commands ("uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent", "npx skills add bmad-code-org/BMAD-METHOD --skill bmad"), precise merge rules ("Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries"), and a defined placeholder convention. It falls short of anchor 5 because Step 5's ticket/document-locating bullet is a dense run-on that is hard to execute unambiguously, and no example of a menu item or dispatch is given.

4 / 5

Workflow Clarity

The 8 activation steps are clearly numbered and sequenced, with explicit failure branches (script not found → offer setup; other failure → manual three-file merge fallback) and a final completion checkpoint ("confirm every entry was executed in order before proceeding"). This earns anchor 4 rather than 5 because minor validation gaps remain: no handling for missing config keys, an undefined {agent.menu}, or an empty prepend/append list's interaction with the final confirmation.

4 / 5

Progressive Disclosure

The skill is a well-sectioned single file (Conventions, On Activation with per-step subsections) with no broken references — no bundle files exist, and "references/guide.md" appears only as a path-format example. At ~70 lines it exceeds the under-50-line simple-skill case, and content like the detailed merge-rule fallback could arguably live in a reference file, so anchor 4 (good structure, minor organization gaps) fits better than 5.

4 / 5

Total

15

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit and distinctive trigger clause anchored to a named persona, but it says almost nothing about what the skill actually does — it is a role title, not a capability list. Users searching for UX/UI help with natural terms like "user experience" or "wireframes" would not find it. Adding 2-3 concrete capabilities and broader trigger synonyms would lift it substantially.

Suggestions

Replace the bare role label with 2-3 concrete capabilities, e.g. "Designs user experiences, produces UX specifications and wireframes, and translates user needs into interaction design".

Broaden the trigger clause to include natural synonyms users would say: "Use when the user asks to talk to Sally, or mentions UX design, user experience, UI, wireframes, or interface design".

Keep the persona trigger ("talk to Sally") since it is the most distinctive hook, but pair it with capability-based triggers so the skill is discoverable by users who don't know the persona's name.

DimensionReasoningScore

Specificity

The description names the domain ("UX designer and UI specialist") but lists no concrete actions or capabilities — nothing like designing wireframes, producing UX specs, or running elicitation. It matches anchor 2 (domain named, actions minimal/generic) rather than 3, which requires 1-2 concrete actions, and is not the pure abstraction of anchor 1.

2 / 5

Completeness

The "when" is explicit ("Use when the user asks to talk to Sally or requests the UX designer"), but the "what" is only a bare role label — "UX designer and UI specialist" — with no description of what the skill actually does. This sits between anchor 2 (vague what, no when) and anchor 4 (both present, when improvable): the when is present and explicit, but the what is too thin for anchor 4's standard.

3 / 5

Trigger Term Quality

"asks to talk to Sally" and "requests the UX designer" are natural phrases, but coverage stops there — common variations like "user experience", "UI", "interface design", or "wireframes" are missing. This fits anchor 3 (some relevant keywords, missing common variations) better than 4 (good coverage with only a few gaps).

3 / 5

Distinctiveness Conflict Risk

"talk to Sally" is a unique persona-specific trigger that would not fire for other skills, and the UX-designer niche is mostly distinct. Anchor 4 (mostly distinct, minor overlap risk) fits because "requests the UX designer" could still overlap with other design- or UI-related skills, keeping it below anchor 5's minimal-conflict standard.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-agent-ux-designer/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.