CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

styleseed-design-review

Reviews UI/frontend code and tells you exactly why it "looks AI-generated" — then how to fix it. Use it when a React/Tailwind/HTML interface looks off, generic, or unfinished, when you want a design score before shipping, or when asked to make UI look more professional, polished, or...

Quality

86%

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

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

This is a tightly written, highly actionable review skill: a concrete evidence-based scoring rubric with exact deductions, a complete output template, prioritized fix guidance, and a built-in re-review feedback loop with an explicit non-destructive boundary. The only weaknesses are minor — a duplicated external repo link and a generic boilerplate Limitations section that adds no skill-specific value.

DimensionReasoningScore

Conciseness

The core scoring rubric is dense and high-value — point-valued deductions ('−6', 'cap −8'), concrete thresholds ('~#2A2A2A', '4.5:1 body', '8px scale') — with no explanations of concepts Claude already knows. Minor trimmable padding keeps it below 5: the GitHub URL is repeated in both the Overview and the closing attribution block, and the 'Limitations' section is generic boilerplate (e.g. 'Verify commands, generated code, dependencies, credentials') unrelated to this skill's actual read-only review workflow.

4 / 5

Actionability

As an instruction-only skill the guidance is fully executable: seven weighted categories summing to 100, exact per-violation deductions with caps, scoring bands ('90+ A · 80–89 B'), and a complete copy-paste output template with a worked example including fix-priority line items and re-score projection. This exceeds the score-4 anchor and matches the common-cases coverage of score 5.

5 / 5

Workflow Clarity

The process is clearly sequenced with explicit validation and a feedback loop: 'Read the file(s)', score 'start each at full marks and subtract for violations you can cite by line', 'Clamp each category at 0; sum to a total', order fixes 'by score gain', then 're-review until the score clears ~80'. Evidence-by-line-number citations act as checkpoints, and the skill is explicitly non-destructive ('Don't auto-edit'), so no destructive-validation cap applies.

5 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), so this scores on the single-file structure: sections are well organized (Overview, When to use, How to review, Output format, Rules) and the external 74-rule reference is clearly signaled ('Full rule set (74 rules) and components: https://github.com/bitjaru/styleseed') at one level deep. It stays at 4 rather than 5 because that link is stated twice (Overview and footer) and the fuller rule set lives entirely outside the skill rather than in an bundled, clearly-signaled reference file.

4 / 5

Total

18

/

20

Passed

Description

78%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 strong description that explicitly states both capability and trigger conditions with natural, specific phrasing and a well-defined niche. Its main deductions are the second-person 'tells you' in the capability clause (voice penalty) and a truncated trailing trigger ('...polished, or...') that leaves the final clause dangling.

Suggestions

Rewrite the capability clause in third person to avoid the voice penalty and sharpen the action list, e.g. 'Reviews React/Tailwind/HTML UI code, diagnoses exactly why it looks AI-generated (mixed radii, color noise, missing states), scores it 0–100, and returns a prioritized fix list.'

Complete or trim the truncated final trigger so the description does not end on a dangling 'or...' — either finish the list ('...professional, polished, or designed') or cut it at 'polished'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Reviews UI/frontend code and tells you exactly why it "looks AI-generated" — then how to fix it' — which fits the score-4 anchor (several specific actions, minor gaps), but the capability clause uses second person ('tells you'), which the rubric penalizes by reducing specificity by 1, landing at 3. It is above score 3's base bar of only 1–2 actions only before the voice penalty applies.

3 / 5

Completeness

Both parts are explicit: 'what' is 'Reviews UI/frontend code and tells you exactly why it "looks AI-generated" — then how to fix it', and 'when' is a concrete 'Use it when' clause with three trigger scenarios (interface looks off/generic/unfinished, pre-ship design score, asked to make UI professional/polished). The trailing truncated 'or...' is a cosmetic flaw but all stated triggers are complete, so it is not the score-4 case of an only-implicitly-specified 'when'.

5 / 5

Trigger Term Quality

Natural trigger phrases are well covered: 'looks off, generic, or unfinished', 'design score before shipping', 'make UI look more professional, polished', plus stack terms 'React/Tailwind/HTML'. A few natural variations users might say (e.g. 'pretty', 'modern', 'design review') are missing, so it does not reach the comprehensive synonym coverage of score 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — diagnosing the 'AI-generated' look in React/Tailwind/HTML UIs and design scoring — with distinct triggers, so it is mostly distinguishable. It carries minor overlap risk with general frontend-styling or design-system skills that could also fire on 'make the UI look professional', keeping it below score 5.

4 / 5

Total

16

/

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

BigSimmo/Communication

Path

.agents/skills/styleseed-design-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.