CtrlK
BlogDocsLog inGet started
Tessl Logo

ui-ux-pro-max

This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.

72

Quality

90%

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

80%

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

The body is concise and highly actionable with concrete executable commands and a clear sequenced workflow. Its weak points are the absence of explicit validation/feedback checkpoints in the workflow and a missing referenced bundle file (data/ui-reasoning.csv) that breaks one signaled navigation path.

Suggestions

Add an explicit validation/feedback step to the Core workflow (e.g., 'If a --domain search returns no matches, broaden keywords or fall back to the master design-system') so error recovery is stated rather than implicit.

Resolve the dangling 'data/ui-reasoning.csv' reference: either include the data/ directory in the bundle (scripts/search.py loads it at runtime) or remove the line from the References section so every signaled path resolves.

Turn the Safety rules into an end-of-workflow verification checkpoint (e.g., confirm palette contrast meets WCAG and animations honor prefers-reduced-motion before finalizing) to give the synthesis step an explicit validation gate.

DimensionReasoningScore

Conciseness

The body is lean — compact bullets and concrete commands with no explaining of basics Claude already knows (what a palette/typography is, how Tailwind works) — so every token earns its place per the lean-and-efficient anchor.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands such as 'python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "<query>" --design-system -p "Project Name"' with real flags (--design-system, --persist, --page, --domain, --stack) plus enumerated supported domains/stacks.

3 / 3

Workflow Clarity

A clear numbered 1–5 Core workflow plus a synthesis 'Default output shape' checklist is present, but there are no explicit validation checkpoints or error-recovery feedback loops (e.g., what to do when a --domain search returns nothing), so it sits at the checkpoints-implicit level rather than the explicit-validation level above.

2 / 3

Progressive Disclosure

The References section is well-signaled and one level deep with a real references/USAGE.md, but the signaled 'data/ui-reasoning.csv' path is absent from the bundle (and scripts/search.py requires it at runtime), so a referenced path does not resolve and navigation is partially broken.

2 / 3

Total

10

/

12

Passed

Description

100%

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 is specific, trigger-rich, and complete, explicitly stating both capabilities and when to invoke the skill in third-person voice. It is distinct from typical document/code skills and carries no obvious conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces' — matching the multiple-specific-actions anchor rather than the domain-plus-some-actions level below.

3 / 3

Completeness

Explicitly answers both what (design/review UI, build landing pages/dashboards, pick colors/typography, improve accessibility, implement frontend interfaces) and when via the 'should be used when the user asks to...' trigger clause, satisfying the explicit-triggers anchor.

3 / 3

Trigger Term Quality

Natural terms users would say ('landing page', 'dashboard', 'colors', 'typography', 'accessibility', 'frontend interfaces') with good coverage, and the third-person 'This skill should be used when the user asks to...' voice avoids the first/second-person penalty.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear UI/UX-design niche with distinct triggers that are unlikely to fire for document, data, or code skills, matching the clear-niche anchor.

3 / 3

Total

12

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Galaxy-Dawn/claude-scholar
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.