CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

url-to-code

Clone a live URL as a runnable frontend-only local app.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/product-design/skills/url-to-code/SKILL.md
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 content is a well-sequenced, heavily validated workflow with concrete commands and hard gating rules — its strongest qualities. Its weaknesses are token efficiency (over-decomposed micro-steps and long enumerations that could be compressed) and an inlined environment-specific preview section that would fit better in an external reference.

Suggestions

Compress the capture micro-steps ("Start at the top... Scroll down in small steps... Continue until the full page has been seen") and the 15-item DOM enumeration into a few dense directives that assume Claude's competence.

Move the "Previewing prototypes in ChatGPT Work Mode" section into local-prototype-preflight.md or a dedicated reference, keeping only a one-line pointer in SKILL.md.

Specify how to invoke ImageGen for asset replacement (or link to a reference that does), since it is currently named without any actionable detail.

DimensionReasoningScore

Conciseness

The body avoids concept explanations, but micro-instructions like "Start at the top of the page. Scroll down in small steps. At each step, capture what is visible." and a 15-item enumeration of DOM things to gather (Elements, Components, Text, Links, ...) assume little intelligence and could be tightened into a few directive lines.

3 / 5

Actionability

Mostly executable guidance: exact commands ("sites-preview start \"$PWD\"", "npm run dev -- --host 0.0.0.0 --port 4173 --strictPort"), concrete viewport ("390 x 844"), and specific Vite settings. Minor gaps remain, e.g. "generate a replacement with ImageGen" gives no invocation detail.

4 / 5

Workflow Clarity

A 13-step numbered workflow with explicit validation checkpoints and feedback loops: step 3 page-correctness stop conditions, step 11 compare-and-fix against the original, and step 12's design-qa gate that must loop until "final result: passed" or report "blocked".

5 / 5

Progressive Disclosure

References are one level deep and clearly signaled (critical-overrides, user-context, local-prototype-preflight, design-qa), but the ~15-line environment-specific "Previewing prototypes in ChatGPT Work Mode" section is inlined detail that belongs in local-prototype-preflight.md, and none of the referenced files ship inside this skill's bundle to verify.

4 / 5

Total

16

/

20

Passed

Description

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

The description states one clear, concrete capability in third person without fluff, but it is a single-action summary. It lacks any "when to use" trigger guidance and natural synonym coverage, leaving a user or router little to distinguish invocation contexts.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to clone, recreate, or copy a website or URL as a local app."

Include natural synonyms such as "website", "site", "recreate", and "copy" alongside "live URL" so the description matches how users actually phrase the request.

Briefly enumerate the key outcomes (captures desktop/mobile, copies assets, runs locally, passes design QA) to make the capability coverage more comprehensive.

DimensionReasoningScore

Specificity

"Clone a live URL as a runnable frontend-only local app" names the domain and one concrete action (clone URL → runnable local app), but coverage is not comprehensive — no mention of capture, assets, verification, or outputs.

3 / 5

Completeness

The "what" is clear (clone a live URL as a frontend-only local app), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"Clone" and "live URL" are natural terms users would say, but common variations and synonyms like "website", "site", "recreate", or "copy this page" are missing.

3 / 5

Distinctiveness Conflict Risk

The URL-to-runnable-local-app clone niche is mostly distinct with clear scope ("frontend-only"), though it has minor overlap risk with general web-development or site-scaffolding skills given the thin trigger phrasing.

4 / 5

Total

13

/

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/url-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.