Skip to content
Agent Skills Tool

Stitch Agent Skills Installer & Setup Guide

Install Stitch Agent Skills with an agent-specific plan from Loop Engineering. Choose plugins or individual skills, connect Stitch MCP and check that your agent can discover the workflow.

Install Stitch Agent Skills

Choose a setup. Review commands before running them.

Browser-only tool

Step 3 — Command & next steps

This Loop Engineering tool only displays and copies instructions. Nothing runs, connects or uploads from this page.

install.sh
codex plugin marketplace add google-labs-code/stitch-skills --ref main \
--sparse .agents/plugins \
--sparse plugins/stitch-design \
--sparse plugins/stitch-build \
--sparse plugins/stitch-utilities
  • Stitch MCP is not configured yet. You can review installation steps now, but Stitch-dependent workflows need an authenticated connection first.
  1. After registration, install and enable stitch-design, stitch-build, stitch-utilities using the Codex plugin interface. The registration command alone installs no plugins.
  2. UI alternative: Settings → Plugin Marketplaces → Add; source https://github.com/google-labs-code/stitch-skills, Git ref main, optional sparse paths matching the command.

What this installs

16 skills across stitch-design, stitch-build, stitch-utilities. Recommended here means the complete suite; choose a family or one skill for a smaller setup.

Selected skills & source folders

Where it installs

Registered marketplace; install and enable the chosen plugins in Codex.

Keep plugin-managed files in their managed location. Individual skill installers show the destination before confirmation.

Prerequisites

  • Stitch MCP configured and connected in this agent.
  • Review the source skill and any bundled scripts before installation.
  • For npx commands, have Node.js and npm available.

Next verification step

  1. Confirm the stitch-skills marketplace is registered and the chosen plugins are installed and enabled in Codex.
  2. In Codex CLI, open /skills or type $ to confirm the expected skill is discoverable.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Last verified: 2026-10-05 · Source README

Last verified: . Based on Google Labs Code’s open-source Stitch Skills repository and Stitch MCP documentation. The repository is not an officially supported Google product. This installer is maintained independently by Loop Engineering.

What Are Stitch Agent Skills?

An Agent Skill is a workflow package centered on SKILL.md: a name, a description of when to use it and instructions the coding agent can load for a relevant task. The Stitch repository packages design and implementation workflows with supporting resources, examples and scripts. Preserve those files when installing a skill; the markdown alone may refer to missing tools or templates.

The agent discovers the skill and follows its procedure. Work that reads or changes Stitch projects also needs a connected Stitch MCP server. For Loop Engineering, treat each skill as a maintained procedure: inspect its permissions, define a stop rule and verify a small task before granting broader access. Agent Skills format reference.

Stitch Agent Skills vs Stitch MCP

CheckStitch Agent SkillsStitch MCP
PurposeTell the agent how to carry out a workflow.Give the agent tools to access Stitch.
InstallationPlugin packages or SKILL.md folders and their resources.Remote server configuration and authentication.
Successful setupThe intended skill is discoverable in the agent.Stitch tools are visible and can list your projects.
CredentialsCopying a skill folder does not authenticate Stitch.The client holds local credentials and project access.

Available Stitch Plugins

Three plugin families organize the current repository. The recommended setup in this tool selects all three; it is a complete starting point, with narrower choices available. The inspected source tree contains 16 skills, including site-md, which was not yet in the README’s summary table on the verification date.

stitch-design

Create and adapt screens, bring code into Stitch and manage design assets.

6 skills

stitch-build

Turn designs into components, dashboards and walkthrough assets.

5 skills

stitch-utilities

Prepare design and site specifications, improve prompts and coordinate build loops.

5 skills

Which Stitch Skill Should I Install?

Match the task to a source skill. Names below are the repository’s frontmatter names; OpenCode needs the naming adaptation described in its setup. A selective install may need supporting skills: code-to-design orchestrates extraction and upload workflows; generate-design has conditional design-system and image-upload branches; stitch-loop uses design/site context.

Install Stitch Skills for Codex

Registered marketplace; install and enable the chosen plugins in Codex.

install.sh
codex plugin marketplace add google-labs-code/stitch-skills --ref main \
--sparse .agents/plugins \
--sparse plugins/stitch-design \
--sparse plugins/stitch-build \
--sparse plugins/stitch-utilities
  1. After registration, install and enable stitch-design, stitch-build, stitch-utilities using the Codex plugin interface. The registration command alone installs no plugins.
  2. UI alternative: Settings → Plugin Marketplaces → Add; source https://github.com/google-labs-code/stitch-skills, Git ref main, optional sparse paths matching the command.

Stitch MCP setup for Codex

  • Follow Stitch’s remote MCP authentication guide.
  • Add the authenticated remote server in your Codex MCP configuration. Use your client’s supported secret handling; marketplace registration does not prove MCP is connected.

Stitch MCP authentication guide · Codex skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install Stitch Skills for Claude Code

Current project (--scope project). Run from the intended project root.

install.sh
npx plugins add google-labs-code/stitch-skills --scope project --target claude-code
  1. Run in the intended project/workspace and review the installer’s scope and selected plugins before confirming.

Stitch MCP setup for Claude Code

  • Create a key in Stitch Settings and register the remote HTTP server using the provider’s example.
  • The MCP example uses user scope (-s user); this is separate from the project-scoped skill installation. Keep credentials out of version control.

MCP registration example — replace api-key locally

mcp-setup.sh
claude mcp add stitch --transport http https://stitch.googleapis.com/mcp --header "X-Goog-Api-Key: api-key" -s user

Stitch MCP authentication guide · Claude Code skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install Stitch Skills for Cursor

Current workspace (--scope workspace). Open the intended workspace first.

install.sh
npx plugins add google-labs-code/stitch-skills --scope workspace --target cursor
  1. Run in the intended project/workspace and review the installer’s scope and selected plugins before confirming.

Stitch MCP setup for Cursor

  • Configure the remote server in .cursor/mcp.json using Stitch’s official example.
  • Replace the API-key placeholder only in your local configuration; verify the server connects.

.cursor/mcp.json — merge into existing configuration

mcp-config.json
{
"mcpServers": {
"stitch": {
"url": "https://stitch.googleapis.com/mcp",
"headers": {
"X-Goog-Api-Key": "YOUR-API-KEY"
}
}
}
}

Stitch MCP authentication guide · Cursor skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install Stitch Skills for Gemini CLI

Compatible, but no dedicated one-command flow is documented here.

  1. Download or clone the source repository from its link. Read the selected SKILL.md files and their bundled scripts before copying.
  2. Copy each complete skill folder, including scripts/resources/examples, from the source paths below into the intended project’s .gemini/skills/ directory. Keep SKILL.md directly inside its own folder; do not overwrite an existing skill.
  3. The destination is your working project, not the downloaded Stitch repository. Use the agent’s documented user directory only when you intentionally want global scope.
  4. Configure Stitch MCP separately using the prerequisite checklist, then perform the agent-specific discovery checks below.

Project skill path: .gemini/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Workspace skills in .gemini/skills; user skills in ~/.gemini/skills.

Stitch MCP setup for Gemini CLI

  • Stitch’s MCP guide documents the Gemini CLI Stitch extension. Install it separately from Agent Skills and complete authentication.
  • Check the extension’s MCP connection before using a Stitch-dependent skill.

Stitch MCP extension — does not install this skills repository

mcp-setup.sh
gemini extensions install https://github.com/gemini-cli-extensions/stitch

Stitch MCP authentication guide · Gemini CLI skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install Stitch Skills for OpenCode

Manual setup required. The repository explicitly excludes npx plugins and npx skills for OpenCode.

  1. Download or clone the source repository from its link. Read the selected SKILL.md files and their bundled scripts before copying.
  2. Copy each complete skill folder, including scripts/resources/examples, from the source paths below into the intended project’s .opencode/skills/ directory. Keep SKILL.md directly inside its own folder; do not overwrite an existing skill.
  3. The destination is your working project, not the downloaded Stitch repository. Use the agent’s documented user directory only when you intentionally want global scope.
  4. Rename namespaced frontmatter such as stitch::generate-design to generate-design. The lowercase kebab-case name must match the folder; keep description. Unknown fields such as allowed-tools are ignored. Adapt web_fetch/run_command references to OpenCode’s webfetch/bash tools and review inter-skill references after renaming.
  5. Configure Stitch MCP separately using the prerequisite checklist, then perform the agent-specific discovery checks below.

Project skill path: .opencode/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Project-local .opencode/skills; optional user path ~/.config/opencode/skills.

Stitch MCP setup for OpenCode

  • Merge a remote stitch entry into project opencode.json (or your user config) after authenticating with Stitch.
  • Replace YOUR_STITCH_MCP_URL and add the authentication required by the official setup guide. A URL alone does not authenticate.

opencode.json — template, not a complete authenticated configuration

mcp-config.json
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stitch": {
"type": "remote",
"url": "YOUR_STITCH_MCP_URL",
"enabled": true
}
}
}

Stitch MCP authentication guide · OpenCode skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install Stitch Skills for Antigravity

Compatible, but no dedicated one-command flow is documented here.

  1. Download or clone the source repository from its link. Read the selected SKILL.md files and their bundled scripts before copying.
  2. Copy each complete skill folder, including scripts/resources/examples, from the source paths below into the intended project’s .agents/skills/ directory. Keep SKILL.md directly inside its own folder; do not overwrite an existing skill.
  3. The destination is your working project, not the downloaded Stitch repository. Use the agent’s documented user directory only when you intentionally want global scope.
  4. Configure Stitch MCP separately using the prerequisite checklist, then perform the agent-specific discovery checks below.

Project skill path: .agents/skills/<folder>/SKILL.md. The skill folders are under plugins/stitch-design/skills, plugins/stitch-build/skills and plugins/stitch-utilities/skills in the source repository. Copy complete folders, then check the scope: Workspace skills in .agents/skills. Global locations vary by Antigravity surface.

Stitch MCP setup for Antigravity

  • In the Agent Panel, open MCP Servers → Manage MCP Servers → View raw config.
  • Merge the provider’s serverUrl example and configure credentials locally.

Antigravity MCP configuration — merge, do not overwrite

mcp-config.json
{
"mcpServers": {
"stitch": {
"serverUrl": "https://stitch.googleapis.com/mcp",
"headers": {
"X-Goog-Api-Key": "YOUR-API-KEY"
}
}
}
}

Stitch MCP authentication guide · Antigravity skills documentation. Merge configuration into existing files; replace credential placeholders only on your machine.

Install One Stitch Skill Only

For Codex, Claude Code or Cursor, open the current README’s interactive skills installer below. Select a skill by its exact name, the target agent and the intended scope. This entry point does not automatically narrow the installation to the skill selected on this webpage. The README does not document noninteractive selection flags, so this tool does not generate them. Inspect referenced supporting skills before confirming; a single folder may not cover an orchestrated workflow.

install-one.sh
npx skills add google-labs-code/stitch-skills

For example, choose enhance-prompt for prompt refinement, or stitch::react-components for React output. For OpenCode, use the complete-folder manual route and normalize the frontmatter name. Gemini CLI and Antigravity have manual paths in this guide because the repository lists compatibility without a dedicated plugin command. Interactive skills CLI reference.

How to Verify Installation

Check skill discovery first, then MCP connectivity. Finally try a small, relevant task in a disposable project with an explicit stop rule and human approval before any upload or design change. The connection check below only asks to list existing projects; it does not create or edit screens.

Codex

  1. Confirm the stitch-skills marketplace is registered and the chosen plugins are installed and enabled in Codex.
  2. In Codex CLI, open /skills or type $ to confirm the expected skill is discoverable.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Claude Code

  1. Open Claude Code’s / menu and look for the installed plugin’s skills; plugin commands are namespaced.
  2. Ask which skills are available and confirm the intended Stitch skill.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Cursor

  1. Open Customize → Skills and confirm the Stitch skills appear in Agent Decides.
  2. Check the skill is available in the workspace where you installed it.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Gemini CLI

  1. In Gemini CLI, run /skills reload and /skills list to confirm discovery.
  2. Check the workspace/user scope and the exact frontmatter name.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

OpenCode

  1. Check OpenCode’s skill tool description lists the installed names.
  2. Confirm each frontmatter name is lowercase kebab-case and matches its containing folder.
  3. Check skill permissions: denied skills are not discoverable.
  4. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Antigravity

  1. Use the workspace .agents/skills path described in Antigravity’s current skills documentation.
  2. Confirm discovery in a new conversation and invoke the intended skill by its available name.
  3. Confirm Stitch tools are visible, then ask the agent to list your Stitch projects. This checks MCP connectivity without creating or editing a design.

Common Errors

Stitch MCP not configured

Install instructions and a successful copy do not prove connectivity. Authenticate the remote server in your agent, confirm the tools appear, then ask to list your Stitch projects.

Skill installed but not discovered

Check the destination belongs to the working project and SKILL.md is directly inside the skill folder. Confirm the plugin is enabled, or use the agent’s discovery checks below. Preserve referenced resources when copying.

Deprecated add-skill command

Replace legacy npx add-skill examples with the current README’s npx skills add entry point. Recheck the source instead of adapting old flags by guesswork.

Wrong project or global scope

Run the plugin command from the intended project/workspace. In the interactive skills installer, confirm both target and scope before accepting. Manual global paths differ by agent.

Codex marketplace not registered

Register the stitch-skills marketplace with the README’s ref and four sparse paths. Then install and enable a plugin in the interface; registration alone is insufficient.

Wrong skill name or missing supporting skill

Use the source frontmatter name in the selected-skill list. Several Design names include stitch::. Selective installs may need supporting skills referenced by their SKILL.md; review those workflow branches.

OpenCode naming restrictions

Rename namespaced frontmatter to lowercase kebab-case and match the containing folder. Review renamed cross-skill references and webfetch/bash tool mappings. Check skill permissions if names remain hidden.

Missing environment or credential

npx flows require Node.js/npm and an available installer. MCP requires the provider’s authentication and project access. Keep keys local, avoid committing them, and use the official setup guide for OAuth renewal or changed authentication steps.

Build Your Own SKILL.md with Loop Engineering

Use Stitch skills for a specific design workflow. Use Loop Engineering to write the surrounding goal, verification steps, budget and approval gate. Keep the workflow small enough that a reviewer can tell whether it succeeded.

Stitch Agent Skills FAQ

What are Stitch Agent Skills?

Reusable SKILL.md workflow packages from Google Labs Code’s open-source Stitch Skills repository. They help compatible coding agents follow design and implementation procedures, using supporting files where needed.

How do I install Stitch Agent Skills?

Choose your agent in the installer. Codex registers the marketplace before plugin installation in its interface; Claude Code and Cursor have documented plugin commands. Other supported agents have manual steps here. Configure Stitch MCP separately.

Do Stitch Agent Skills work with Codex?

Yes. The repository documents marketplace registration with four sparse paths. Install and enable the chosen plugins afterward, then check discovery through /skills or the $ skill picker.

Do they work with Claude Code?

Yes. The repository provides a project-scoped plugin installation command targeting claude-code. Confirm the installed plugin’s skills in the / menu and separately verify Stitch MCP connectivity.

Do they work with Cursor?

Yes. The README documents workspace-scoped plugin installation targeting cursor. Check Customize → Skills in the intended workspace and verify the MCP connection.

Do I need Stitch MCP?

Stitch-dependent workflows need an authenticated Stitch MCP connection. Local preparation tasks may not call Stitch, but installing skill files alone does not connect your agent to the service.

What is the difference between Stitch MCP and Stitch Skills?

Skills describe how to carry out a workflow. MCP supplies the tool interface and authentication needed to access Stitch projects and screens. Both discovery and connectivity need separate verification.

Can I install one Stitch skill only?

Yes. Use the README’s npx skills add entry point and choose the desired skill, target agent and scope interactively. Review any supporting workflows first. OpenCode requires manual folder installation.

Is npx add-skill still correct?

That legacy command is deprecated for this guide. The current Stitch README uses npx skills add. The installer never recommends or generates npx add-skill.

Does OpenCode support Stitch Skills?

The README provides manual setup for OpenCode. Copy full skill folders into .opencode/skills, use lowercase kebab-case names matching folders, adapt tool references and configure Stitch MCP separately.

How do I install Stitch skills for Gemini CLI?

The repository lists Gemini CLI compatibility without a dedicated one-command plugin flow. This guide uses documented .gemini/skills folders and /skills reload plus /skills list for discovery. The Stitch MCP extension is installed separately.

Is this an officially supported Google product?

The repository belongs to Google Labs Code, but its README says it is not an officially supported Google product. This Loop Engineering installer is an independent guide and command preview.

Will this installer run commands or collect my credentials?

No. It generates static instructions in your browser, with no shell execution, account connection, credential input or data upload. Review commands before running them in your own environment.

Sources & Maintenance

Commands were checked against the README on 2026-10-05; skill names and folders were checked against the repository tree and individual SKILL.md files. These instructions are a dated snapshot. Recheck the upstream documentation before installing after a product update.