Skip to content
Development
Skill

/stitch-mcp-list-projects

Lists all Stitch projects accessible to the user. Use this to find an existing project ID before resuming work or generating new screens in an existing project.

From plugin
stitch-kit
4536 skills1 agent2 hooks
Install
$ npx -y skills add gabelul/stitch-kit --skill stitch-mcp-list-projects --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/stitch-mcp-list-projects

Context preview

The summary Claude sees to decide when to auto-load this skill.

Lists all Stitch projects accessible to the user. Use this to find an existing project ID before resuming work or generating new screens in an existing project.

SKILL.md

stitch-mcp-list-projects.SKILL.md
name: stitch-mcp-list-projects
description: Lists all Stitch projects accessible to the user. Use this to find an existing project ID before resuming work or generating new screens in an existing project.
allowed-tools:
  - "stitch*:*"

Stitch MCP — List Projects

Lists Stitch projects available to the user. Use this when you need to find an existing projectId rather than creating a new project.

Critical prerequisite

**Only use this skill when the user explicitly mentions "Stitch".**

When to use

  • User says "continue working on my Stitch project" without providing an ID
  • User says "list my Stitch projects" or "what projects do I have?"
  • You need to find an existing projectId before calling `generate_screen_from_text`
  • Checking whether a project already exists before creating a new one

Call the MCP tool

**To list owned projects (default):**

{
  "name": "list_projects",
  "arguments": {
    "filter": "view=owned"
  }
}

**To list projects shared with the user:**

{
  "name": "list_projects",
  "arguments": {
    "filter": "view=shared"
  }
}

**To list all accessible projects (owned + shared):**

{
  "name": "list_projects",
  "arguments": {}
}

Output schema

{
  "projects": [
    {
      "name": "projects/3780309359108792857",
      "title": "Analytics Dashboard",
      "updateTime": "2024-11-15T10:30:00Z"
    }
  ]
}

After listing

1. Present the project list to the user with titles and last-updated timestamps 2. Ask which project to work in (if multiple) 3. Extract the numeric ID from the chosen `name` field: `projects/ID` → `ID` 4. Store both the full name and numeric ID for subsequent calls

ID format reminder

  • `list_screens`, `get_project` → use `projects/NUMERIC_ID`
  • `generate_screen_from_text`, `get_screen` → use `NUMERIC_ID` only
Read more
Ships withstitch-kit

Your coding agent writes decent code and designs terrible UI. stitch-kit fixes the second half — it wires agents into Google Stitch (text prompts → genuinely beautiful screens) and teaches them to drive it properly.

Get the whole plugin

Other skills on stitch-kit.