CtrlK
BlogDocsLog inGet started
Tessl Logo

design-review

Designer Who Codes: visual audit then fixes with atomic commits and before/after screenshots. Useful for tightening shipped UI before launch.

52

Quality

57%

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

Quality

Content

40%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 thin catalogue entry that defers all real guidance to an external upstream repo, so it is structurally clean but lacks executable content and a real workflow. The skill advertises an audit/fix/commit/screenshot process that the body never actually instructs.

Suggestions

Inline at least a minimal executable workflow for the core task (e.g., how to run the visual audit, capture before/after screenshots, and make atomic commits) instead of only linking out.

Remove the verbatim repetition of the description under "What it does" or replace it with genuinely new detail to save tokens.

Add a validation checkpoint (e.g., confirm screenshots render and the build still passes before committing) since the skill performs UI changes and commits.

DimensionReasoningScore

Conciseness

The body is short, but it repeats the description verbatim under "What it does" and spends lines explaining the catalogue/advertising mechanism, which is mild padding a reader largely does not need.

3 / 5

Actionability

Guidance is high-level ("install the upstream bundle into your active agent's skills directory") with only a trivial `open https://...` command and no concrete steps for the actual audit/fix/commit/screenshot work.

2 / 5

Workflow Clarity

Only a rough meta-sequence (install bundle, open URL, invoke by name/triggers) is present, with no validation checkpoints for the fix-and-commit work the skill claims to perform.

2 / 5

Progressive Disclosure

The body is well organized into clear sections and signals a single one-level reference (the upstream GitHub URL); no local bundle files exist to verify further depth.

4 / 5

Total

11

/

20

Passed

Description

75%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, actionable, and covers both what and when with natural trigger phrases. It is held back from a top score by the slightly soft "Useful for" phrasing of the when-clause and minor generic wording around "fixes".

DimensionReasoningScore

Specificity

"visual audit then fixes with atomic commits and before/after screenshots" names the domain plus several concrete actions (audit, fix, commit, screenshot), with only minor gaps such as the generic word "fixes".

4 / 5

Completeness

It states what (visual audit + fixes + commits + screenshots) and gives a when ("Useful for tightening shipped UI before launch"), but the when is framed as "useful for" rather than an explicit "Use when..." clause so it could be sharper.

4 / 5

Trigger Term Quality

The frontmatter triggers ("design review", "visual audit", "before after", "pre launch design check") are natural phrases a user would say, with good synonym coverage but a few common variants missing.

4 / 5

Distinctiveness Conflict Risk

The design-audit-before-launch niche is fairly distinct with dedicated triggers, though "fixes with atomic commits" lightly overlaps with general code-change skills.

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.

Validation15 / 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
nexu-io/open-design
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.