stitch::upload-to-stitch
google-labs-code/stitch-skills · 9.2k installs · 8.5K stars
Skill
Install
npx -y skills add google-labs-code/stitch-skills --skill stitch::upload-to-stitch --agent claude-codeRun in a terminal. Claude loads the skill when a task calls for it. Check the repo's README before you run it.
Files
Upload-to-Stitch
Upload local assets (images, mockups, HTML, and markdown files) to a Stitch project using the provided upload script, which bypasses the MCP tool's base64 output token limits.
[!NOTE] The AI model cannot upload files via MCP tools directly because the base64 encoding of even a small file exceeds the model's output token limit (~16K tokens). This script reads the file and sends it directly over HTTP.
Steps
1. Identify Target Project
Use list_projects to find the correct projectId.
2. Get the API Key
Locate your active MCP server configuration file and extract the API key:
- Antigravity:
.gemini/antigravity/mcp_config.jsonor.gemini/jetski/mcp_config.json - Gemini CLI:
~/.gemini/settings.jsonor~/.gemini/extensions/Stitch/gemini-extension.json - Claude Code:
~/.claude.json
Extract:
- API Key: From the
X-Goog-Api-Keyheader or auth argument - MCP URL (optional): From the
httpUrlor endpoint argument (defaults tohttps://stitch.googleapis.com)
[!IMPORTANT] If you cannot find the API key in any of these locations, or if you cannot access these files, you MUST ask the user to provide the Stitch API key. Do not proceed without a valid API key.
3. Run Upload Script
[!WARNING] Checkpoint — User Confirmation Required. Before running the upload script, you MUST pause and present the file(s) to be uploaded (paths, sizes, and types) to the user and wait for explicit approval. Do NOT execute the upload script until the user confirms.
Use run_command to execute the Python script:
python3 <SKILL_DIR>/scripts/upload_to_stitch.py \
--project-id <PROJECT_ID> \
--file-path <PATH_TO_FILE> \
--api-key <API_KEY> \
[--api-url <STITCH_API_URL>] \
[--title <SCREEN_TITLE>] \
[--generated-by <GENERATED_BY>]
[!TIP] macOS / SSL Certificate Troubleshooting: If the upload fails with
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] unable to get local issuer certificate, this means your Python installation does not have root certificate authorities configured.The script automatically attempts to use the
certifipackage to load the CA bundle if it is installed in your python environment. Ifcertifiis not installed, you can either install it (pip install certifi) or manually supply theSSL_CERT_FILEenvironment variable when running the script:SSL_CERT_FILE=$(python3 -c "import certifi; print(certifi.where())") python3 <SKILL_DIR>/scripts/upload_to_stitch.py \ --project-id <PROJECT_ID> \ --file-path <PATH_TO_FILE> \ --api-key <API_KEY> \ [--api-url <STITCH_API_URL>] \ [--title <SCREEN_TITLE>] \ [--generated-by <GENERATED_BY>]
Supported File Types
| Extension | MIME Type |
|---|---|
.png |
image/png |
.jpg, .jpeg |
image/jpeg |
.webp |
image/webp |
.html, .htm |
text/html |
.md |
text/markdown |
The script auto-detects MIME type from the file extension.
Script Options
--project-id: Required. The Stitch project ID.--file-path: Required. Path to the local file to upload.--api-key: Required. API key for Stitch authorization.--api-url: Optional. Base URL of the Stitch API. Defaults tohttps://stitch.googleapis.com.--title: Optional. Title for the uploaded screen. When uploading extracted HTML from a web app, set this to the route path of the page (e.g.,'/dashboard','/settings/profile','/inbox') so that the screen name/title in Stitch clearly identifies the route.--generated-by: Optional. Specify how the uploaded file was generated (e.g., 'stitch::extract-static-html' skill, 'Claude Code', 'Codex', 'Gemini' etc.).
Facts
- Kind
- Skill
- Repo
- google-labs-code/stitch-skills
- Group
- Uncategorized
- Installs
- 9.2k
- Stars
- 8.5K
- 1find-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.3.8M
- 2grill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.3M
- 3grill-with-docsmattpocock/skillsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.1.1M
- 4agent-browservercel-labs/agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.1.1M
- 5improve-codebase-architecturemattpocock/skillsScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.1.1M
- 6tddmattpocock/skillsTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.1.1M