CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stitch-ui-design

Expert guidance for crafting effective prompts in Google Stitch, the AI-powered UI design tool by Google Labs. This skill helps create precise, actionable prompts that generate high-quality UI designs for web and mobile applications.

Quality

70%

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/AI-Agents-Safe-Coding-Skills/skills/stitch-ui-design/SKILL.md

The canonical home for this skill is stitch-ui-design in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 highly actionable, with copy-paste-ready prompt templates and examples covering the main use cases, and its iteration/export workflows are clearly sequenced with informal checkpoints. Its main weaknesses are padded filler sections and a progressive-disclosure failure: two reference files exist in the bundle but are never referenced from SKILL.md, which instead inlines a large prompt-example library that duplicates them.

Suggestions

Reference the bundle files explicitly and move the inlined 'Common Use Cases' prompt library to references/prompt-examples.md (e.g. "## Common use cases — see [prompt-examples.md](references/prompt-examples.md)"), keeping only 1-2 exemplar prompts inline.

Add a clearly signaled 'Advanced techniques' section pointing to references/advanced-techniques.md (image-to-UI workflows, design system integration, accessibility) so the file is discoverable.

Delete the filler sections — the intro paragraph duplicating the frontmatter description, the 'Conclusion' summary, and the vacuous 'When to Use' line — to tighten conciseness.

DimensionReasoningScore

Conciseness

Quotes: "Expert guidance for crafting effective prompts in Google Stitch... This skill helps create precise, actionable prompts..." (the opening paragraph duplicates the frontmatter description verbatim), "## Conclusion ... Effective Stitch prompts are specific, context-rich, and visually descriptive", and "## When to Use ... This skill is applicable to execute the workflow or actions described in the overview" (pure filler). The bulk of the body is example-driven and earns its tokens, but the duplicated intro, summary Conclusion, filler 'When to Use' line, and the Anti-Patterns section restating Principle 1 ('Generic prompts yield generic results' vs '❌ Vague Prompts') are unnecessary. Not a 4 due to these several padded sections; not a 2 because most sections deliver concrete, non-redundant guidance.

3 / 5

Actionability

Quotes: the Prompt Structure Template ("[Screen/Component Type] for [User/Context] ... Platform: [Mobile/Web/Responsive]"), concrete poor/effective prompt pairs ("Create a dashboard" vs "Member dashboard with course modules grid, progress tracking bar..."), and copy-paste-ready use-case prompts for landing pages, mobile apps, dashboards, and forms. For an instruction-only prompting skill this is fully executable guidance with specific examples covering the common cases — exactly the anchor-5 standard; scoring note confirms code absence is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

Quotes: the annotate-to-edit workflow ("1. Generate initial design from prompt 2. Annotate specific elements ... 4. Stitch updates only the annotated areas"), progressive refinement ("Initial: E-commerce homepage → Refinement 1: ... → Refinement 2: ..."), and export checklists ("Before exporting: Verify responsive breakpoints; Check color contrast for accessibility"). Sequences are clear and validation-style checklists are present, but they are informal review prompts without explicit error-recovery loops, matching 'Clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because there is no validate/fix/retry feedback loop; not a 3 because checkpoints like the before-export checklist and 'Stitch will ask for confirmation before generating multiple screens' are explicit.

4 / 5

Progressive Disclosure

The bundle contains references/advanced-techniques.md and references/prompt-examples.md, but grep of the body shows no mention of either file — the references are completely unsignaled and orphaned. Meanwhile ~75 lines of inlined use-case prompts ("### Landing Pages", "### Mobile Apps", "### Dashboards", "### Forms and Inputs") duplicate the purpose of prompt-examples.md, and advanced material (e.g. image-to-UI workflows documented in advanced-techniques.md) is only hinted at. This matches 'content that clearly belongs in separate files is inlined; or references are buried'. Not a 3 because unlike the anchor-3 example the body never signals the reference files at all ('See ADVANCED.md' is absent); not a 1 because the body itself is well-sectioned and the references are only one level deep, not nested.

2 / 5

Total

14

/

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 names a specific niche (Google Stitch prompt crafting) with a clear 'what' and reasonable natural trigger terms, but it never states when to use the skill. Adding an explicit 'Use when...' clause with trigger synonyms (mockup, wireframe, prototype) would raise both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Stitch, wants to generate UI designs or app screens from text or sketches, or asks for mockups, wireframes, or prototypes."

Include natural synonyms users would say — "mockup", "wireframe", "prototype", "app design", "landing page design" — to broaden trigger coverage beyond "prompts" and "UI designs".

Distinguish the concrete actions more sharply (e.g. mention image/sketch-to-UI conversion and multi-screen app flows) instead of restating prompt-writing twice with different adjectives.

DimensionReasoningScore

Specificity

Quotes: "crafting effective prompts in Google Stitch" and "create precise, actionable prompts that generate high-quality UI designs". The domain is clearly named, but the only concrete action (prompt crafting) is stated twice with different adjectives rather than listing several distinct actions, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. Not a 4 because there are no additional specific actions beyond prompt-writing; not a 2 because the domain and action are concrete, not generic.

3 / 5

Completeness

Quotes: "This skill helps create precise, actionable prompts that generate high-quality UI designs for web and mobile applications" — a clear 'what'. There is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is entirely absent rather than present-but-vague; not a 2 because the 'what' is clear and specific.

3 / 5

Trigger Term Quality

Quotes: "Google Stitch", "prompts", "UI designs", "web and mobile applications". These are natural terms a user would say when needing this skill, giving good keyword coverage; a few natural synonyms like "mockup", "wireframe", "prototype", or "app/screen design" are missing. Not a 5 because synonym and variation coverage is incomplete; not a 3 because multiple distinct natural trigger terms are present, not just some relevant keywords.

4 / 5

Distinctiveness Conflict Risk

Quotes: "prompts in Google Stitch, the AI-powered UI design tool by Google Labs" — a clear niche with a named, specific tool. Minor overlap risk remains with general UI-design or design-prompting skills triggered by phrases like "UI design". Not a 5 because the broader UI-design phrasing could pull in general design skills; not a 3 because the Stitch-specific framing makes confusion with other skills unlikely.

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/stitch-ui-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.