CtrlK
BlogDocsLog inGet started
Tessl Logo

ux-ui-map-page-by-page

Produce the EdgeQuake WebUI UX/UI map one route at a time (capture screenshots, then immediately write per-page docs and per-page analysis requests). Use when asked to map UI, capture screens page-by-page, avoid agent memory saturation, or generate ux_ui_map artifacts.

79

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, executable, and well-structured with a clear sequenced workflow, validation checkpoints, and properly signaled one-level-deep references to real bundle files.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explanation of screenshots, routes, or dev servers) and every section earns its place; minor overlap between the checklist and output contract serves distinct validation purposes rather than padding.

3 / 3

Actionability

It provides copy-paste-ready commands (e.g. "node .github/skills/.../page_artifacts.mjs scaffold --page dashboard --route /") with concrete file paths and template links, not pseudocode or vague direction.

3 / 3

Workflow Clarity

A numbered 1–5 process is given with an explicit per-route validation checklist and a validate subcommand, supplying checkpoints and a feedback loop for this batch operation.

3 / 3

Progressive Disclosure

The overview points to one-level-deep, clearly signaled references (assets/page-template.md, assets/request-template.json, scripts/page_artifacts.mjs), all of which are real bundle files, keeping the SKILL.md itself lean.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise yet complete, naming concrete actions, explicit triggers, and a distinct niche. It answers both what and when without padding or buzzwords.

DimensionReasoningScore

Specificity

"capture screenshots, then immediately write per-page docs and per-page analysis requests" lists multiple concrete actions, matching the anchor for listing several specific actions rather than a single domain mention.

3 / 3

Completeness

It states what the skill does ("Produce the EdgeQuake WebUI UX/UI map one route at a time...") and gives an explicit "Use when..." trigger clause, satisfying both halves clearly rather than implying one.

3 / 3

Trigger Term Quality

"asked to map UI, capture screens page-by-page ... or generate ux_ui_map artifacts" covers natural phrasings a user would say; while "agent memory saturation" is mildly technical, the common variations are well represented.

3 / 3

Distinctiveness Conflict Risk

The EdgeQuake WebUI page-by-page mapping niche with page-by-page capture triggers is narrowly scoped and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
raphaelmansuy/edgequake
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.