CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-agent-ux-designer

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

65

Quality

78%

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

88%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 content is a tightly written, highly actionable 8-step activation workflow with concrete commands, an explicit confirmation checkpoint, and an error-recovery fallback. It is well-structured and self-contained, with only minor conciseness padding and no need for external reference files.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with only minor motivational padding ('Fully embody this persona so the user gets the best experience') that could be trimmed, so it sits at efficient-with-minor-over-explanation rather than the every-token-earns-its-place bar of 5.

4 / 5

Actionability

It provides fully executable, copy-paste-ready guidance — exact 'uv run' commands with argument templates, a concrete file-read order, specific merge rules, and defined menu columns — with a documented fallback when the script fails.

5 / 5

Workflow Clarity

The 8-step activation sequence is clearly ordered with an explicit confirmation checkpoint ('confirm every entry was executed in order before proceeding') and an error-recovery feedback loop (Step 1 script-failure fallback); this is not a destructive/batch operation so the cap-at-3 rule does not apply.

5 / 5

Progressive Disclosure

The body is well-organized into clear sections and numbered steps with no nested references, but at roughly 70 lines it exceeds the under-50-line simple-skill threshold and has no bundle files to split, so it does not fully reach the clear-overview-with-one-level-references bar of 5.

4 / 5

Total

18

/

20

Passed

Description

68%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 strong, distinctive trigger guidance and a clear 'when' clause, but its 'what' is only a role label with no concrete actions or capabilities. Expanding the capability statement would lift specificity and completeness.

Suggestions

Add 1-2 concrete actions to the description (e.g. 'translates user needs into interaction design and UX specifications') so specificity moves beyond a bare role label.

Broaden trigger terms to include natural synonyms users might say, such as 'UI', 'user experience', or 'interface design', not just 'UX designer'.

Tighten the 'what' so it states what Sally produces (UX specs, interaction designs) rather than only who she is, pushing completeness toward 5.

DimensionReasoningScore

Specificity

The description names a concrete domain ('UX designer and UI specialist') but states no concrete actions, matching the anchor for naming the domain with minimal/generic actions; it is not a 1 because the domain is specific rather than pure abstract fluff, and not a 3 because no actions are listed.

2 / 5

Completeness

It has both a 'what' (UX designer/UI specialist role) and an explicit 'when' ('Use when the user asks to talk to Sally or requests the UX designer'), but the 'what' is a thin role label with no concrete capabilities, so it does not reach the explicit-both-with-concrete-triggers bar of 5.

4 / 5

Trigger Term Quality

'talk to Sally' and 'requests the UX designer' are natural phrases a user would say, giving good keyword coverage, but common synonyms like UI, user experience, or interface design are missing, so it falls short of comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

The trigger is gated on a unique persona name ('Sally') and a specific role ('UX designer'), creating a clear niche with minimal conflict risk against other skills.

5 / 5

Total

15

/

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.

Validation15 / 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
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.