CtrlK
BlogDocsLog inGet started
Tessl Logo

design-spec-review

Warn when user-facing UI changes drift from DESIGN.md. Advisory only; findings never gate Warden clearance.

56

Quality

64%

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/design-spec-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, actionable rule catalog with a clear review workflow and good sectioning, assuming Claude's competence throughout. It is held back only by minor redundancy and the lack of an explicit verification checkpoint.

DimensionReasoningScore

Conciseness

The body is dense with rule-specific checks and assumes Claude's competence (no explaining what React/CSS/tokens are); minor redundancy between the intro scope statement and the 'Do NOT report' section keeps it just shy of fully lean.

4 / 5

Actionability

Guidance is highly concrete — specific paths (apps/app/src/**), named primitives, exact anti-patterns (<div onClick>, CardDescription under CardTitle), and a grep command — with only minor gaps; absence of code is fine for this instruction-only review skill.

4 / 5

Workflow Clarity

A clear sequence exists (read DESIGN.md first → scope to changed user-facing lines → apply rule groups → use the report format), with a 'zero findings is valid' guardrail; only minor validation/checkpoint gaps remain.

4 / 5

Progressive Disclosure

Content is well-sectioned (What to check, Do NOT report, Report format) with no nested or buried references and no bundle files needed; being a self-contained ~100-line file rather than a <50-line simple skill keeps it at good-but-not-exemplary organization.

4 / 5

Total

16

/

20

Passed

Description

53%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 and distinctive about a narrow advisory role, but it omits an explicit 'Use when...' trigger clause, capping completeness and trigger-term quality. Adding concrete trigger phrases would lift the weaker dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing diffs that touch user-facing UI surfaces (apps/app/src, apps/desktop renderer, den-web, MCP App/artifact views).'

Surface 1-2 more concrete actions beyond 'warn' (e.g. 'cites numbered DESIGN.md rule ids in each finding') to broaden capability coverage.

Include natural user-facing synonyms (e.g. 'design-system drift', 'UI rule violations') to improve trigger-term quality.

DimensionReasoningScore

Specificity

"Warn when user-facing UI changes drift from DESIGN.md" names the domain (UI changes vs DESIGN.md) and one concrete action (warn), but offers no broader set of actions, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

The 'what' is clear (warn about UI drift from DESIGN.md) but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Relevant keywords ("user-facing UI changes", "DESIGN.md", "drift") appear, but common variations or explicit trigger phrases a user would naturally say are missing, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche is specific (DESIGN.md UI-rule drift, advisory-only, never gates Warden clearance) and mostly distinct from sibling review skills, with only minor overlap risk against general code/design review.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
different-ai/openwork
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.