CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skillshare-ui-website-style

Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard, fix visual bugs in either frontend, or need to know which design tokens, ss-* classes, components, or patterns to use. Covers the two dashboard styles (Clean / Playful) in light and dark, design tokens, the ss-* class system, component API, page structure, accessibility, keyboard shortcuts, and anti-patterns. Even if the user just says "fix the styling" or "add a card", use this skill to ensure consistency.

Quality

94%

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

90%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 dense, high-quality design-system reference: terse tables, executable commands, a complete page template, explicit screenshot verification, and a checklist. The main weaknesses are a workflow that is implied across sections rather than sequenced, and a bundle-inconsistent reference to scripts/ai-context.py that does not exist alongside SKILL.md.

Suggestions

Fix the dangling reference: the body instructs 'run python3 scripts/ai-context.py frontend' as the first step, but no scripts/ directory exists in the skill bundle — either include the script or remove/repoint the instruction.

Consolidate the operating workflow into one explicitly numbered sequence near the top (run ai-context → apply tokens/ss-* classes and components → verify with four-look screenshots → run the checklist) instead of distributing it across the intro, 'Verifying a change', and the closing checklist.

Consider moving the legacy-alias migration table and the full ss-* class catalog into references/STYLE_GUIDE.md or a second reference file so SKILL.md stays a lean overview, consistent with its own 'names, does not copy' principle.

DimensionReasoningScore

Conciseness

The body is dense and reference-grade — token tables, class catalogs, an anti-pattern table — with no padding and no explanation of concepts Claude already knows; it even states 'This file names tokens and classes and says when to use them. It does not copy their values.' Every token earns its place, matching the lean-and-efficient anchor rather than the merely-efficient level 4.

5 / 5

Actionability

Guidance is copy-paste ready: an executable grep command to list ss-* classes, a complete TSX page template, a component API table with exact props and variants, and concrete verification commands ('?theme=clean', 'run the dev server... with the ui command'). It exceeds the 'mostly executable' level 4 anchor by covering the common cases with fully executable examples.

5 / 5

Workflow Clarity

The workflow is present and validated — 'Before acting, run python3 scripts/ai-context.py frontend', 'Screenshot the page in all four looks... Look at the screenshots before reporting done', and a closing checklist — but it is distributed across sections rather than one explicitly sequenced flow with error-recovery loops. This fits 'clear sequence with most checkpoints present; minor validation gaps', not the level 5 anchor's coherent validate-fix-retry structure.

4 / 5

Progressive Disclosure

Structure is good: the reasoning/reference material is split one level deep into references/STYLE_GUIDE.md (which exists in the bundle), clearly signaled as 'Design rules and the reasoning behind them'. However the body's primary entry step references scripts/ai-context.py, which is absent from the bundle (no scripts/ directory), a dangling reference that keeps it below the level 5 'well-signaled, easy navigation' anchor.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: it states what the skill covers concretely, gives an explicit 'Use this skill whenever you:' trigger list spanning both frontends, anticipates vague user phrasings like 'fix the styling', and is tightly scoped to the Skillshare project so trigger conflicts are unlikely.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'build or modify a dashboard page or component in ui/src/', 'style or layout website pages or custom CSS in website/', 'create new React components', 'fix visual bugs' — with comprehensive coverage of both frontends. It matches the 'multiple specific concrete actions; comprehensive coverage' anchor, exceeding level 4's 'minor gaps in coverage'.

5 / 5

Completeness

It clearly answers both questions: what ('Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/)... Covers the two dashboard styles (Clean / Playful)... design tokens, the ss-* class system, component API, page structure, accessibility, keyboard shortcuts, and anti-patterns') and when (an explicit 'Use this skill whenever you:' trigger list with concrete phrases). This is the level 5 anchor exactly.

5 / 5

Trigger Term Quality

Natural user phrasings are explicitly covered, including informal ones: "Even if the user just says 'fix the styling' or 'add a card'", plus 'dashboard page', 'component', 'custom CSS', 'visual bugs', 'design tokens'. Coverage is comprehensive with synonyms, fitting the level 5 anchor rather than level 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche with distinct triggers — Skillshare, ui/src/, website/, ss-* classes, Clean/Playful styles — so conflict with generic styling or documentation skills is minimal. It matches 'clear niche with distinct triggers; minimal conflict risk' rather than level 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

runkids/skillshare

Path

.skillshare/skills/skillshare-ui-website-style/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.