CtrlK
BlogDocsLog inGet started
Tessl Logo

stitch-sdk-usage

Use the Stitch SDK to generate, edit, and iterate on UI screens from text prompts, manage projects, and retrieve screen HTML/images. Use when the user wants to consume the SDK in their application.

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

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/stitch-sdk-usage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured reference with excellent executable examples, but it is token-heavy and keeps a full API reference inline rather than progressively disclosing it, and workflows omit explicit validation checkpoints.

Suggestions

Move the verbose API Reference tables into a separate references/ file (e.g. REFERENCE.md) and link to it, keeping SKILL.md as a lean overview to improve progressive disclosure and conciseness.

Add explicit validation/retry checkpoints for the uploadImage, generate, and edit workflows (e.g., catch StitchError, inspect e.recoverable, retry on RATE_LIMITED) to lift workflow clarity.

Trim repeated `import { stitch } from "@google/stitch-sdk"` lines and consolidate the duplicated error-code lists to reduce token usage.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable code, but the large inline API-reference tables and repeated import statements add bulk that could be tightened or offloaded; it assumes Claude's competence but is not consistently lean.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript examples for every major operation plus concrete method signatures, options tables, and error codes, matching the 'fully executable code' anchor.

3 / 3

Workflow Clarity

Sections are well-labeled and the quick-start sequence is clear, but multi-step generation/iteration/upload workflows lack explicit validation or error-recovery checkpoints, which caps clarity at 2 per the destructive/batch-operation guideline.

2 / 3

Progressive Disclosure

Content is well-organized into sections, but it is a monolithic single-file skill with no bundle references and a large inline API reference that could live in a separate file; no references directory exists to split content one level deep.

2 / 3

Total

9

/

12

Passed

Description

82%

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 strong, specific description that clearly states capabilities and includes an explicit 'Use when' trigger. Trigger-term quality is the only weakness, as the phrasing is developer-oriented rather than mirroring natural user requests.

Suggestions

Add user-natural trigger phrasing such as 'Use when the user wants to generate UI screens or mockups from text, build a Stitch project, or work with the Stitch SDK' to broaden natural keyword coverage.

Consider mentioning '.ui' / mockup generation terms since users may phrase requests as 'turn this prompt into a screen' or 'generate a mockup'.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'generate, edit, and iterate on UI screens from text prompts, manage projects, and retrieve screen HTML/images' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It answers both 'what' (the listed SDK capabilities) and 'when' via an explicit 'Use when the user wants to consume the SDK in their application' clause, meeting the both-what-and-when anchor.

3 / 3

Trigger Term Quality

It includes natural terms like 'text prompts', 'UI screens', 'HTML/images', and 'SDK', but the only user-side trigger phrasing is 'consume the SDK in their application', which lacks common natural variations a user would actually say.

2 / 3

Distinctiveness Conflict Risk

The Stitch SDK / UI-screen-generation niche is specific and clearly distinct from other skills, with a trigger scoped to SDK consumption, making conflicts unlikely.

3 / 3

Total

11

/

12

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
google-labs-code/stitch-sdk
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.