CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-design-system

Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.

Quality

76%

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/openclaw-design-system/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a model of token-efficient, overview-first skill writing: terse rules, a concrete workflow, real one-level-deep references, and an explicit validation step. Its only weaknesses are minor — a missing error-recovery loop after validation and a couple of rules that defer specifics to the references without naming them.

DimensionReasoningScore

Conciseness

The body is a lean set of terse imperative rules with no padding and no explanation of concepts Claude already knows; every line is a directive that assumes the model's competence.

5 / 5

Actionability

The guidance is mostly executable — concrete file paths ("references/tokens.md", "components.css"), explicit package specifiers ("use `@openclaw/carapace` when it is installed, otherwise preserve the legacy `@openclaw/design-system` specifier"), and the exact imports live in the referenced files — with only minor gaps such as "focused exported entry points" not being enumerated inline.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced and ends with an explicit validation checkpoint ("Validate the affected routes with existing tests and real browser screenshots"), but it stops short of a fix-and-retry feedback loop for when validation fails.

4 / 5

Progressive Disclosure

The body is a compact overview, and both referenced bundle files (references/tokens.md and references/consumer-adapters.md) exist, are exactly one level deep with no further nested references, and are clearly signaled with their purpose stated at the point of reference.

5 / 5

Total

18

/

20

Passed

Description

53%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 communicates a clear, niche-scoped "what" with concrete domain artifacts, but it lacks any explicit trigger guidance and buries its useful keywords under migration framing. It reads more like a changelog entry than a skill description that would fire when a user asks about tokens, themes, or styling.

Suggestions

Add an explicit trigger clause such as "Use when styling UI, choosing tokens, theming, or wiring up the design system CSS for OpenClaw consumers" so the skill fires on natural user phrasing.

Replace the single verb "applies" with several distinct concrete actions (e.g., "Select semantic tokens for color, spacing, and radii; configure theme imports; compose shared CSS classes for each framework adapter") to broaden action coverage.

Include natural synonyms users would actually say — "design system", "colors", "styles", "CSS variables" — instead of leading with migration jargon like "Compatibility alias for existing installations".

DimensionReasoningScore

Specificity

The description names the domain and a list of concrete artifacts ("Carapace semantic tokens, themes, shared CSS foundations, consumer adapters") but rests on a single action verb ("applies"), matching the anchor for 1-2 concrete actions rather than several distinct actions.

3 / 5

Completeness

The "what" is clear ("applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives") but the "when" is only weakly implied by "for existing OpenClaw installations"; there is no explicit "Use when..." or equivalent trigger clause, which caps this dimension at 3.

3 / 5

Trigger Term Quality

Keywords like "semantic tokens", "themes", and "CSS" are relevant, but the description leads with migration jargon ("Compatibility alias for existing OpenClaw installations") and omits natural variations users would say such as "design system", "colors", or "styles".

3 / 5

Distinctiveness Conflict Risk

The specific OpenClaw/Carapace naming gives it a clear niche, but it explicitly serves the same domain as the canonical `openclaw-carapace` skill it aliases, creating minor overlap risk with that closely related skill rather than minimal conflict.

4 / 5

Total

13

/

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

openclaw/clawhub

Path

.agents/skills/openclaw-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.