CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-ref-ui-polish

UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies frontend/UI domain work with production-grade "interface taste" rules. NOT for: backend logic, database design, DevOps, security audits, non-UI work.

Quality

81%

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

90%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 exceptionally tight, actionable reference: dense rule tables with exact values, no filler, and a coherent review-mode/severity/verdict structure with a verification checklist. Progressive disclosure is well executed with clearly signaled on-demand references, docked only for dangling cross-references inside design-audit.md and an implied rather than explicit review-step ordering.

DimensionReasoningScore

Conciseness

The body is dense rule tables with no padding and no explanation of concepts Claude already knows; every rationale is non-obvious domain judgment (e.g., "scale(0.96) on click — always 0.96 ... smaller than 0.95 (reads as a bug, not a press)").

5 / 5

Actionability

Guidance is copy-paste concrete throughout: exact values like "cubic-bezier(0.2, 0, 0, 1)", "44 × 44 px", "oklch(0 0 0 / 0.1)", "@media (hover: hover) and (pointer: fine)", and "font-variant-numeric: tabular-nums" cover the common cases; per the scoring notes, an instruction-only skill needs actionable guidance, not code, and this delivers it.

5 / 5

Workflow Clarity

The review procedure is well formed (Review Modes with finding caps → Severity levels → Verdict conditions, plus a Verification checklist), but the sequence is composed from separate tables rather than explicitly ordered steps, and the entry point ("identify the project's existing styling system" in Core Philosophy) is not connected to the review flow.

4 / 5

Progressive Disclosure

The two L3 references are real files, clearly signaled with load-on-demand conditions ("load on demand when motion is the substance of the work"), and the inline-rules vs. reference-depth split is appropriate; however, references/design-audit.md cites three files not present in the bundle (agent-common-protocol-reference.md, cache-aware-execution.md, verification-claim-integrity.md), leaving dangling referenced paths.

4 / 5

Total

18

/

20

Passed

Description

66%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 specific, well-scoped description with strong enumeration of covered topics and a useful exclusion list, but it buries its positive triggers: the "when to use" guidance lives in a separate when_to_use field rather than the description, capping completeness. Keywords are good though missing common synonyms like "animation" and "CSS".

Suggestions

Fold a positive trigger clause into the description itself (e.g., "Use when building or reviewing UI components, animations, shadows, hover states, or any visual/frontend detail work") so the 'when' is explicit where agent matching actually reads it.

Add natural user synonyms such as "animation", "CSS", "design system", and "hover/active states" alongside the current design-jargon terms like "optical alignment" and "tabular numbers".

State the skill's actions explicitly (e.g., "Reviews and polishes frontend code against interface-taste rules") rather than only naming the covered topics.

DimensionReasoningScore

Specificity

The description enumerates many concrete covered items ("concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas") but presents them as topic nouns rather than explicit actions, and "production-grade 'interface taste' rules" leans slightly on buzzword phrasing.

4 / 5

Completeness

The "what" is clear and detailed, but the description field contains no positive "Use when..." clause — only the exclusion list "NOT for: backend logic, database design, DevOps, security audits, non-UI work" — so per the rubric cap, positive trigger guidance is at best weakly implied.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("UI polish", "visual details", "interface", "motion", "typography", "hit areas", "frontend") that users would plausibly say, but common synonyms like "animation", "CSS", "hover states", and "design system" are absent.

4 / 5

Distinctiveness Conflict Risk

The visual-polish niche is well distinguished and the explicit "NOT for" list actively reduces conflict risk, but there is minor overlap with general frontend/design-system skills since the description's own positive scope ("frontend/UI domain work") is broad.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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

modu-ai/moai-adk

Path

.claude/skills/moai-ref-ui-polish/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.