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.

71

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tightly written, fully executable 8-step activation procedure with explicit sequencing, an error-recovery fallback, and a completion checkpoint. It earns top marks across actionability, workflow clarity, and progressive disclosure, with only minor policy-prose that could be tightened.

DimensionReasoningScore

Conciseness

The body is dense procedural instruction with no concept-pedagogy Claude already knows; every line addresses path resolution, merge rules, or activation steps, though a few Step 8 policy sentences could be trimmed.

3 / 3

Actionability

It provides an executable resolver command, exact file paths, and concrete structural merge rules, giving copy-paste-ready guidance.

3 / 3

Workflow Clarity

Eight explicitly sequenced steps with a script-failure fallback branch and an explicit completion checkpoint before the main workflow begins.

3 / 3

Progressive Disclosure

With no bundle files present, the self-contained body is organized into clear sections (Overview, Conventions, On Activation) with no nested reference chains, meeting the simple-skill exception for a well-organized single file.

3 / 3

Total

12

/

12

Passed

Description

75%

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 pairs a clear domain statement with an explicit persona-triggered 'Use when' clause, giving it strong completeness and distinctiveness. Its main weakness is a lack of concrete action verbs and narrower trigger-term coverage.

Suggestions

Add concrete actions to the description, e.g. 'Designs interaction flows, wireframes, and UX specifications' so it lists what the skill does, not just what it is.

Broaden trigger terms to cover natural phrasings such as 'design the UI', 'user experience', 'wireframes', or 'interaction design'.

Consider whether naming only the persona ('Sally') limits discoverability for users who don't know the agent's name; add domain-based triggers too.

DimensionReasoningScore

Specificity

The phrase 'UX designer and UI specialist' names the domain concretely but lists no concrete actions, so it falls between the vague anchor and the multi-action anchor.

2 / 3

Completeness

It states what the skill is ('UX designer and UI specialist') and includes an explicit 'Use when...' trigger, satisfying both what and when.

3 / 3

Trigger Term Quality

'talk to Sally' and 'requests the UX designer' are natural user phrases, but common variations like 'design the UI', 'user experience', or 'wireframes' are missing.

2 / 3

Distinctiveness Conflict Risk

The persona-based trigger 'Sally' is highly distinctive, making it unlikely to fire for an unrelated skill.

3 / 3

Total

10

/

12

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.