CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-helper

Build and modify the frontend of this repo using the existing design tokens and components rather than inventing new ones. Covers both visual variants in the project — the marketing pages (light theme, Google blue

Quality

95%

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

92%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 well-structured, highly actionable skill body: project-specific detail throughout, a clear procedure with explicit verification, and correct use of one-level-deep references that all resolve. The only weakness is mild redundancy from re-listing the asset inventory in both tables and the File layout tree.

DimensionReasoningScore

Conciseness

The body is dense with project-specific facts and assumes Claude's competence, but the same asset filenames are listed three times (snippet table, template list, File layout tree) and a few rhetorical sentences ('This skill exists to prevent that') could be trimmed — minor over-explanation, matching the 4 anchor rather than a fully lean 5.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: ordered variant-detection signals, 'copy from the cited line range' pointers, ready-to-paste snippet and template paths, a concrete token-mixing symptom list, and specific verification checks — the common cases are all covered with copy-paste-ready direction.

5 / 5

Workflow Clarity

The 5-step procedure is clearly sequenced with an explicit validation step ('### 5. Verify' with concrete checks), feedback loops for error recovery ('If you catch any of these, stop and switch variants explicitly'; 'If signals conflict — ask'), and checklists — no destructive or batch operations, so no cap applies.

5 / 5

Progressive Disclosure

The body is a clear overview that appropriately pushes exact token values to references/tokens.md and per-component detail to references/components-map.md, both one level deep and well signaled with when-to-read guidance; all referenced bundle files (2 references, 11 snippets, 3 templates) exist on disk.

5 / 5

Total

19

/

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: concrete actions with file paths, explicit and varied trigger phrases, both variants named with distinguishing details, and slash-command invocation. It is information-dense without padding and stays in third-person/imperative voice throughout.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('adding a new page, dropping in a button or card, building a modal or form, fixing inconsistent styling') anchored to specific files (public/*.html, src/website/webServer.ts), giving comprehensive coverage of the frontend domain with no gaps.

5 / 5

Completeness

It explicitly answers both 'what' ('Build and modify the frontend of this repo using the existing design tokens and components rather than inventing new ones') and 'when' ('Use this skill whenever the user wants to add, modify, or restyle anything in public/*.html or the inline HTML strings...') with concrete trigger phrases and slash-command guidance.

5 / 5

Trigger Term Quality

Natural trigger terms users would say are covered comprehensively — page, button, card, modal, form, styling/restyle, dashboard, marketing pages — including synonyms (add/modify/restyle/fix) and file-extension triggers (public/*.html, webServer.ts), matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — this repo's two named visual variants with specific hex colors, fonts, and files — and the webServer.ts scope is qualified to 'inline HTML strings', minimizing overlap with backend skills. Trigger risk is minimal.

5 / 5

Total

20

/

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

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

boarlabsxyz/awesome-mcp

Path

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