CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-design

Route OpenClaw design work to canonical brand, Carapace product-interface, marketing-page, or design-audit guidance. Use when a task touches OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance.

Quality

82%

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

78%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 efficient, well-structured router skill: a clear branch table, unambiguous routing rules for the two main cases, and a compact shared contract with validation checkpoints. It falls short of top marks mainly on staleness of the pinned CLI version and contract bullets that state what to do without giving the specific command or criterion.

Suggestions

Replace or contextualize the pinned "npx skills@1.5.16" version (e.g., pin policy or a note on when to bump) so the guidance does not silently go stale.

Make validation actionable: name the tool or command for browser validation at desktop/mobile sizes and light/dark themes.

Add a one-line entry rule for when to route to openclaw-design-audit so all five branches have a clear trigger condition.

DimensionReasoningScore

Conciseness

The body is lean (~37 lines) with no padding and no explanations of concepts Claude already knows — every line is directive. The one trimmable/staleness issue is the pinned version in "npx skills@1.5.16 update --project --yes", time-sensitive version information not placed in a deprecation or old-patterns section, which keeps it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Routing rules are concrete and executable ("start with openclaw-marketing-pages and add openclaw-brand only when the task changes identity, logo, imagery, typography, or voice") and one full command is included. Some contract bullets lack the specific means — "Validate rendered pages in a real browser" names no tool or command, and "recorded permission" is undefined — so guidance is mostly but not fully executable.

4 / 5

Workflow Clarity

The decision flow is clear and conditional (choose one branch; website → marketing-pages first, product → carapace first) and validation checkpoints exist in the contract ("Validate rendered pages… at desktop and mobile sizes", "Check both light and dark themes"). Minor gaps — no entry rule for when to use openclaw-design-audit, and validation steps lack specific commands — place it below the explicit-feedback-loop anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, ships no bundle files, and has no content that belongs in separate files; its sections (branch table, routing rules, Shared Contract) are well-organized and the pointers to the five target skills are clearly signaled in a table — one level deep by design. Per the simple-skill guidance this is a 5 even without external file references.

5 / 5

Total

17

/

20

Passed

Description

78%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 well-crafted router description with an explicit Use-when clause, natural trigger terms, and a clearly scoped niche. Its main limitations are that it describes only a single routing action rather than multiple concrete capabilities, and its triggers overlap with the sibling skills it dispatches to.

Suggestions

Add one or two concrete actions beyond routing (e.g., 'load the matching skill and apply its token/component rules') so the 'what' describes more than one capability.

Include common synonym trigger terms users are likely to say, such as 'design system', 'landing pages', 'typography', or 'brand guidelines', to broaden natural keyword coverage.

Sharpen the boundary against sibling skills, e.g., 'Use for deciding which OpenClaw design skill applies; the target skills handle the hands-on work' to reduce overlap risk with openclaw-brand/openclaw-carapace triggers.

DimensionReasoningScore

Specificity

The description names the domain thoroughly and enumerates four routing targets ("canonical brand, Carapace product-interface, marketing-page, or design-audit guidance"), but the only concrete action performed is routing itself — it does not list several specific actions, matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

It explicitly answers both questions: the "what" is routing design work to four named guidance branches, and the "when" is an explicit "Use when a task touches…" clause with concrete trigger phrases. The "when" clause is specific and multi-trigger, matching the top anchor rather than the "could be more explicit" anchor at 4.

5 / 5

Trigger Term Quality

"OpenClaw visual identity, shared CSS tokens, product UI, public web pages, or Carapace compliance" are natural phrases a user would say, giving good keyword coverage. A few natural synonyms are missing (e.g., "design system", "landing pages", "typography", "brand guidelines"), keeping it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The description is clearly scoped to OpenClaw design with a distinct niche, but its trigger terms ("visual identity", "product UI", "public web pages") overlap with the very sibling skills it routes to (openclaw-brand, openclaw-carapace, openclaw-marketing-pages), which is exactly the "minor overlap risk with closely related skills" anchor rather than minimal conflict risk.

4 / 5

Total

16

/

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