CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-design-tools

Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.

Quality

77%

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

Quality

Content

63%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 delivers concrete, well-sequenced guidance for all three tools — commands, tool tables, decision guides, and verification checkpoints — but generic best-practice filler inflates the token budget, and all four referenced detail files are missing from the bundle, breaking progressive disclosure entirely.

Suggestions

Trim or remove the 'Common Design-to-Code Patterns' and 'Workflow Best Practices' sections: statements like 'All tools handle responsive layouts' and 'Create pull requests for design changes' restate knowledge Claude already has and add ~40 lines of padding without tool-specific instruction.

Create the four referenced files (reference/figma.md, reference/pencil-renderer.md, reference/pencil-code.md, reference/comparison.md) or remove the references and Navigation Guide steps that point to them — currently every instruction to 'open tool-specific reference file' dead-ends.

Drop the trailing metadata block ('Status: Active / Version: 5.1.0... / Last Updated: 2026-04-05') and inline version numbers (schema v2.9, CLI v0.2.4) from the body: they duplicate frontmatter fields and go stale; if version-specific behavior matters, confine it to a dedicated compatibility note.

DimensionReasoningScore

Conciseness

Core tool sections are dense (tool tables, install commands, workflows), but generic filler pads the body: 'All tools handle responsive layouts', 'Use Figma comments for design feedback', 'Create pull requests for design changes' restate what Claude already knows; the trailing metadata block ('Status: Active / Version: 5.1.0 (Pencil docs sync — schema v2.9, CLI v0.2.4...)') duplicates frontmatter, and time-sensitive version numbers sit outside any deprecated/old-patterns section. Fits 'mostly efficient but includes some unnecessary explanation'; not 2 because the majority of sections are tight tables and commands.

3 / 5

Actionability

Mostly executable guidance: copy-paste commands ('bunx --bun shadcn@latest create --preset "https://ui.shadcn.com/init?..."', 'claude plugin install figma@claude-plugins-official', 'pencil login') and specific tool calls with arguments ('open_document(filePathOrNew: "new")', 'find_empty_space_on_canvas(direction: "right", size: { w: 200, h: 100 })'). Not 5 because batch_design syntax uses '{ ... }' placeholders rather than a complete runnable example, and the Pencil-to-code step 'Map to React/Tailwind' lacks any concrete code sample.

4 / 5

Workflow Clarity

Clear sequences with validation checkpoints: 'Generate design with batch_design → Visually review with get_screenshot → Iterate on design', 'Verify against screenshot' in both the Figma and export workflows, plus a final verification checklist ('Implementation matches design file at all breakpoints'). Batch operations do have a validation loop (get_screenshot review), so the destructive/batch cap at 3 does not apply; not 5 because there is no error-recovery guidance when visual review reveals problems.

4 / 5

Progressive Disclosure

References are clearly signaled — each of reference/figma.md, reference/pencil-renderer.md, reference/pencil-code.md, reference/comparison.md gets a description and 'Key sections' list, backed by a numbered Navigation Guide — but none of these files exist in the bundle (no references/ directory is present), so every 'Open tool-specific reference file for implementation details' instruction dead-ends. Good in-body structure, but the disclosure structure is broken by missing files, fitting 'some structure but could be better organized'; not 4 because clearly-signaled references to nonexistent content undermine navigation.

3 / 5

Total

14

/

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 strong, third-person description that names three specific capabilities and tools and includes an explicit 'Use when' clause with concrete triggers. Minor gaps: missing common synonyms like '.pen files' or 'design to code', and the React/Tailwind export trigger slightly overlaps with general frontend skills.

DimensionReasoningScore

Specificity

Names concrete capabilities — 'covering Figma MCP, Pencil renderer, and Pencil-to-code export' — and three specific actions: 'fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code'. Matches the 'several specific actions; minor gaps' anchor rather than 5 because coverage of the full capability set (16 Figma tools, FigJam, Code Connect, design tokens) is incomplete, and rather than 3 because it goes beyond 1-2 actions.

4 / 5

Completeness

The 'what' is explicit ('Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export') and the 'when' is an explicit 'Use when' clause with three concrete trigger actions. Clearly matches the 5 anchor (both what and when with concrete trigger phrases); the 4 anchor's caveat ('when' could be more explicit) does not apply since the triggers are specific.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say are present: 'Figma', 'design context', 'rendering Pencil designs', 'React/Tailwind code'. Not 5 because common variations like '.pen files', 'design to code', or 'design tokens' are missing; not 3 because coverage extends well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Named tools (Figma MCP, Pencil) carve out a clear niche with minimal conflict, but 'exporting to React/Tailwind code' overlaps general frontend-generation skills, fitting 'mostly distinct; minor overlap risk with closely related skills'. Not 5 due to that overlap; not 3 since the tool-specific triggers are highly distinctive.

4 / 5

Total

17

/

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