CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

image-to-code

Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

Quality

76%

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/image-to-code/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.

A strong, action-oriented workflow document with concrete commands, explicit validation gates, and a genuine fix-retest feedback loop through design QA. Its weaknesses are minor: a duplicated CRITICAL RULE, repeated handoff instructions, and a few steps (fonts, icon search) that direct rather than specify.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and environment-specific with essentially no explanation of concepts Claude already knows, but it has trimmable duplication: the "Do not create custom div art, CSS art, inline SVGs..." CRITICAL RULE appears nearly verbatim in both step 5 and step 8, and "Keep the local preview open" / "Do not deploy to Sites unless the user explicitly asks" each appear multiple times. This fits anchor 4 (efficient with minor instances that could be trimmed) rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Much of the guidance is executable and copy-paste ready: `sites-preview start "$PWD"`, `npm run dev -- --host 0.0.0.0 --port 4173 --strictPort`, the Vite `server.host`/`server.allowedHosts` config, `http://terminal.local:4173/`, `--template mobile-app`, and the `design-qa.md` report file. Minor gaps remain — "Find freely available fonts" and "Find a freely available icon library... Search for the best match" give no concrete method or source — so it lands at anchor 4 rather than 5's fully-covered common cases.

4 / 5

Workflow Clarity

The 13-step checklist is explicitly declared as a checklist to complete, opens with a precondition gate (step 1: do not start without a resolved visual target, with a stop-and-ask rule), and closes with a blocking design-QA gate containing a full feedback loop: "Fix P0/P1/P2 issues, capture the app again, and repeat until the QA report says `final result: passed`" plus blocked-state handling. This matches anchor 5 (clear sequence, explicit validation, feedback loops for error recovery, checklists).

5 / 5

Progressive Disclosure

The body is well-sectioned and its references are clearly signaled with purposes and anchors one level deep (`[$index](../index/SKILL.md)`, `[critical-overrides](../../references/critical-overrides.md#build-handoff)`, `[local-prototype-preflight](../../references/local-prototype-preflight.md)`, `[design-qa](../design-qa/SKILL.md)`), though none of these targets exist within this skill's own bundle (references/, scripts/, assets/ are absent). Some environment-specific operational detail (the ~15-line ChatGPT Work Mode previewing procedure) is inlined where a reference file could carry it, so anchor 4 (good structure, references mostly clear, minor organization gaps) is the best fit.

4 / 5

Total

17

/

20

Passed

Description

61%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 concise, domain-specific description with a clear 'what' and good natural trigger nouns, but it lacks any explicit 'Use when...' trigger guidance and describes only one core action. Adding a trigger clause and one or two more concrete capability verbs would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user selects or provides a screenshot, mockup, or generated image to recreate as a website or web app" — the missing 'when' currently caps completeness at 3.

Include one or two more concrete actions beyond 'implement' (e.g., "generates matching image assets, measures layout and spacing, and runs design QA against the reference") to raise specificity.

Add natural user phrasings like "design", "turn this mockup into code", or "recreate this UI" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain clearly ("Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend") but centers on a single action — implementing/recreating — rather than listing several concrete actions like asset generation, layout measurement, or design QA. It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than anchor 4, which requires several distinct specific actions; the enumerated items are input types, not separate capabilities.

3 / 5

Completeness

The 'what' is clear — implement a selected visual as a faithful, responsive frontend — but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by 'selected'. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3, and anchor 4's requirement of an explicit (if imperfect) 'when' is not met.

3 / 5

Trigger Term Quality

Natural trigger terms are present: "image", "screenshot", "mockup", "Image Gen reference", "frontend" — phrases a user would plausibly say when asking to recreate a visual. A few common variations are missing ("design", "design-to-code", "website/web app", "UI", "HTML"), so it fits anchor 4 (good keyword coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

The image/screenshot/mockup-to-frontend niche is fairly distinct with clear triggers, carrying only minor overlap risk with generic frontend-building or design-implementation skills. It fits anchor 4 (mostly distinct, minor overlap with closely related skills); anchor 5 would require an explicit trigger clause sharpening the niche further.

4 / 5

Total

14

/

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: 9 suspicious

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

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