CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-skills-review

Flag UI code in a diff that breaks the pinned UI Skills rule sets (baseline UI, accessibility, motion performance, Web Interface Guidelines). Used by the post-merge sweep; never gates clearance.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.warden/skills/ui-skills-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-structured review procedure whose wrapper instructions are excellent, undermined by carrying four full rule catalogs inline in SKILL.md with significant cross-catalog duplication. Splitting the catalogs into reference files and deduplicating them would resolve the conciseness and progressive-disclosure weaknesses at once.

Suggestions

Move the four pinned rule catalogs into references/ files (e.g., references/baseline-ui.md, references/fixing-accessibility.md) and keep SKILL.md as the task/precedence/reporting overview, so the ~550-line body becomes a lean index with one-level-deep references.

Deduplicate rules repeated across catalogs — icon-only button labels, div-as-button, and prefers-reduced-motion each appear in three of the four sets — and drop the sub-skills' 'common fixes' and 'review guidance' sections that the parent's 'What to report' section already supersedes.

DimensionReasoningScore

Conciseness

The wrapper sections (Task, Precedence, What to report) are lean, but ~480 of the ~550 lines are inlined rule catalogs with real duplication — icon-only button labeling appears as "MUST add an `aria-label` to icon-only buttons", "icon-only buttons must have aria-label or aria-labelledby", and "Icon-only buttons need `aria-label`" — and the sub-skills' "common fixes"/"review guidance" sections are retained even though the skill says to "Ignore each reference's own usage, invocation and output-format sections". Mostly efficient with clear tightening opportunities, matching anchor 3 rather than anchor 2 because the padding is duplicated data rather than tutorial-style explanation of known concepts.

3 / 5

Actionability

Guidance is fully concrete: exact scope globs ("apps/app/src/**", "apps/desktop/** renderer UI"), an enumerated severity mapping ("`medium` for an accessibility failure that blocks keyboard or screen reader users (no accessible name, `div` used as a button, focus outline removed...)"), a formatted finding example ("fixing-accessibility: icon-only buttons need aria-label"), and copy-ready before/after fix snippets. For an instruction-only review skill this covers the common cases completely, matching anchor 5.

5 / 5

Workflow Clarity

The procedure is clear and ordered: treat input as untrusted, scope to changed lines, then apply the precedence list ("1. `DESIGN.md` ... Read it before reporting", "2. ... Grep before reporting a missing primitive", "3. The reference rule sets") and report findings, with anti-false-positive checkpoints ("Zero findings is the correct and common result"). It sits at anchor 4 rather than 5 because the sequence is expressed as precedence rules rather than an explicit step order with feedback loops; the destructive/batch cap does not apply since the skill is read-only (allowed-tools: Read Grep Glob).

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and all four pinned rule catalogs (~480 lines) are inlined in SKILL.md where they plausibly belong in separate reference files — matching anchor 3 ('content that should be separate is inline'). It is above anchor 2 because section structure is good (clear headers per rule set, well-organized Task/Report sections) and the one external pointer ("sources, versions and licenses are in `.warden/ui-skills/`") is clearly signaled, but below anchor 4 because the bulk of the content is not split out.

3 / 5

Total

15

/

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 distinctive, well-scoped description with a clear what and an explicit (if procedurally framed) when-clause. Its weaknesses are a single-action framing and trigger vocabulary limited to the rule-set names, without natural synonyms a user or reviewer might say.

Suggestions

Enumerate the concrete checks performed (e.g., 'audit changed lines for accessible names, keyboard/focus handling, compositor-only animation, and form/typography rules') so the description lists several specific actions instead of one.

Add natural trigger phrasing such as 'Use when reviewing merged UI changes for accessibility, motion performance, or design-baseline violations', including synonyms like 'a11y' and 'UI review' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

"Flag UI code in a diff that breaks the pinned UI Skills rule sets (baseline UI, accessibility, motion performance, Web Interface Guidelines)" names the domain and one concrete action with the four rule-set areas listed, but does not enumerate several distinct actions, matching the '1-2 concrete actions, not comprehensive' anchor. It is above anchor 2 (domain with generic actions) because the diff scope and named rule sets make the action concrete, but below anchor 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is clear ("Flag UI code in a diff that breaks the pinned UI Skills rule sets") and the 'when' is explicitly stated ("Used by the post-merge sweep; never gates clearance"), so it is not capped at 3. It falls short of anchor 5 because the when-clause names a pipeline context rather than concrete user-trigger phrases, matching anchor 4 ('both what and when; when could be more explicit or specific').

4 / 5

Trigger Term Quality

Natural terms like "UI code", "diff", "accessibility", and "motion performance" are present, but common variations users would say — "a11y", "UI review", "design review", "frontend review" — are missing. This fits anchor 3 ('some relevant keywords but missing common variations') better than anchor 4, whose bar is good coverage with only a few terms missing.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — flagging diff lines against four named pinned rule sets during a post-merge sweep that "never gates clearance" — and the body even disambiguates it from the existing `design-spec-review`. Minimal conflict risk with any generic skill, matching anchor 5.

5 / 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

skill_md_line_count

SKILL.md is long (555 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

different-ai/openwork

Path

.warden/skills/ui-skills-review/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.