CtrlK
BlogDocsLog inGet started
Tessl Logo

design

Canonical repo-local DESIGN.md workflow for product, UI/UX, and frontend decision source of truth

56

Quality

70%

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/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 lean, well-structured instruction skill with a clear sequenced workflow and concrete contract spec; its main gap is the absence of an example showing a filled-in DESIGN.md section.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; the inline required-sections list is the contract spec itself, not verbosity.

4 / 5

Actionability

A concrete 5-step workflow, explicit required DESIGN.md sections, specific interview-gap categories, and a completion checklist give mostly executable guidance; a filled-in section example would close the minor gap.

4 / 5

Workflow Clarity

Steps are clearly numbered (Discover, Interview, Create/refresh, Apply, Handoff) with an 'Evidence and completion' validation checklist; no destructive/batch ops so the cap is irrelevant, though explicit re-validate feedback loops are light.

4 / 5

Progressive Disclosure

Well-organized sections with one clearly signaled one-level reference (templates/AGENTS.md) and no bundle files; just short of 5 because the section template could optionally live in a reference file.

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 clearly identifies a distinct niche and deliverable but lacks explicit trigger guidance and concrete action verbs, leaving its 'when' underspecified.

Suggestions

Add a 'Use when ...' clause naming concrete trigger phrases (e.g., 'Use when creating a design brief, refreshing DESIGN.md, or deciding product/UI/frontend direction').

Replace the generic word 'workflow' with 2-3 concrete verbs (discover evidence, interview gaps, create/refresh DESIGN.md).

Include common synonyms users say ('design brief', 'design doc', 'design system') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("product, UI/UX, and frontend") and the deliverable ("DESIGN.md ... decision source of truth") but relies on the generic term "workflow" rather than enumerating concrete actions like discover, interview, or refresh.

3 / 5

Completeness

It gives a clear "what" but no "Use when..." trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms such as "product", "UI/UX", "frontend", and "design"/"DESIGN.md" are present, but common variations a user might say ("design brief", "design doc", "design system") are missing.

3 / 5

Distinctiveness Conflict Risk

The repo-local DESIGN.md governance niche is distinct and has clear triggers, with only minor overlap risk against the sibling $visual-ralph skill.

4 / 5

Total

13

/

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

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
Yeachan-Heo/oh-my-codex
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.