CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

muapi-url-to-design

Analyze a website URL and generate a redesigned, improved UI — recreate the visual design with modern aesthetics, better hierarchy, and fresh brand direction.

Quality

75%

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 ./library/visual/url-to-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured, instruction-style recipe with concrete models, prompts, and fallback commands, and an explicit error path for unreachable URLs. Its main gaps are the missing concrete muapi CLI invocation syntax and the absence of a post-generation verification checkpoint, plus minor token duplication of the description.

Suggestions

Show one complete `muapi image generate` invocation with actual flags (e.g. `muapi image generate --model gpt4o-text-to-image --aspect-ratio 9:16 --prompt "..."`) so the calls are copy-paste ready.

Add an explicit post-generation checkpoint: verify both request results succeeded (via `muapi predict wait`) and retry or report errors before presenting the mockups.

Remove the bold restatement of the frontmatter description and fold the Trigger Keywords into the description to trim duplicated tokens.

DimensionReasoningScore

Conciseness

The body is efficient — an inputs table, concrete prompts with exact model IDs, and operational notes — with no explanations of concepts Claude already knows. It is not level 5 because the bold restatement of the frontmatter description under the title is duplicated framing, and the 'Trigger Keywords' section largely repeats information that belongs in the description, tokens that could be trimmed.

4 / 5

Actionability

Guidance is largely concrete and executable: exact models ('gpt4o-edit', 'gpt4o-text-to-image', 'bytedance-seedream-v4.5'), full copy-paste-ready prompts with documented {{placeholder}} substitution, aspect ratios (9:16, 9:19.5), and a near-complete curl fallback command. It stops short of level 5 because the actual `muapi image generate` CLI invocation syntax (how the prompt, model, and aspect-ratio flags are passed) is never shown, and the curl fallback leaves `<endpoint>` and a literal `{...}` body unspecified.

4 / 5

Workflow Clarity

The sequence is clear — two parallel generation steps with conditional prompt logic (screenshot vs. no screenshot, keep_brand), then post-generation presentation steps — and it includes a real error-recovery path ('If the URL is unreachable, ask the user to provide a screenshot') plus polling via `muapi predict wait`. It is not level 5 because there is no explicit checkpoint verifying that both images generated successfully before presenting them. This is not a destructive or batch operation, so the level-3 validation cap does not apply.

4 / 5

Progressive Disclosure

The body is roughly 50 lines, single-purpose, well-organized into clearly labeled sections (Inputs, Steps, Notes, Trigger Keywords, Notes for the Executing Agent), contains no bundle files and no external references to break or nest — matching the rubric's simple-skill provision that short, well-sectioned skills with no external file needs score 5. It would drop if any reference pointed at a missing file, but none do.

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

The description is concise, third-person, and states a clear capability in a distinct niche, but it omits any explicit 'Use when...' trigger guidance, which both caps completeness and limits its trigger-term effectiveness. Adding a 'when' clause with natural trigger phrases would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user provides a website URL and asks for a redesign, mockup, or visual refresh of a page.'

Enumerate 1-2 more distinct concrete actions (e.g. 'generate desktop and mobile mockups') so the capability list reads as several specific actions rather than one restated deliverable.

Include natural synonyms users actually say — 'redesign my website', 'landing page mockup', 'modernize our site' — to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names a specific domain ('website URL') with a few concrete actions — 'Analyze a website URL', 'generate a redesigned, improved UI', 'recreate the visual design' — but the actions largely restate one deliverable rather than enumerating several distinct capabilities. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is not level 4 because there is no list of several distinct specific actions (compare the level-5 example's 'extract text and tables, fill forms, merge documents, convert pages').

3 / 5

Completeness

The 'what' is clear ('Analyze a website URL and generate a redesigned, improved UI'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is clearly the anchor 'Has a clear what but when is missing or only weakly implied', not level 4 which requires an explicit (if imperfect) 'when'.

3 / 5

Trigger Term Quality

Phrases like 'redesigned', 'improved UI', 'visual design', 'website URL', and 'brand direction' are natural terms a user would say when wanting a site redesign, giving good keyword coverage. It falls short of level 5 because common synonyms users actually say — 'redesign my website', 'mockup', 'landing page design', 'modernize' — are absent from the description (they only appear in the body's Trigger Keywords section, which is not the evaluation target here).

4 / 5

Distinctiveness Conflict Risk

The URL-input-to-UI-mockup niche is fairly distinct — the input ('a website URL') and output ('redesigned, improved UI') combination would rarely fire the wrong skill. It is not level 5 because there is some overlap risk with general frontend-development, image-generation, or design-system skills that also trigger on 'UI' and 'design' phrasing.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

SamurAIGPT/Generative-Media-Skills

Path

library/visual/url-to-design/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.