Google Stitch Mockup Extraction

VerifiedCaution

Automatically extracts generated mockup images from Google Stitch project pages using Playwright. Downloads and organizes design assets into a structured directory hierarchy.

Sby Skills Guide Bot
ContentIntermediate
3/4/2026
Claude Code
#stitch#mockups#playwright#browser-automation#design-assets

Recommended for

Automated summary

Extracts generated mockup images from a Google Stitch project page into a local exports folder using a Playwright script driven by an authenticated Chrome browser.

Strengths

  • Resolves the target feature directory by matching the Stitch project title against existing .google-stitch/ directories, with a fallback prompt
  • Filters images by source URL and by size (>= 400px) so only mockups are kept and icons or UI chrome are dropped
  • Detects the "Generating..." state and aborts with a retry message instead of saving incomplete assets
  • Prints a summary report listing each extracted file, its dimensions, and the destination folder tree

Limitations

  • Requires a Chrome profile signed into Google plus Playwright browsers installed through uv
  • Assumes a .google-stitch/{feature}/ directory convention that is usually created beforehand by a companion prompt-authoring skill
  • Relies on Stitch's current markup and lh3.googleusercontent.com/aida/ image URLs, so it can break when the site changes
When to use it

Use it when someone hands over a stitch.withgoogle.com project URL and wants the generated mockups archived locally.

When not to use it

Avoid it without an authenticated Google session or while Stitch is still generating, and outside a project laid out with .google-stitch/ feature directories.

Security analysis

Caution
Quality score85/100

The skill uses powerful local tools and an authenticated browser session to extract images, which is legitimate but carries meaningful execution and account-access risk. No destructive, exfiltration, or obfuscated commands appear in SKILL.md, but the safety of the referenced extraction script depends on its bundled implementation.

Findings
  • •Requires an authenticated Chrome browser profile with an active Google session, so the automation can access logged-in account data.
  • •Runs a bundled Python script via uv/Playwright, but the script contents are not included in SKILL.md; actual behavior cannot be fully audited from the instructions alone.
  • •Writes image files into project-local .google-stitch directories; path handling and overwrite behavior are not described.
How this analysis is made

Examples

Extract a Stitch project
Extract the mockups from https://stitch.withgoogle.com/projects/123 and save them to my exports folder.
Target a specific feature
Download the Stitch designs at https://stitch.withgoogle.com/projects/456 into the dashboard feature directory.
Archive all generated designs
I need to archive the mockup images generated in my Stitch project — here's the project URL.

name: extracting-stitch-mockups description: > Extracts generated mockup images from Google Stitch project pages. Use when user provides a Stitch project URL (stitch.withgoogle.com/projects/...), mentions extracting/downloading Stitch mockups, saving Stitch designs, or wants to archive generated design assets. Requires authenticated Chrome browser profile. allowed-tools: Read, Write, Bash, Grep, Glob

Extract Stitch Mockups

Quick Start

  1. Get project URL - User provides https://stitch.withgoogle.com/projects/{id}
  2. Resolve feature directory - Determine where to save using fallback chain
  3. Run extraction script - Execute scripts/extract_images.py with Playwright
  4. Save to exports - Images saved to .google-stitch/{feature}/exports/

Feature Directory Resolution

Determine target feature directory using this fallback chain:

  1. User specifies - Optional --feature argument provided
  2. Auto-detect - Match Stitch project title to existing .google-stitch/{feature}/ directories
  3. Prompt user - List existing directories and ask user to select or create new

Auto-Detection Logic

  • Extract project title from Stitch page (e.g., "Eco-Travel Home Screen")
  • Normalize to feature format: lowercase, hyphens, strip special chars
  • Search for matching directory in .google-stitch/
  • If multiple partial matches, prompt user to select

Extraction Process

Prerequisites

  • Chrome browser with active Google session
  • uv installed (https://github.com/astral-sh/uv)
  • Playwright browsers: uv run playwright install chromium

Script Execution

# Basic usage
uv run scripts/extract_images.py "https://stitch.withgoogle.com/projects/123"

# With explicit feature directory
uv run scripts/extract_images.py "https://stitch.withgoogle.com/projects/123" --feature dashboard

# Or run directly (after chmod +x)
./scripts/extract_images.py "https://stitch.withgoogle.com/projects/123"

Image Filtering

  • Source: lh3.googleusercontent.com/aida/... URLs only
  • Size filter: Images with dimensions >= 400px (mockups, not UI elements)
  • Excludes: avatars, icons, UI chrome

Generation Check

Script checks for "Generating..." status on page:

  • If detected: Exit with message to retry after generation completes
  • If complete: Proceed with extraction

Output Structure

Images saved to existing feature's exports/ directory:

.google-stitch/{feature}/exports/
├── mockup-1.png
├── mockup-2.png
└── mockup-N.png

File Naming

  • Sequential numbering: mockup-{index}.png
  • Index starts at 1
  • Preserves original image format (typically PNG)

Report

After extraction, display summary:

Extracted {N} mockups from Stitch project

Project: {project-title}
URL: {project-url}

Saved to: .google-stitch/{feature}/exports/
  - mockup-1.png (400x800)
  - mockup-2.png (400x800)
  - ...

Feature directory:
  .google-stitch/{feature}/
  ├── prompt-v{N}.md
  ├── exports/          <- Mockups saved here
  │   ├── mockup-1.png
  │   └── mockup-2.png
  └── wireframes/

Common Issues

  • Not authenticated - Open Chrome, sign into Google, then retry
  • Still generating - Wait for Stitch to complete, then retry
  • No feature directory - Run authoring-stitch-prompts first, or specify --feature

See TROUBLESHOOTING.md for detailed solutions.

Reference Files

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/google-stitch-mockup-extraction-mmbizjpx/download' --output '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md.part' && mv '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md.part' '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Bash, Grep, Glob

Original excerpt: Prerequisites

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md' && test -s '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/extracting-stitch-mockups' && cp -R '.skill-downloads/google-stitch-mockup-extraction-mmbizjpx' '.claude/skills/extracting-stitch-mockups'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/google-stitch-mockup-extraction-mmbizjpx'

openskills read 'google-stitch-mockup-extraction-mmbizjpx'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/google-stitch-mockup-extraction-mmbizjpx/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills