CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

design-qa

Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/design-qa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

An exceptionally actionable QA workflow with executable code, explicit validation gates, and a genuine iteration loop, organized into clear sections with a real one-level-deep reference. Its only notable weakness is repetition and duplication between the inline fidelity-surface checklists and references/qa-rubric.md, which costs tokens without adding guidance.

DimensionReasoningScore

Conciseness

The body is dense with prescriptive, operational directives and explains nothing Claude already knows, but it repeats key instructions verbatim ('Put the source image and the implementation screenshot together in the same comparison input' appears twice) and the Required Fidelity Surfaces section duplicates checklists already in references/qa-rubric.md.

3 / 5

Actionability

Fully executable throughout: a copy-paste-ready Playwright snippet with a 393 x 852 bounding-box guard, concrete commands ('npm run check:runtime'), specific selectors ('data-testid="device-screen"', '[data-phone-screen]'), a severity taxonomy, an output template, and an explicit design-qa.md field list.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints (blocking 'npm run check:runtime', blocked-on-missing-artifacts rules), a documented find -> fix -> re-capture -> re-compare feedback loop, and a required-fields checklist for the final report.

5 / 5

Progressive Disclosure

Good structure with a real, clearly signaled, one-level-deep reference ('Read [qa-rubric](./references/qa-rubric.md) when the QA pass spans more than a quick visual check'), but the inlined Required Fidelity Surfaces section substantially overlaps that reference file, leaving a minor content-splitting gap versus anchor 5.

4 / 5

Total

17

/

20

Passed

Description

66%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 well-scoped, highly distinct description with an explicit 'Use only after...' trigger clause and strong negative routing. Its weaknesses are a thin statement of what the QA actually does (one implied action, no mention of the fix-list output or fidelity surfaces) and trigger terms that lean on internal pipeline jargon over natural user language.

Suggestions

State the concrete outputs and actions in the 'what' clause, e.g. 'Compares a source visual target against the rendered implementation and produces a severity-ranked fix list (fonts, spacing, colors, imagery, copy) saved to design-qa.md'.

Add natural trigger synonyms users would actually say, such as Figma, mockup, screenshot, 'compare design to implementation', or 'visual fidelity check', alongside the internal build-pipeline terms.

Trim the parenthetical pipeline qualifiers ('URL-to-code build, or image-to-code build') to one or two plain-language equivalents so the trigger clause reads as user-facing language rather than internal routing configuration.

DimensionReasoningScore

Specificity

Names the domain precisely (prototype QA comparing 'a source visual target and a rendered implementation... before handoff') but offers only one core action rather than the several distinct actions of the next anchor.

3 / 5

Completeness

Both what and when are present, and the 'Use only after a Product Design prototype, URL-to-code build, or image-to-code build' clause is explicit and concrete; however, the what ('Internal prototype QA helper') is thin and omits what the QA actually produces, falling short of anchor 5's comprehensive pairing.

4 / 5

Trigger Term Quality

Relevant keywords are present ('prototype', 'QA', 'handoff', 'Product Design prototype'), but terms like 'URL-to-code build' and 'image-to-code build' are pipeline jargon rather than natural user phrases, and common variations (Figma, mockup, screenshot, visual diff) are missing.

3 / 5

Distinctiveness Conflict Risk

It carves a clear post-build visual-fidelity QA niche and explicitly disambiguates the nearest competitor ('Do not use for broad UX critique, design critique, product audits, or flow reviews; route those... to audit'), giving minimal conflict risk.

5 / 5

Total

15

/

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

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/product-design/skills/design-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.