CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-system

Use before any change to how a screen looks in this repository — a new page or component, a layout, a redesign, or a one-line colour or spacing fix. Maps each frontend to the DESIGN.md or wiki page that governs its look, says the document is what ships until the owner chooses another value, says which design skill fits which task and which must never touch a surface with a design system, and how to show the result rendered. Loaded by the designer and design-mechanic agents; any session doing UI work can load it.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A high-quality, deeply repository-specific skill: a clearly sequenced four-step workflow with copy-paste commands, exact paths, and a genuine pre-report validation checklist, all acting as a router to per-surface design documents. The main improvements are structural — splitting the third-party-skill policy into a reference file and breaking the dense multi-clause table rows into readable form — plus making the fix-and-retry loop explicit when a check fails.

DimensionReasoningScore

Conciseness

The body is dense with repository-specific policy Claude cannot know (which DESIGN.md governs which surface, bun vs npm, telemetry-pinned third-party commands, banned skills) and wastes almost no tokens on concepts Claude already knows. It falls short of a 5 because several passages are baroque run-ons — e.g. the stageshow and modern-web-guidance table rows pack multi-paragraph policy into single cells, and Step 2 chains many clauses into one sentence — that could be tightened without losing information.

4 / 5

Actionability

Guidance is fully executable: copy-paste commands throughout ("find . -name DESIGN.md -not -path '*/node_modules/*'", "DISABLE_TELEMETRY=1 npx -y modern-web-guidance@1.0.0 <search|retrieve> …", "npm ci --ignore-scripts", the per-surface dev-server table), exact file paths for every reference, and a named skill per task type. The common cases — finding the governing document, running the right dev server, invoking each skill safely — are each covered by a specific command or table row.

5 / 5

Workflow Clarity

The four steps are explicitly numbered and well-ordered (read the governing document → know the arbitration rule → pick a skill → show the result rendered), and Step 4 is a real validation checklist: rendered checks at phone and desktop widths in light and dark, lab stories per state, browser tests for layout invariants, and gates with mandatory "NOT RUN" reporting. It stops short of a 5 because the validate→fix→retry loop is implicit — what to do when a gate or rendered check fails is never stated — and some failure paths (dispatched-agent "NEEDS INPUT") are buried in dense prose.

4 / 5

Progressive Disclosure

The skill is effectively an overview that routes to one-level-deep, clearly signalled references — per-surface DESIGN.md and wiki pages, other skills' SKILL.mds by path — with the design detail correctly living in those files rather than inlined. It falls short of a 5 because the ~60-line "Eight things these skills do that an agent here must not follow" section and the long operational policy rows are inlined policy that could be split into a reference file, which would also relieve the wall-of-text table rows.

4 / 5

Total

17

/

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 description: it front-loads an explicit, concrete trigger clause and enumerates the skill's distinct capabilities, all scoped tightly to this repository's design-governance context. Its weaknesses are indirect meta-phrasing of the capabilities and a few missing natural trigger synonyms (styling, CSS, frontend).

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Maps each frontend to the DESIGN.md or wiki page that governs its look", the owner-chooses arbitration rule, which design skill fits which task, and "how to show the result rendered" — with only minor gaps. It falls short of a 5 because the actions are stated in indirect meta-language ("says the document is what ships…", "says which design skill fits…") rather than as direct capabilities, and there is no fuller enumeration of what the skill covers.

4 / 5

Completeness

It explicitly answers both questions: "what" is stated through the enumerated capabilities (mapping frontends to governing docs, arbitration, skill routing, rendered verification), and "when" is given as an explicit, concrete trigger clause — "Use before any change to how a screen looks in this repository — a new page or component, a layout, a redesign, or a one-line colour or spacing fix". The trigger guidance is specific and front-loaded, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Trigger terms are natural and well-covered: "a new page or component, a layout, a redesign, or a one-line colour or spacing fix" plus "any session doing UI work" — phrases a user would genuinely say. A few common variations are missing (e.g. "styling", "CSS", "frontend", "design change"), which keeps it below the comprehensive-synonym level of a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — repo-specific design-system governance anchored to "this repository", "DESIGN.md", and named wiki pages — so it is mostly distinct from generic skills. Minor overlap risk remains with general frontend-design skills, since triggers like "a new page or component, a layout, a redesign" would also fire for a generic design skill in a shared library.

4 / 5

Total

17

/

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

referenced_paths_exist

Referenced path issues: 1 possibly missing (assets/app-icons.ts)

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

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