CtrlK
BlogDocsLog inGet started
Tessl Logo

url-to-code

Recreate an authorized live website or app URL as a faithful, runnable, frontend-only local implementation.

64

Quality

76%

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 ./packages/opencode/src/skill/builtin/.bundle/product-design/workflows/url-to-code/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a tight, well-structured instruction-only workflow with explicit validation gates, a feedback loop, and a checklist, making effective use of tokens and references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a DOM, breakpoint, or lazy-loading is, and every step and hard-rule line is actionable instruction with no padding.

5 / 5

Actionability

Steps are concrete and executable as process guidance with specific file references and actions, but as an instruction-only skill it lacks copy-paste code and a few steps (e.g. 'the smallest suitable frontend supported by the harness') rely on context-dependent judgment.

4 / 5

Workflow Clarity

The 10-step sequence has explicit validation checkpoints (stop conditions in step 2, source comparison in step 9, and the design-qa gate in step 10) plus a fix-and-retry feedback loop and a Hard Rules checklist.

5 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Workflow, Hard rules) and clearly signaled, one-level-deep references to sibling skills and files, fitting the simple-skill exception.

5 / 5

Total

19

/

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.

The description is concise and clearly states what the skill does with good natural keywords and a distinct niche, but it omits any explicit 'when to use it' trigger guidance, which caps completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when the user asks to clone or faithfully recreate a live website or app URL they own or have permission to reproduce.'

Add the synonym 'clone' alongside 'Recreate' to capture the most common user phrasing for this task.

Optionally name 1-2 concrete sub-actions (e.g. capture source evidence, scaffold a local frontend) to raise specificity above a single action.

DimensionReasoningScore

Specificity

The description names the domain ('live website or app URL') and one concrete action ('Recreate ... as a faithful, runnable, frontend-only local implementation'), with precise qualifiers, but lists only a single action rather than several concrete steps.

3 / 5

Completeness

There is a clear 'what' (recreate a live URL as a frontend-only local implementation) but no 'when' — no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural keywords a user would say are present ('Recreate', 'website', 'app', 'URL'), giving good coverage; the very common synonym 'clone' is absent, which is the main gap.

4 / 5

Distinctiveness Conflict Risk

The niche (recreating an authorized live URL as a frontend-only local implementation) is fairly distinct and scoped by 'authorized' and 'frontend-only', with only minor overlap risk against general frontend/build skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.