CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visual-design

Guides and reviews visual design and brand identity for web and React Native UI — color, typography, hierarchy, and named style directions — deferring contrast math and a11y mechanics to /ux. Triggers on "make this look good", "visual design", "style direction", "does this look generic", "/visual-design".

Quality

79%

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

Quality

Content

63%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 well-structured advisory skill: clear mode detection, a sequenced four-phase workflow, concrete output templates, and deliberate progressive-disclosure design. Its two real weaknesses are that the referenced rules/ and templates/ files are not shipped with the bundle (making the index point at nothing) and that deferral/composability guidance is restated several times.

Suggestions

Ship the referenced bundle files: create rules/ (style-directions, brand-identity, visual-hierarchy, color-systems, typography-pairing, signature-details, style-audit) and templates/direction-brief.md, or inline the essential content — the per-mode loading table currently points at files that do not exist.

State the /ux deferral once (e.g., keep the 'What this skill defers' list, drop the intro restatement and Behavioral Rule 8) to recover token budget in a SKILL.md that positions itself as a thin index.

Add a lightweight verification checkpoint to Phase 4 — e.g., confirm every recommended token actually exists in the project's theme/tokens file before emitting the build sheet.

DimensionReasoningScore

Conciseness

The body is dense and instructive with no padding about concepts Claude already knows, but guidance is repeated: the /ux deferral appears four times (intro prose, the Phase 3 table, the six-bullet "What this skill defers" list, Behavioral Rule 8), and the thin-index note appears twice (blockquote plus "Do not pre-load all rules. The progressive-disclosure cost is real."). Could be tightened by stating each once; not 2 because there is no fluff or over-explanation.

3 / 5

Actionability

Concrete, executable guidance throughout: exact mode-detection trigger tokens, platform heuristics ("View, Text, Pressable, expo-router"; "git diff --name-only HEAD~1"), a complete copy-paste build-sheet output template, and a findings format ("cite file:line, the named principle ... a concrete fix with code"). Not 5 because the substantive rules (named directions, palette construction, pairings) are all deferred to referenced files rather than exemplified inline.

4 / 5

Workflow Clarity

A clearly sequenced four-phase workflow (context discovery → load rules by mode → compose with siblings → output) with mode detection up front and explicit decision checkpoints ("If ambiguous, ask"; "Do not review or generate code you have not read"). Not 5 because there is no verification step on the output (e.g., confirming recommended tokens exist in the project's theme); not 3 because checkpoints like ask-when-ambiguous and read-before-review are explicit.

4 / 5

Progressive Disclosure

The body is a well-signaled, one-level-deep index with an excellent per-mode loading table — but scored against the actual bundle, none of the eight referenced files (rules/style-directions.md, rules/brand-identity.md, rules/visual-hierarchy.md, rules/color-systems.md, rules/typography-pairing.md, rules/signature-details.md, rules/style-audit.md, templates/direction-brief.md) exist, so every Phase 2 load fails. Structure and signaling are good, but the disclosure chain is broken as shipped.

3 / 5

Total

14

/

20

Passed

Description

87%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: it states concrete capabilities with a scope (web and React Native UI), gives an explicit trigger clause with natural user phrases, and actively disambiguates from the adjacent /ux skill. The only weakness is slightly incomplete enumeration of what the skill owns (signature details, style audit) and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Names two concrete actions ("Guides and reviews visual design and brand identity") plus enumerated concern areas ("color, typography, hierarchy, and named style directions") and an explicit boundary ("deferring contrast math and a11y mechanics to /ux"). Falls just short of the 5 anchor because coverage has minor gaps — e.g., signature details and style audit, which the body owns, are not mentioned.

4 / 5

Completeness

Clearly answers both what ("Guides and reviews visual design and brand identity ... color, typography, hierarchy, and named style directions") and when ("Triggers on 'make this look good', 'visual design', 'style direction', 'does this look generic', '/visual-design'") with concrete trigger phrases — a direct match for the 5 anchor, not the 4 anchor whose 'when' is only adequate.

5 / 5

Trigger Term Quality

Triggers on "make this look good", "does this look generic", "visual design", "style direction" — natural phrases a user would actually say, including the aesthetic-quality framing. A few common synonyms are missing (e.g., "make it pretty", "polish", "branding"), which keeps it at the 4 anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — the generative, brand-aware side of visual work — and explicitly disambiguates from the nearest neighbor ("deferring contrast math and a11y mechanics to /ux"), so the risk of triggering for a mechanics/a11y request is minimal. Not 4, because the boundary with the closely-related /ux skill is drawn explicitly in the description itself.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

mthines/agent-skills

Path

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