CtrlK
BlogDocsLog inGet started
Tessl Logo

design

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

64

Quality

75%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear sequenced workflow and validation checklist, but it carries verbosity in the comparison sections and keeps a large inline template rather than splitting it into a reference file.

Suggestions

Move the full DESIGN.md structure template into a references/ file (e.g. DESIGN_TEMPLATE.md) and summarize the required sections inline in SKILL.md.

Tighten the 'Relationship to $visual-ralph' and 'Do not use when' sections to the minimal distinguishing statements needed for routing.

DimensionReasoningScore

Conciseness

The prose is directive and avoids explaining concepts Claude already knows, but the relationship-to-$visual-ralph and do-not-use-when sections plus the inline template add length that could be tightened.

2 / 3

Actionability

Concrete, copy-paste-ready guidance throughout: specific file-pattern discovery lists, focused interview prompts, a complete DESIGN.md section template, and an explicit completion checklist.

3 / 3

Workflow Clarity

A clear five-step sequence with a validation-style completion checklist and an explicit contradiction-handling feedback loop in step 4 ('update DESIGN.md or add an open question before proceeding').

3 / 3

Progressive Disclosure

Sections are well organized, but the ~80-line DESIGN.md template is inline with no reference files to offload detail, so content that could be split remains in SKILL.md.

2 / 3

Total

10

/

12

Passed

Description

72%

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 distinctive and uses natural trigger terms, but it states purpose rather than concrete actions and omits an explicit use-when trigger, leaving completeness and specificity at the mid level.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when creating or refreshing a repo DESIGN.md for product/UI/UX/frontend decisions').

Replace the abstract 'workflow for ... decision source of truth' phrasing with concrete verbs such as discovers, interviews, creates, and refreshes to raise specificity.

DimensionReasoningScore

Specificity

The description names a concrete domain and artifact ("repo-local DESIGN.md workflow for product, UI/UX, and frontend") but does not enumerate concrete actions like creates/interviews/refreshes, so it is more purpose-statement than action-list.

2 / 3

Completeness

It clearly states what the skill does (DESIGN.md source of truth) but lacks an explicit "Use when..." trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Natural user-facing terms are well covered ("product, UI/UX, frontend, design, DESIGN.md"), matching phrases a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The narrow framing of a repo-local design decision source of truth carves a clear niche distinct from generic skills and from the visual-implementation scope of $visual-ralph.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.