CtrlK
BlogDocsLog inGet started
Tessl Logo

baseline-ui

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

70

Quality

85%

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

82%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 efficient, highly actionable constraints checklist with clean sectioning and a clear invocation workflow. The main gap is the absence of any inline good/bad code examples to anchor the directives.

Suggestions

Add 1–2 short before/after code snippets illustrating a typical violation and its fix to make the review pass concrete.

Show an example output of `/baseline-ui <file>` (violation + why-it-matters + fix) so the review format is unambiguous.

Consider moving the full Tailwind z-index scale or component-primitive list into a reference file to keep the body lean and enable progressive disclosure.

DimensionReasoningScore

Conciseness

Every line is a lean directive with no padding or explanation of concepts Claude already knows (Tailwind, animation, accessibility); each token earns its place.

5 / 5

Actionability

Directives are concrete and executable (specific classes like `h-dvh`, libraries like `motion/react`, thresholds like `200ms`), but no inline code examples show correct vs. incorrect application for the instruction-only guidance.

4 / 5

Workflow Clarity

The "How to use" section gives an unambiguous single-purpose workflow with a defined review output format (violations, why it matters, fix), though it lacks explicit validation checkpoints; no destructive ops require them.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Stack, Components, Animation, etc.) with no external references needed, but at ~80 lines it slightly exceeds the simple-skill threshold where sectioning alone would merit a 5.

4 / 5

Total

17

/

20

Passed

Description

88%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 tight, well-structured description that cleanly answers what and when with concrete actions and natural triggers. The only weakness is the coined term "deslop," which users are unlikely to say verbatim.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions — "fixing spacing, hierarchy, typography, and small layout issues" — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ("deslop UI code by fixing spacing, hierarchy, typography, and small layout issues") and when ("Use when the interface needs a fast cleanup or polish pass") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

"cleanup", "polish pass", and "interface" are natural terms users would say, but the coined verb "deslop" is not a phrase users naturally utter and common synonyms (tidy, fix up) are absent.

4 / 5

Distinctiveness Conflict Risk

The UI-polish niche (spacing, hierarchy, typography) is mostly distinct with clear triggers, though it has minor overlap risk with general code-formatting or lint skills.

4 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ibelick/ui-skills
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.