CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-page-frame

Keep EdgeQuake WebUI pages visually consistent - one page frame (gutter, max width, vertical rhythm), one page-title style, one focus ring, and DOM-geometry checks. Use when adding or restyling a route, page header, toolbar, settings pane, or any layout in edgequake_webui, or when a page looks misaligned, clunky, or inconsistent with its siblings.

Quality

97%

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

96%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 an excellent example of a project-specific style-enforcement skill: terse, fully concrete, with a real workflow checklist, executable verification commands, and failure-triage guidance. Its only structural weakness is that it is a flat ~105-line file whose verification details (spec list, known-failures ledger) could be split into a one-level-deep reference.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with zero padding: exact token values ('--gutter 24px (16px under 900px)'), exact Tailwind classes, and terse rules like 'Screenshots are for humans.' It never explains concepts Claude already knows, matching 'Lean and efficient; assumes Claude's competence; every token earns its place' rather than anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands (the Playwright invocation with the exact spec file list, `npx vitest run src/components/shared`, `npx tsc --noEmit -p tsconfig.json`), exact class strings (`text-[1.375rem] font-semibold leading-snug tracking-[-0.012em]`), a prop table, and precise tolerances ('within 1px', viewports 375/768/1280/1920). This matches 'Fully executable; copy-paste ready code or commands' covering the common cases, not anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Section 4 is an explicit 6-step checklist ending with a validation gate ('Run the checks below before calling the page done'), and section 5 supplies the verification commands plus error-recovery triage ('Known pre-existing failures (not from frame work)...') so failures can be attributed correctly. This matches 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists', exceeding anchor 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The single-file body (~105 lines) is well organized into six clearly labeled sections with a prop table and checklist, but it exceeds the under-50-line threshold where structure alone earns a 5, and some operational detail (the spec command list and the known-pre-existing-failures ledger) could live in a reference file. This matches 'Good structure; most content is appropriately placed; minor organization gaps' rather than the clean one-level-deep reference split of anchor 5.

4 / 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: it states concrete capabilities with technical specifics, provides a rich 'Use when...' clause covering both task intents and symptom-based triggers, and is tightly scoped to a single product area. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'one page frame (gutter, max width, vertical rhythm), one page-title style, one focus ring, and DOM-geometry checks' — each with parenthetical detail, comprehensively covering the skill's scope. It matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' and is not the level below, which allows 'minor gaps in coverage' that are not evident here.

5 / 5

Completeness

It explicitly answers both 'what' ('Keep EdgeQuake WebUI pages visually consistent - one page frame..., one page-title style, one focus ring, and DOM-geometry checks') and 'when' via a full 'Use when...' clause with concrete triggers. This is the anchor-5 pattern ('Clearly and explicitly answers both what AND when with concrete trigger phrases'), not anchor 4 where the 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Trigger terms cover both intents ('adding or restyling a route, page header, toolbar, settings pane, or any layout') and symptom phrases a user would naturally say ('misaligned, clunky, or inconsistent with its siblings'), with synonyms covered. This matches 'Comprehensive coverage of natural terms including synonyms'; a score of 4 would require several natural terms to be missing, which is not the case.

5 / 5

Distinctiveness Conflict Risk

The description is scoped to a named product ('EdgeQuake WebUI pages', 'edgequake_webui') with distinct, layout-specific triggers, giving it a clear niche with minimal conflict risk against generic skills. It is not anchor 4, which anticipates overlap with closely related skills; the explicit repo scoping prevents that.

5 / 5

Total

20

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

raphaelmansuy/edgequake

Path

.github/skills/ui-page-frame/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.