CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

emcn-design-review

Review UI code for alignment with the emcn design system — components, tokens, patterns, and conventions

Quality

78%

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 ./.agents/skills/emcn-design-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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 an exemplar of lean, highly actionable instruction-only content: exact tokens, components, variants, and anti-pattern match patterns with no wasted tokens. Its main gap is workflow-level — the fix-application path (batch edits, default on) lacks any post-fix validation step — and its 74-line inline token catalog leaves modest room for reference-file splitting.

Suggestions

Add a post-fix validation step to the workflow, e.g. "5. After applying fixes, run the typecheck/build and re-scan the diff to confirm no violations remain".

Consider moving the full token catalog (text/surface/border/z-index/badge families) to a references/tokens.md file and keeping only the most common tokens inline, bringing SKILL.md under the simple-skill threshold.

Clarify in the Steps how findings should be reported when fix=false (e.g., grouped by file or by rule) so the propose-only path is as well-specified as the apply path.

DimensionReasoningScore

Conciseness

The body is a lean, checklist-style rule catalog with zero padding and no explanation of concepts Claude already knows — every line states a rule, a token, or an anti-pattern. It matches anchor 5 (lean and efficient, assumes Claude's competence); anchor 4 would require identifiable over-explanation to trim, and none is present.

5 / 5

Actionability

Guidance is fully concrete: exact file paths to read ("packages/emcn/src/index.ts", "apps/sim/app/_styles/globals.css"), exact token names with values ("--z-dropdown (100)"), exact component/variant/prop names, and concrete match patterns to flag ("text-gray-*", "#hex", "rgb()", "h-[Npx] w-[Npx]"). Per the rubric's scoring notes, an instruction-only skill with this level of specific, actionable guidance scores at anchor 5.

5 / 5

Workflow Clarity

The 4-step sequence (read barrel, read globals.css, analyze scope against every rule, apply or propose fixes) is clearly ordered, but the workflow ends at "apply the fixes" with no validation checkpoint (e.g., typecheck, build, or visual re-verification). Since fix=true is the default and scope can be "whole codebase" (a batch edit operation), the missing validation step caps workflow clarity at 3 per the judging guidelines.

3 / 5

Progressive Disclosure

The single-file body (~74 lines) is well organized with clear section headers and appropriately signals external codebase paths inline. However, it exceeds the under-50-line simple-skill threshold, and content such as the full token catalog and the dense Mobile rules paragraph could be split into a reference file. This matches anchor 4 (good structure, most content appropriately placed, minor organization gaps) rather than 5.

4 / 5

Total

17

/

20

Passed

Description

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

The description is concise, specific to a clearly identifiable niche, and written in appropriate verb-first style, but it omits any explicit "Use when..." trigger guidance and undersells the skill's fix-applying capability. Adding a trigger clause and mentioning that it can apply or propose fixes would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing or fixing UI code, or when the user mentions emcn components, design tokens, or styling conventions."

Mention the fix capability in the description (e.g. "...and apply or propose fixes") since the skill defaults to fix=true.

Include a couple of natural synonyms such as "styling" or "CSS variables" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("UI code", "emcn design system") and one concrete action ("Review ... for alignment") with four enumerated focus areas ("components, tokens, patterns, and conventions"), but does not cover other capabilities such as applying or proposing fixes. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several distinct specific actions.

3 / 5

Completeness

The "what" is clear (review UI code for alignment with the emcn design system), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" half is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Natural keywords a user of this codebase would say are present: "UI code", "design system", "emcn", "components", "tokens". Common variations like "styling", "CSS", "Tailwind", or "design review" are missing, so it falls short of the comprehensive synonym coverage of anchor 5 but is clearly above anchor 3.

4 / 5

Distinctiveness Conflict Risk

"emcn" is a project-specific component library name, giving the description a clear niche with distinct triggers and minimal conflict risk against generic review or styling skills. Anchor 5 is the best fit; anchor 4's "minor overlap risk" would apply only if the emcn qualifier were absent.

5 / 5

Total

15

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

simstudioai/sim

Path

.agents/skills/emcn-design-review/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.