Agent 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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/stitch-mcp-list-projects
SKILL.md
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
- Present the project list to the user with titles and last-updated timestamps
- Ask which project to work in (if multiple)
- Extract the numeric ID from the chosen
namefield:projects/ID→ID - Store both the full name and numeric ID for subsequent calls
ID format reminder
list_screens,get_project→ useprojects/NUMERIC_IDgenerate_screen_from_text,get_screen→ useNUMERIC_IDonly
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?