CtrlK
BlogDocsLog inGet started
Tessl Logo

codex

A radically minimal, blank-canvas interface built as a pure edge-to-edge surface, with almost no color and typography carrying the visual weight. Black serves as the only filled color, the only divider, and the sole surface tone cards.

33

Quality

28%

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

Quality

Content

57%

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

The content is a well-structured, opinionated instruction skill with clear foundations, a sequenced authoring workflow, required output structure, and a QA checklist. It would benefit from removing the duplicated Brand section and adding one worked example of generated guidance.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet-point guidance that assumes Claude's competence, but the Brand section repeats the frontmatter description verbatim and a few rules could be tightened.

2 / 3

Actionability

Guidance is concrete and specific (required states listed, 'must'/'should' language, required output structure), but there are no worked examples of actual generated guidelines, leaving it one step short of copy-paste ready.

2 / 3

Workflow Clarity

The Guideline Authoring Workflow is a clear 6-step sequence ending in a QA checklist, but mid-process validation checkpoints are implicit rather than explicit feedback loops.

2 / 3

Progressive Disclosure

This is a single, well-organized SKILL.md (~75 lines) with clearly labeled sections and no nested or external references, which is appropriate for a self-contained skill of this size.

3 / 3

Total

9

/

12

Passed

Description

0%

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 a brand aesthetic statement rather than a skill description: it conveys no actions, no natural trigger terms, and no use-when guidance, so it fails to tell a user or Claude what the skill does or when to invoke it. It should be rewritten as a capability statement with explicit triggers.

Suggestions

Rewrite as a capability statement naming concrete actions, e.g. 'Authors implementation-ready design-system guidelines for the Codex brand...'.

Add an explicit 'Use when...' clause with natural trigger terms such as 'design system', 'brand guidelines', 'design tokens', or 'UI style rules'.

Use third-person voice focused on what the skill produces (guidelines, tokens, component rules) rather than describing the visual aesthetic.

DimensionReasoningScore

Specificity

The description ('A radically minimal, blank-canvas interface... typography carrying the visual weight') describes a visual aesthetic, not skill capabilities; no concrete actions (e.g. generate, apply, author) are named.

1 / 3

Completeness

It answers neither what the skill does (as a capability) nor when Claude should use it; there is no 'Use when...' clause or equivalent trigger guidance, capping completeness well below 2.

1 / 3

Trigger Term Quality

Terms like 'blank-canvas', 'edge-to-edge surface', 'typography' are design jargon, not the natural keywords a user would say to invoke this skill (e.g. 'design system', 'brand guidelines', 'design tokens', 'UI styles').

1 / 3

Distinctiveness Conflict Risk

With no capability or trigger framing, this reads as a generic design statement that would overlap with many UI/design skills and could trigger for the wrong one.

1 / 3

Total

4

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
bergside/awesome-design-skills
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.