Agent skill
stitch-mcp-list-screens
Lists all screens in a Stitch project. Use this after generate_screen_from_text to find the screenId of the newly generated screen, then call stitch-mcp-get-screen to retrieve it.
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-screens
SKILL.md
Stitch MCP — List Screens
Lists all screens contained within a specific Stitch project. You typically call this right after generate_screen_from_text to find the screenId of the screen that was just created.
Critical prerequisite
Only use this skill when the user explicitly mentions "Stitch".
When to use
- Immediately after
generate_screen_from_text— to find the new screen's ID - User wants to browse all screens in a project
- You need a
screenIdto callget_screen - Checking what screens already exist before generating a new one
Call the MCP tool
Important: Use the projects/ID format — not the numeric ID alone.
{
"name": "list_screens",
"arguments": {
"projectId": "projects/3780309359108792857"
}
}
✅ "projects/3780309359108792857"
❌ "3780309359108792857"
Output schema
{
"screens": [
{
"name": "projects/3780309359108792857/screens/88805abc123def456",
"title": "Login Screen",
"screenshot": {
"downloadUrl": "https://storage.googleapis.com/..."
},
"deviceType": "MOBILE"
}
]
}
After listing
- Identify the target screen (usually the most recently generated — last in the list)
- Extract the numeric
screenIdfrom thenamefield:"projects/3780309359108792857/screens/88805abc123def456"→ screenId ="88805abc123def456"
- Call
stitch-mcp-get-screenwith the numericprojectIdandscreenId
ID format reminder
For the next call (get_screen), you need the numeric IDs for both project and screen:
projectId→3780309359108792857(stripprojects/prefix)screenId→88805abc123def456(stripprojects/.../screens/prefix)
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?