CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-ui-states

Enumerate and screenshot every UI state a PR adds or changes. Use when asked to show, capture, or screenshot the UI states of a PR or branch.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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 tight, minimal instruction-only skill whose main weakness is execution detail: it tells Claude what to enumerate and to screenshot each state, but not how states are discovered or how screenshots are captured. Conciseness and structure are exemplary; actionability is the limiting dimension.

Suggestions

Add one concrete line on how to discover changed UI states, e.g., 'Identify changed frontend files via the PR diff (components, pages, forms) to derive the state list.'

Specify the capture mechanism or at least the prerequisite, e.g., 'Launch the app (see the run skill if needed) and screenshot each state,' so screenshots are executable rather than aspirational.

Add a lightweight completion check, e.g., 'Confirm every enumerated state has a corresponding screenshot before finishing.'

DimensionReasoningScore

Conciseness

Three lean sentences with zero padding: 'Enumerate all of the UI states that were modified or added in the PR, including error states, inputs like toggles, buttons, or forms' assumes Claude's competence and explains nothing it already knows. Every token earns its place.

5 / 5

Actionability

The enumeration of state categories ('error states, inputs like toggles, buttons, or forms, or any edited pages or interfaces') is concrete scope guidance, but there are no specifics on how to identify which UI states changed (e.g., diffing frontend files) or how to capture the screenshots (launching the app, tooling). This sits between anchor 2 and anchor 3, closer to 'some concrete guidance but incomplete; missing key details'.

3 / 5

Workflow Clarity

A clear two-step sequence (enumerate states, then 'Take screenshots of each') with unambiguous scope, but no checkpoint that each screenshot actually captured the state (e.g., verifying screenshots are non-blank or that every enumerated state was covered). Matches 'clear sequence with most checkpoints present; minor validation gaps' rather than the explicit validation of anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; the body is well-organized with no content that belongs in bundle files. Per the simple-skill guideline this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit and well-phrased trigger clause; its only real weakness is specificity, since it names just two actions (enumerate, screenshot) and stops there. Trigger coverage and what/when completeness are solid.

Suggestions

Broaden the action list slightly to lift specificity, e.g., 'Enumerate and screenshot every UI state a PR adds or changes, including error, loading, and input states, and save each capture for review.'

Add one or two natural synonyms such as 'visual states' or 'what the UI looks like after the change' to round out trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('UI state a PR adds or changes') and exactly two concrete actions ('Enumerate and screenshot'), matching the anchor for 'names domain and 1-2 concrete actions, but not comprehensive'. It is not a 4 because it lists only two actions and omits what happens with the captures (saving, comparing, reporting).

3 / 5

Completeness

It explicitly answers both questions: the what ('Enumerate and screenshot every UI state a PR adds or changes') and a concrete when ('Use when asked to show, capture, or screenshot the UI states of a PR or branch'). This mirrors the anchor-5 pattern of a clear what plus an explicit 'Use when' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

'show, capture, or screenshot' covers natural synonym phrasings and 'PR or branch' covers both user framings, giving good keyword coverage. It falls short of anchor 5 because a few natural variations ('visual states', 'what the UI looks like', 'UI of the app') are missing.

4 / 5

Distinctiveness Conflict Risk

The PR/branch UI-state niche is well differentiated with distinct triggers, with only minor overlap risk against generic screenshot or run-the-app skills. This matches 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict clarity of anchor 5.

4 / 5

Total

16

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

every-app/open-seo

Path

.agents/skills/review-ui-states/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.