CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-design-craft

Intent-First design craft specialist covering design direction, domain vocabulary, design memory, and post-build critique. Use when establishing design intent or auditing code against design principles.

Quality

72%

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 ./.moai/archive/skills/v3.0/moai-design-craft/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-organized, lean, and genuinely actionable, with clear sequences and a verification checklist. The critical defect is that the progressive-disclosure architecture is broken: all four referenced module files are absent from the bundle, so the skill's primary navigation points to nothing.

Suggestions

Ship the four referenced files under modules/ (intent-first.md, design-memory.md, critique-workflow.md, web-copy-craft.md) or remove the Module Index and inline their essential content — the current references point to nonexistent files.

Add one worked example per headline formula (Number Anchor, Reversal, etc.) and a short template for the structure of a design-direction entry written to .moai/design/system.md.

Close the loop on the critique workflow: add an explicit step to re-verify the patched/rebuilt interface against the original intent, and define a concrete signal for choosing patch vs rebuild.

DimensionReasoningScore

Conciseness

The body is dominated by lean tables and terse numbered lists ("Identify 3–5 domain vocabulary terms", "verb-first, outcome-oriented, one per viewport") with no padding explaining concepts Claude already knows. Not 5 because the trailing "Version: 1.2.0 / Last Updated: 2026-03-30" duplicates frontmatter metadata (time-sensitive info penalized outside a deprecated section) and the Common Rationalizations table rows carry trimmable justification prose.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact file paths ("Read .moai/design/system.md"), quantities ("Define design intent in 1–3 sentences", "Identify 3–5 domain vocabulary terms"), named headline formulas ("Number Anchor, Reversal, Direct Question, Empathy Hook, Declaration"), and "Report violations with file:line references". Not 5 because the headline formulas are named but never exemplified and there is no template for what to actually write into system.md.

4 / 5

Workflow Clarity

Each of the three operations has a clearly numbered sequence, and the closing Verification checklist supplies explicit checkpoints ("Design direction documented before implementation begins", "Component names match the established design vocabulary"). Not 5 because there is no feedback loop after critique or audit (e.g. re-check the fix against intent) and the patch-vs-rebuild boundary, while gestured at ("small drift" vs "fundamental misalignment"), is never operationalized.

4 / 5

Progressive Disclosure

The Module Index is cleanly signaled and one level deep ("modules/intent-first.md", "modules/design-memory.md", "modules/critique-workflow.md", "modules/web-copy-craft.md"), but none of these files exist in the bundle — there is no modules/ directory at all, so the entire detail layer the structure promises is dangling. Per the guideline to score against the actual bundle structure, this broken disclosure chain sits at the minimal-structure level; only the inline Quick Reference summaries stand in for the missing files, keeping it above 1.

2 / 5

Total

14

/

20

Passed

Description

67%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 solid description with an explicit what-plus-when structure and a distinct niche framing. Its main weakness is trigger coverage: the when-clause names only two entry scenarios and never mentions web copy/UX writing even though that is a headline capability of the skill.

Suggestions

Expand the 'Use when' clause to cover all four claimed capabilities, e.g. add '...writing or reviewing web copy, headlines, and CTAs' and '...running a post-build design critique'.

Add natural trigger synonyms users would actually say — 'design review', 'design audit', 'critique my design/UI' — so the skill fires on common phrasings, not just 'design intent'.

Convert the noun-list of coverage areas into at least one concrete action verb phrasing (e.g. 'Captures design intent, aligns domain vocabulary, and audits implementations against the design memory') to strengthen specificity.

DimensionReasoningScore

Specificity

"covering design direction, domain vocabulary, design memory, and post-build critique" lists four specific capability areas rather than vague filler, matching the several-specific-actions anchor. It falls short of 5 because these are coverage areas named as nouns, not concrete operational actions, and stays above 3 because it enumerates four distinct capabilities rather than 1-2.

4 / 5

Completeness

Both halves are explicit: the what ("Intent-First design craft specialist covering design direction, domain vocabulary, design memory, and post-build critique") and the when ("Use when establishing design intent or auditing code against design principles"). Not 5 because the when-clause covers only two scenarios and omits triggers for the post-build critique and web-copy capabilities it claims; not 3 because the Use-when clause is present and explicit.

4 / 5

Trigger Term Quality

"Use when establishing design intent or auditing code against design principles" supplies some natural phrases ("design intent", "auditing code"), but misses common variations users would say such as "design review", "design audit", "critique my UI", or "web copy" — the latter being a whole module of the skill the when-clause never triggers on. This matches the some-relevant-keywords-but-missing-variants anchor, not 4, which requires only a few natural terms missing.

3 / 5

Distinctiveness Conflict Risk

"Intent-First design craft specialist" carves a clear niche with intent-audit triggers unlikely to fire for unrelated skills, matching the mostly-distinct anchor. Not 5 because "auditing code against design principles" and general design language carry minor overlap risk with closely adjacent design/UI-UX skills — the body itself lists three such neighbors needing "complementary, not overlapping" disclaimers.

4 / 5

Total

15

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

modu-ai/moai-adk

Path

.moai/archive/skills/v3.0/moai-design-craft/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.