CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-ux

Capture the user's UX vision in two documents: DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

Quality

93%

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%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.

An exemplary process skill body: dense but unambiguous, fully actionable commands, explicit sequencing with validation checkpoints and fallbacks, and clean separation of overview from one-level-deep reference material. No dimension shows a meaningful weakness.

DimensionReasoningScore

Conciseness

The body is relentlessly lean — e.g. "Sections omittable; order locked when present." — with no explanation of concepts Claude already knows and no padding; even illustrations like the named-protagonist examples exist to pin a rule ("Mary, mom of three, kids asleep — not 'the user'"), so every token earns its place.

5 / 5

Actionability

Guidance is fully concrete and executable: exact commands with flags ("uv run {project-root}/_bmad/scripts/memlog.py append --workspace {doc_workspace} --type <decision|change|override|assumption|event> --text \"…\""), exact folder patterns ("ux-{slug}/ux-{slug}.md"), and specific fallback steps for each failure mode (script not found, no active_initiative).

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced (numbered On Activation 1–5, ordered Finalize outcomes) with real checkpoints — the Reviewer Gate opt-in, "Runs the rubric walker's Pass 1 coverage checks proactively", the mock-coverage walk, and "confirm every entry was executed in order" — plus error-recovery paths (resume detection, misroute scan, script-not-found fallbacks).

5 / 5

Progressive Disclosure

The body is an overview that pushes all detail to real, clearly-signaled, one-level-deep bundle files — references/design-md-spec.md, references/validate.md, references/headless.md, and references/creative-tools.md all exist, with examples and templates in assets/ — and references are cited exactly where each is needed.

5 / 5

Total

20

/

20

Passed

Description

83%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.

A strong description that clearly states both capability (two scoped UX documents) and explicit, naturally-phrased triggers in third person. Its only weaknesses are incomplete coverage of the skill's full action set (update/validate) and a few missing natural synonyms.

DimensionReasoningScore

Specificity

"Capture the user's UX vision in two documents" plus "DESIGN.md for how the product looks and EXPERIENCE.md for how it behaves" names the domain and two concrete deliverables with a clear scope split, exceeding the anchor-3 example, but does not list several distinct actions (update, validate, elicitation modes are unmentioned), so it falls short of anchor 5.

4 / 5

Completeness

It explicitly answers both what ("Capture the user's UX vision in two documents: DESIGN.md... EXPERIENCE.md...") and when ("Use when the user says..." with three concrete trigger phrases), matching the anchor-5 exemplar structure exactly.

5 / 5

Trigger Term Quality

The quoted phrases "lets create UX design", "create UX specifications", and "help me plan the UX" are natural things a user would say, giving good coverage, but common variations such as "user experience", "UI design", or "wireframes" are missing, so it does not reach comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Capturing UX vision into two named peer documents is a clear niche and every trigger phrase contains "UX", keeping conflict risk low, but adjacent visual-design or UI-mockup skills could still overlap on "design"-style requests, leaving minor rather than minimal overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-ux/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.