CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

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

78%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, token-efficient workflow skill with concrete commands, clear file contracts, and excellent use of one-level-deep bundle references. Its main gaps are the unspecified screenshot-capture mechanism and validation not being wired into the per-route loop as an explicit checkpoint.

Suggestions

Add the concrete screenshot-capture step (e.g. the Playwright command or snippet used to grab desktop/tablet/mobile screenshots) so the core capture action is executable, not just named.

Insert validation into the per-route loop, e.g. add step 5: "Run `page_artifacts.mjs validate --page {page}`; only when it passes, append to capture-index.jsonl and move to the next route".

Trim or fold the "Example prompts that should trigger this skill" section into the description, since the trigger phrasing is already duplicated there.

DimensionReasoningScore

Conciseness

The body is lean and operational with no concept explanations, but the "Example prompts that should trigger this skill" section duplicates trigger guidance already in the description and could be trimmed.

4 / 5

Actionability

Gives concrete executable commands ("node .github/skills/.../page_artifacts.mjs scaffold --page dashboard --route /") and exact output paths, but never specifies how screenshots are actually captured (no Playwright command despite the compatibility note requiring it).

4 / 5

Workflow Clarity

The 5-step per-route sequence is clear and backed by a checklist and a validate command, but the validate step is not explicitly sequenced into the loop — "Only then move to the next route" does not include running validation first.

4 / 5

Progressive Disclosure

A concise ~55-line overview with clearly signaled, one-level-deep markdown links to real bundle files (assets/page-template.md, assets/request-template.json, scripts/page_artifacts.mjs), with template bulk appropriately split out of the body.

5 / 5

Total

17

/

20

Passed

Description

87%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 that clearly and explicitly states both capability and trigger conditions in third person, with concrete actions and product-specific distinctiveness. Keyword coverage is good but could add a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ("capture screenshots", "write per-page docs and per-page analysis requests", "one route at a time") but omits some capabilities covered in the body (viewport variants, capture-index logging), so coverage has minor gaps.

4 / 5

Completeness

Explicitly answers both what ("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)") and when ("Use when asked to map UI, capture screens page-by-page, avoid agent memory saturation, or generate ux_ui_map artifacts").

5 / 5

Trigger Term Quality

"map UI", "capture screens page-by-page", and "generate ux_ui_map artifacts" are natural trigger phrases, but a few common variations (e.g. "screenshot the app", "context window") are missing.

4 / 5

Distinctiveness Conflict Risk

Tied to a specific product and artifact set ("EdgeQuake WebUI", "ux_ui_map artifacts") with distinct triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

18

/

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/ux-ui-map-page-by-page/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.