CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-design

Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A lean, well-structured router skill with a clearly sequenced workflow, a validation checkpoint, a failure-recovery table, and concrete guardrails (WCAG AA default, CJK glyph coverage). Its main weaknesses are minor duplication between the trigger sections, abstract phrasing in a few directives, and a reference chain that rests entirely on files not present in the bundle.

Suggestions

Merge the overlapping 'Intent signature' and 'When to use' sections into a single trigger list to remove the duplicated phrasing about visual systems, design direction, and typography/color/layout/motion.

Inline the two or three highest-value checks from `resources/checklist.md` at the step-4 validation point so the checkpoint is actionable even before the reference file is loaded.

Add one concrete worked example of a resolved supplier selection and handoff (e.g., brief -> Taste -> DESIGN.md delta -> checklist result -> frontend handoff) to ground the abstract routing directives in 'Transitions'.

DimensionReasoningScore

Conciseness

The body is dense and telegraphic with no explanations of concepts Claude already knows ("Keep WCAG AA as the default accessibility target", "A chosen GPU effect, cinematic video-scroll scene, or GSAP behavior adds the matching frontend implementation extension"). It is not 5 because the "Intent signature" and "When to use" sections restate the same triggers (visual system / design direction, typography, color, layout, motion) and could be merged; it is well above 3 since there is no padding or over-explanation.

4 / 5

Actionability

Concrete guidance for an instruction-only router skill: a four-step canonical path with specific file paths ("Use `resources/external-design-skills.md`", "Check the affected result using `resources/checklist.md`"), named supplier operations (Interface Design `design-review`, Taste, Impeccable), and a failure/recovery table. It falls short of anchor 5 because some directives remain abstract ("Resolve project design intent") and the executable detail lives entirely in referenced files, but it is well above anchor 3's vague/pseudocode level.

4 / 5

Workflow Clarity

The canonical workflow (inspect -> select supplier -> apply -> check -> hand off) is clearly sequenced, with a validation checkpoint (step 4 checklist), feedback loops ("Failure and recovery" table with concrete recoveries like "Report the gate as unrun; do not replace it with a claimed pass"), and explicit exit criteria. It stays at anchor 4 rather than 5 because the validation step's actual checks and failure handling are delegated to referenced files rather than stated inline, leaving minor checkpoint gaps.

4 / 5

Progressive Disclosure

The body is an overview with fourteen clearly signaled, one-level-deep references, each annotated with a one-line description in the References section (e.g., "`resources/checklist.md`: affected-result verification and evidence"), and operational detail appropriately deferred to those files. It is not 5 because the bundle ships no reference files at all (no references/, scripts/, or assets/ directories exist), so the referenced `resources/...` paths — and the cross-skill `../oma-frontend` and `../_shared` paths — cannot be verified, leaving navigation dependent on unconfirmed files.

4 / 5

Total

16

/

20

Passed

Description

83%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.

A concise, third-person description that explicitly answers both what the skill does and when to use it, with concrete domain triggers and a distinctive DESIGN.md artifact hook. It narrowly misses top marks only on trigger-synonym coverage and minor overlap with sibling implementation skills.

DimensionReasoningScore

Specificity

"Define or review a visual system, DESIGN.md, or redesign direction" names concrete actions and objects, and the trigger clause enumerates five design domains ("typography, layout, color, motion, and interaction design"). This matches 'lists several specific actions; minor gaps in coverage' — it stops short of 5 because capabilities like extracting design systems from existing UI/screenshots (covered in the body) are absent from the description, and exceeds 3 because coverage goes beyond 1-2 generic actions.

4 / 5

Completeness

Both parts are explicit: what ("Define or review a visual system, DESIGN.md, or redesign direction") and when ("Use for typography, layout, color, motion, and interaction design decisions") with concrete trigger phrases. This mirrors the anchor-5 pattern of an action sentence plus an explicit 'Use for...' clause with concrete triggers; it is not anchor 4 because the when-clause is explicit and specific rather than weakly implied.

5 / 5

Trigger Term Quality

Natural user terms are present: "redesign", "typography", "layout", "color", "motion", and the distinctive file trigger "DESIGN.md". Good coverage but a few natural synonyms are missing ("design system", "UI", "style guide", "brand"), so it fits anchor 4 rather than the comprehensive synonym-level coverage of anchor 5, and is clearly above the sparse keyword coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

The pre-implementation design niche and the DESIGN.md artifact give it a clear lane ("design decisions" vs. implementation), but "layout" and "interaction design decisions" carry minor overlap risk with sibling frontend/mobile implementation skills in the same family. Mostly distinct with minor overlap risk — anchor 4 rather than 5's minimal-conflict clear niche.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

first-fluke/oh-my-agent

Path

.agents/skills/oma-design/SKILL.md

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.