CtrlK
BlogDocsLog inGet started
Tessl Logo

improve-ui

Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

75

Quality

92%

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

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

The body is a tightly written, highly actionable audit workflow with explicit sequencing and validation checkpoints, supported by a single well-signaled reference file. Its only gap is minor cross-section redundancy that slightly dents conciseness.

Suggestions

Consolidate the repeated 're-open every cited source' instruction into one stated practice so sections 3, 4, and 6 reference it rather than restating it.

DimensionReasoningScore

Conciseness

The body is lean and directive with no re-teaching of concepts Claude knows, but the instruction to 're-open every cited source' recurs across sections 3, 4, and 6, introducing minor redundancy that could be tightened.

4 / 5

Actionability

Provides concrete, copy-paste-ready guidance: exact markdown templates for 'Design language' and a findings table with required columns, plus precise decision criteria (Contract, Runtime, Correction) and hard rules like 'Stop at three' and 'Delete any finding that does not include every required column'.

5 / 5

Workflow Clarity

The audit is a clearly numbered six-step sequence (Select → Reconstruct → Prove → Vet → Report → Specify) with explicit validation checkpoints: a three-proof gate in section 3 and a falsification pass that deletes unsupported candidates in section 4.

5 / 5

Progressive Disclosure

The SKILL.md is a well-organized process overview that signals one clearly-named, one-level-deep reference ('Read [references/plan-template.md]') to a real bundle file for the detailed plan format, keeping the overview navigable.

5 / 5

Total

19

/

20

Passed

Description

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

The description is specific, complete, and distinctive: it states concrete actions, provides explicit 'Use when' trigger guidance, and carves out a clear read-only design-audit niche. Its only weakness is moderate trigger-term coverage that leaves a few natural synonyms unsaid.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Audit an existing product surface against its own design evidence', 'identify verified UI problems', and 'write self-contained implementation plans for another agent' — covering the full audit-to-plan workflow comprehensively.

5 / 5

Completeness

Explicitly answers both what (audit, identify problems, write plans) and when ('Use when asked to review, refine, improve, or clean up an interface...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('review, refine, improve, or clean up an interface', 'investigate design-system drift', 'prepare a design handoff') but omits common synonyms such as 'polish', 'redesign', or 'audit UI'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — read-only design-surface audit producing implementation plans — with distinct triggers and constraints ('Strictly read-only on product source', 'without replacing its identity') that minimize overlap with general coding or refactor skills.

5 / 5

Total

19

/

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.