CtrlK
BlogDocsLog inGet started
Tessl Logo

userinterface-wiki

UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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 lean, well-organized rule index that assumes Claude's competence, but it lacks in-document executable examples (deferring all code to rule files that are not present in the bundle) and the referenced files do not actually exist alongside SKILL.md. It scores well on conciseness and organization, lower on actionability and progressive disclosure.

Suggestions

Add at least one short executable code example in the body (or inline in the highest-priority sections) so the skill is actionable without loading an external file.

Provide the referenced rules/ directory and AGENTS.md so the progressive-disclosure pointers resolve to real files, or note clearly that rule files are generated/optional.

Reconcile the rule count: the intro says '152 rules across 12 categories' but several category lists contain more/fewer entries than implied; verify the total.

DimensionReasoningScore

Conciseness

The body is a dense index of terse one-line directives with no padding and no explanation of concepts Claude already knows (e.g., it never explains what CSS or springs are); every line carries a rule, so it is not the level-2 anchor of mostly-efficient-with-some-unnecessary-explanation.

3 / 3

Actionability

Rules are concrete directives ('User animations must complete within 300ms', 'Springs for overshoot-and-settle, not easing') but the body contains no executable code or commands, deferring examples to rule files; this matches the incomplete/pseudocode-level anchor rather than copy-paste-ready code.

2 / 3

Workflow Clarity

As a lookup/reference skill with no destructive multi-step process, it is clearly organized by priority with a 'How to Use' section explaining the rule-file structure; per the simple-skills note, clear organization earns a 3 without explicit validation checkpoints.

3 / 3

Progressive Disclosure

The overview points to one-level-deep references (rules/*.md, AGENTS.md) and signals them clearly, but no references/ or assets/ bundle exists and the referenced rules/ and AGENTS.md paths are absent, so the split is signaled but not actually provided — matching the level-2 anchor.

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 well-formed: third-person voice, explicit what-and-when triggers, and concrete review domains with a clear output format. It scores at the top of the scale on all four dimensions, with only a minor factual nit (it says 11 categories while the body lists 12).

Suggestions

Resolve the category count inconsistency: the description says 'Covers 11 categories' but the body's priority table and Quick Reference list 12 (including Visual Design).

DimensionReasoningScore

Specificity

Lists concrete review domains ('reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations') and a concrete output ('Outputs file:line findings'), matching the multiple-specific-actions anchor; it is not the level below which only names a domain without actions.

3 / 3

Completeness

Explicitly answers what ('UI/UX best practices for web interfaces' covering 11 categories) and when ('Use when reviewing animations, CSS, audio, typography...'), satisfying the what-and-when anchor rather than capping at 2 for an implied trigger.

3 / 3

Trigger Term Quality

Natural terms a user would say (animations, CSS, audio, typography, prefetching, icons) appear alongside an explicit 'Use when reviewing...' clause, giving good coverage of common variations rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

The narrow UI/UX web-review niche with specific triggers (animations, prefetching, typography, icons) makes it unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
gsd-build/gsd-2
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.