CtrlK
BlogDocsLog inGet started
Tessl Logo

ux-ui-analyze-single-page

Analyze exactly one captured UI page (from ux_ui_map screenshots + request JSON) and immediately write/update ux_ui_map/pages/{page}.md in neutral descriptive language. Use when asked to analyze screenshots, rewrite corresponding analysis immediately, or avoid memory/context saturation.

72

Quality

88%

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.

A concise, well-structured single-purpose skill with concrete paths, an ordered procedure, and a clear output template. It is appropriately lean for a simple descriptive task and would benefit mainly from a fuller worked example of the output document.

DimensionReasoningScore

Conciseness

Lean, well-sectioned body with no over-explanation of concepts Claude already knows; every section (When to use, Inputs, Output, Rules, Procedure, Example) earns its place. It is not a 2 because there is no unnecessary explanation or padding to trim.

3 / 3

Actionability

Gives concrete, executable guidance: exact input/output paths, an ordered procedure, and an explicit output template skeleton (Overview, ASCII diagram, screenshot table, regions/containers/components). It is an instruction-only skill so the absence of code is not penalized; guidance is specific and actionable.

3 / 3

Workflow Clarity

Clear numbered sequence with explicit ordering (desktop then tablet/mobile) and an explicit stop condition ('Stop after writing this one page'). As a simple, non-destructive single-page task it qualifies for 3 under the simple-skills note; it is not a 2 because the sequence and termination are unambiguous.

3 / 3

Progressive Disclosure

A short (<50 line), single-purpose skill organized into clear sections with no deep or nested references, and no bundle files to misroute. Under the simple-skills guideline this scores 3 on well-organized sections alone.

3 / 3

Total

12

/

12

Passed

Description

77%

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 tightly scoped, action-oriented description with explicit 'Use when' guidance covering both what and when. Its main weakness is the 'avoid memory/context saturation' trigger, which is jargon-laden and introduces some overlap risk with other skills.

Suggestions

Replace the jargon trigger 'avoid memory/context saturation' with a phrase a user would naturally say, such as 'Use when the user wants each page analyzed and written immediately rather than in a batch'.

Add a couple of natural trigger variations (e.g., 'describe the UI of one page', 'write up one screenshot') to broaden coverage of terms users would actually say.

DimensionReasoningScore

Specificity

Names multiple concrete actions with exact artifacts: 'Analyze exactly one captured UI page', 'immediately write/update ux_ui_map/pages/{page}.md', 'in neutral descriptive language'. It is not a 2 because it specifies the precise input source and output file rather than only naming a domain.

3 / 3

Completeness

Explicitly answers both 'what' (analyze one captured UI page and write/update the page doc in neutral language) and 'when' via a clear 'Use when' clause. It is not a 2 because the 'when' is explicit rather than implied.

3 / 3

Trigger Term Quality

Includes some natural triggers like 'Use when asked to analyze screenshots' and 'rewrite corresponding analysis immediately', but also jargon a user would not naturally say ('avoid memory/context saturation') and lacks common variations. It is not a 3 because coverage of natural phrasings is incomplete.

2 / 3

Distinctiveness Conflict Risk

The core niche is specific ('exactly one captured UI page', 'ux_ui_map' paths), but the 'avoid memory/context saturation' trigger is broad and could overlap with general context-management skills. It is not a 1 because the primary triggers are tied to a distinct task, and not a 3 because of that overlap risk.

2 / 3

Total

10

/

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.