CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mercury-design-system

Applies Mercury Design System styling to UIs built with Chameleon. Use when the user mentions Mercury, @genexus/mercury, getBundles, ch-theme, Mercury tokens, or Globant theme — or when styling Chameleon components with a design system.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-sequenced skill with excellent executable examples and a sound one-level reference structure. The main costs are token efficiency — rules are restated multiple times across the Fundamentals, Workflow, and Do's and Don'ts sections — and some lookup-table detail that belongs in the theme reference file.

Suggestions

Consolidate the repeated rules (token fallbacks, primitive-token translation, Figma font-weight −100) into a single authoritative section and have the workflow and Do's and Don'ts reference it instead of restating them.

Move the light/dark surface-hex and neutral-palette lookup tables from 'How to detect the variant' into references/themes-and-variants.md, keeping only the decision flow and primary-color signal inline.

Trim the bundle-category table's per-component enumeration (26 component names) since references/bundles-index.md already provides the full list.

DimensionReasoningScore

Conciseness

The body contains no generic-concept padding (everything is Mercury-specific), but the same rules are deliberately repeated across sections — the token-fallback prohibition, primitive-token translation, and Figma font-weight −100 correction each appear two to three times in 'Mercury Fundamentals', the workflow, and 'Do's and Don'ts'. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, whose over-explanation should be only minor.

3 / 5

Actionability

Guidance is fully executable: a copy-paste getBundles import and call, correct-vs-wrong ch-theme HTML, concrete CSS snippets for focus rings and wrappers, exact class and token tables, and runnable commands ('npm i @genexus/chameleon-controls-library @genexus/mercury', 'npm ls ...'). Specific examples cover the common cases (buttons, forms, inputs, theming), matching the anchor 5.

5 / 5

Workflow Clarity

Two clearly sequenced paths (Figma design / vibe code) converge on shared numbered common steps, with the critical theme decision forced FIRST, a mandatory dependency on the Chameleon skill, and explicit validation checkpoints (step 9 version-compatibility check with a runnable npm ls command, step 10 mandatory Do's and Don'ts checklist). This matches 'clear sequence with explicit validation steps... checklists for complex processes'.

5 / 5

Progressive Disclosure

The SKILL.md is an overview with well-signaled, verified, one-level-deep references (component-bundles-table.md, bundles-index.md, design-foundations/*, icons/README.md, api/*, installation/* — all present on disk). It falls short of anchor 5 because sizable lookup data (the light/dark surface-hex tables and neutral-palette hexes for theme detection) is inlined in the body rather than delegated to the existing themes-and-variants.md reference.

4 / 5

Total

17

/

20

Passed

Description

82%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 description with an explicit 'what' and a rich, explicit 'Use when' trigger list including package and API names. Its only weakness is specificity: it summarizes the skill in one action phrase rather than enumerating its concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ('Mercury Design System styling to UIs built with Chameleon') and one concrete action — applying styling — but does not enumerate the skill's several specific capabilities (ch-theme, getBundles, design tokens, typography, theming) that the body actually covers. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several listed actions.

3 / 5

Completeness

It explicitly answers both questions: 'Applies Mercury Design System styling to UIs built with Chameleon' (what) and 'Use when the user mentions Mercury, @genexus/mercury, getBundles, ch-theme, Mercury tokens, or Globant theme' (when) with concrete trigger phrases — a direct match for the anchor 5 example pattern.

5 / 5

Trigger Term Quality

Strong natural trigger coverage: 'Mercury, @genexus/mercury, getBundles, ch-theme, Mercury tokens, or Globant theme — or when styling Chameleon components with a design system' includes the package name, API names, and theme names a user would actually say. It falls just short of anchor 5's comprehensive synonym coverage (e.g., 'Mercury theme', 'dark mode', or styling-related phrasing variants are absent).

4 / 5

Distinctiveness Conflict Risk

Clear niche (Mercury design-system styling layered on Chameleon components) with distinct triggers (@genexus/mercury, getBundles, ch-theme, Globant theme) that no generic or neighboring skill would claim, minimizing conflict risk — matching the anchor 5 'clear niche with distinct triggers'.

5 / 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

relative_links

Relative link issues: 10 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 10 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

cinthamo/genexus-skills

Path

frontend/mercury-design-system/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.