CtrlK
BlogDocsLog inGet started
Tessl Logo

web-design-guidelines

前端 UI 审查清单:可读性、视觉密度、间距、响应式、空状态、加载态和可访问性。

59

Quality

67%

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 ./skills/web-design-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 review checklist with a clear output contract and good workflow clarity for a simple skill. The main gap is actionability: criteria are concrete but lack specific thresholds or example fixes.

Suggestions

Add a couple of concrete pass/fail thresholds or examples per high-impact category (e.g. target contrast ratios, line-length ranges, tap-target sizes) so reviews are less subjective.

Include one short example of the expected Output block (a sample pass/fail summary with a top issue and concrete fix) to make the deliverable copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a tight checklist with one-line criteria per category and a defined output spec, with no padding or explanation of concepts Claude already knows. The only mild extra is the short PilotDeck migration note, which is negligible.

3 / 3

Actionability

Each checklist item gives concrete sub-criteria (e.g. 'keyboard focus, labels, alt text, contrast, reduced motion') and the Output section defines what to return, but it stops short of specific thresholds or concrete example fixes, leaving the guidance somewhat general.

2 / 3

Workflow Clarity

This is a simple, single-purpose review skill whose flow is unambiguous: review against the eight checklist dimensions, then return the specified output. Per the simple-skills note, a clear well-organized single-purpose workflow scores 3, and no destructive/batch feedback loop is required for a read-only review.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/scripts/assets are absent) and is organized into clear sections (Checklist, Output, Migration Note), satisfying the simple-skills progressive-disclosure criterion.

3 / 3

Total

11

/

12

Passed

Description

50%

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 concise and names a clear domain with several concrete review dimensions, but it lacks an explicit 'Use when...' trigger clause and relies on checklist topics rather than concrete actions. It is a competent but incomplete description.

Suggestions

Add an explicit trigger clause, e.g. 'Use after building or modifying web UI, or when the user asks for a UI/design review, UI audit, or polish pass.'

Lead with concrete review actions (e.g. 'Reviews front-end UI for readability, spacing, responsiveness, and accessibility') rather than framing it only as a checklist.

Include more natural trigger variations users would say ('UI review', 'design QA', 'polish the interface', 'check empty/loading states').

DimensionReasoningScore

Specificity

The description names the domain ('前端 UI 审查清单') and lists seven concrete review areas (readability, visual density, spacing, responsiveness, empty states, loading states, accessibility), but these are checklist topics rather than concrete actions/verbs, so it stops short of the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It states what the skill does (a front-end UI review checklist across these dimensions) but provides no explicit 'Use when...' trigger guidance, so the 'when' is only implied — capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

It includes relevant natural UI terms a user might say ('UI 审查', '可读性', '响应式', '可访问性'), but misses common variations such as 'UI audit', 'design review', 'polish', or 'design QA', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The 'front-end UI review' niche is reasonably specific, but a generic review/checklist framing could still overlap with general code-review or design skills, so it is not yet a clearly distinct trigger set.

2 / 3

Total

8

/

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
OpenBMB/PilotDeck
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.