CtrlK
BlogDocsLog inGet started
Tessl Logo

design

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

58

Quality

68%

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 ./plugins/oh-my-codex/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 well-structured, lean instruction-only skill with a clear sequenced workflow, concrete deliverable template, and an explicit completion checklist. The main improvement is making per-step validation checkpoints inline rather than relegating all verification to the closing checklist.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using terse imperatives and offloading shared invariants to AGENTS.md; minor redundancy between 'Use when', 'Do not use it for', and 'Relationship to $visual-ralph' keeps it just short of a 5.

4 / 5

Actionability

It gives concrete, specific guidance — an exact list of evidence sources to inspect and a copy-paste-ready required-section template for DESIGN.md — with only minor gaps such as no worked example snippet.

4 / 5

Workflow Clarity

A clear five-step sequence (Discover, Interview, Create/refresh, Apply, Handoff) is backed by an explicit completion checklist and a contradiction-feedback loop in step 4, though per-step validation is implied rather than framed as inline checkpoints.

4 / 5

Progressive Disclosure

Structure is clean with a single clearly-signaled one-level reference to templates/AGENTS.md and no nested/deep references; the inlined required-section template is long but legitimately belongs as the contract spec.

4 / 5

Total

16

/

20

Passed

Description

61%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 largely distinct, but it states only the "what" and omits explicit "when to use" trigger guidance, which the rubric caps at completeness 3. Adding a Use-when clause with natural trigger phrases would lift the weakest dimension.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when a feature needs a repo-local design brief before implementation, or when product/UI/UX/frontend decisions need a durable source of truth.'

Add natural synonyms users actually say — 'design brief', 'design system', 'wireframe', 'mockup', 'style guide' — to broaden trigger coverage.

Replace the abstract word 'workflow' with 1-2 concrete verbs (e.g. 'discover, interview, and maintain') to raise specificity.

DimensionReasoningScore

Specificity

The description names a concrete domain and deliverable ("repo-local DESIGN.md" as a "decision source of truth") but uses the generic term "workflow" rather than enumerating specific actions like discover, interview, or refresh.

3 / 5

Completeness

It gives a clear "what" (a canonical DESIGN.md decision source of truth) but lacks any "Use when..." trigger clause, so per the rubric guidance completeness is capped at 3.

3 / 5

Trigger Term Quality

It surfaces natural terms users would say ("product, UI/UX, and frontend", "DESIGN.md", "design") but omits common synonyms such as design brief, wireframe, mockup, or style guide.

4 / 5

Distinctiveness Conflict Risk

The design-governance niche is mostly distinct, with only minor overlap risk against the closely related $visual-ralph implementation skill referenced in the body.

4 / 5

Total

14

/

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.

Validation14 / 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.