CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visual-qa

Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the platform's design guidelines.

Quality

82%

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

73%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 exceptionally rigorous, actionable QA workflow - explicit steps, copy-paste commands, complete reviewer prompts, and a hard completion gate with bounded retry loops. Its weaknesses are token efficiency (a long harness-compatibility preamble and repeated rules that add no visual-QA value) and inlining the full prompt templates and platform-routing boilerplate instead of moving them to reference files.

Suggestions

Move the "Codex Harness Tool Compatibility" preamble (including its thrice-repeated "this section wins" rule and the dense V1/V2 routing paragraph) into a separate reference file or a routing table one-tenth the length; it is generic harness boilerplate, not visual-QA guidance, and consumes ~25 lines of every load.

Extract the two full oracle prompt templates (Pass A and Pass B, ~110 lines) into references such as references/pass-a-prompt.md and references/pass-b-prompt.md, keeping a short charter summary plus the file pointer in SKILL.md.

State recurring rules once instead of three times: the fresh-evidence requirement is repeated across "Evidence must be fresh", capture hygiene, and the completion gate, and could be consolidated into a single up-front rule the later sections reference.

DimensionReasoningScore

Conciseness

The visual-QA core (steps, checklist, gates, commands) is dense and operational with no concept over-explanation, but the ~25-line "Codex Harness Tool Compatibility" preamble is harness-routing boilerplate unrelated to the skill's purpose, "If a code block below conflicts with this section, this section wins" is repeated three times, and the V1/V2 paragraph restates routing rules heavily. This is more than the minor trimming of anchor 4, so it fits "mostly efficient but could be tightened".

3 / 5

Actionability

Provides copy-paste-ready commands ("node \"$SKILL_DIR/scripts/visual-qa.mjs\" image-diff <reference.png> <actual.png>", tui-check, pdftoppm, the scroll-owner probe, the web-terminal QA script) and two complete fill-in reviewer prompt templates. Not 5 because the primary web-capture path and machine pre-check depend on external unbundled skills (omowright via the `browser` skill, the `frontend` detect SDK), so the flow is not fully executable from this bundle alone.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with hard validation checkpoints: fresh-evidence staleness rules, capture hygiene verification before dispatching reviewers, a machine pre-check, and a bounded completion gate with explicit feedback loops (defect -> fix -> re-capture -> FRESH reviewer) and a NEEDS HUMAN REVIEW terminal state on budget exhaustion. This matches the anchor-5 pattern of explicit validation, error-recovery loops, and a checklist for a complex process.

5 / 5

Progressive Disclosure

Bundle structure is good: references/browser-setup.md and scripts/visual-qa.mjs are real, one level deep, and clearly signaled from the body ("$SKILL_DIR/references/browser-setup.md has the matrix loop..."), with capture detail and tooling appropriately split out. Not 5 because ~110 lines of oracle prompt templates and the Codex harness preamble are inlined in SKILL.md where they clearly belong in reference files.

4 / 5

Total

16

/

20

Passed

Description

83%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: it states multiple concrete capabilities in third person and pairs them with an explicit, naturally-phrased "Use when..." trigger clause covering builds, changes, and "does it look right" questions. Its only weaknesses are a broad "any UI build or change" trigger that invites overlap with frontend/review skills and a few missing synonym trigger phrases.

DimensionReasoningScore

Specificity

Lists several concrete actions - "an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict" - in third person. Not 5 because several real capabilities (reference-fidelity, before/after, motion capture) are unmentioned; well above 3 since far more than 1-2 specific actions are named.

4 / 5

Completeness

Explicitly answers both what ("Runs rigorous visual QA... checklist, paired light/dark captures... per-item PASS/FAIL verdict") and when ("Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the platform's design guidelines") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "visual QA", "UI build or change", "looks right", "design guidelines", "page, component, or TUI" - phrases a user would naturally say. Not 5 because common variations like "design review", "screenshot check", or "visual regression" are missing.

4 / 5

Distinctiveness Conflict Risk

The visual-QA-over-rendered-surfaces niche is distinct with specific triggers (web, terminal, paginated, TUI), but "Use for any UI build or change" is broad enough to overlap with frontend-development and general review skills. Mostly distinct with minor overlap risk, fitting anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/visual-qa/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.