Is deleting a Stitch project reversible?

No. Deleting a Stitch project is permanent and cannot be undone.

What format should I use for the project path?

Always use the full path with the 'projects/' prefix, e.g., projects/ID.

Can I delete multiple projects in one action?

No. Each deletion must be confirmed explicitly and performed one project at a time.

stitch-mcp-delete-project

npx machina-cli add skill gabelul/stitch-kit/stitch-mcp-delete-project --openclaw

Files (1)

SKILL.md

1.9 KB

Stitch MCP — Delete Project

Permanently deletes a Stitch project and all its screens, designs, and history. This action is irreversible.

Critical prerequisite

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

This is a destructive action. You MUST ask the user to confirm before calling delete_project. Never auto-delete.

When to use

User explicitly asks to delete a Stitch project
Cleaning up test/scratch projects after confirming with the user
The orchestrator offers project cleanup and the user accepts

Step 1: Confirm the project

Show the user what they're about to delete:

Call stitch-mcp-get-project with projects/[ID] to get the project title and screen count
Present: "You're about to permanently delete [title] ([N] screens). This cannot be undone. Proceed?"
Only continue if the user explicitly confirms

Step 2: Call the MCP tool

{
  "name": "delete_project",
  "arguments": {
    "name": "projects/3780309359108792857"
  }
}

`name` — full path with `projects/` prefix

✅ "projects/3780309359108792857"
❌ "3780309359108792857"

This follows the same format as get_project — both use projects/ID.

After deleting

Confirm: "Project [title] has been deleted."
Offer: "Want to see your remaining projects?" → stitch-mcp-list-projects
Do NOT attempt to access the deleted project's screens or data

Anti-patterns

Never delete without explicit user confirmation — even if the orchestrator suggests cleanup
Never delete multiple projects in a batch without confirming each one
Never use numeric ID — delete_project requires the full projects/ID path

Source

git clone https://github.com/gabelul/stitch-kit/blob/main/skills/stitch-mcp-delete-project/SKILL.mdView on GitHub

Overview

This skill permanently deletes a Stitch MCP project and all its screens, designs, and history. It is destructive and requires explicit user confirmation before invoking the delete_project action.

How This Skill Works

First fetch project details with stitch-mcp-get-project to show the title and screen count, then prompt the user with a clear confirmation message. If the user confirms, call delete_project with the full path projects/ID; after deletion, confirm success and offer to view remaining projects.

When to Use It

User explicitly asks to delete a Stitch project
Cleaning up test or scratch projects after user confirmation
The orchestrator offers project cleanup and the user accepts
During a cleanup flow where the user explicitly mentions Stitch and approves deletion
After deletion, confirm completion and offer to list remaining projects

Quick Start

Step 1: Confirm the project by calling stitch-mcp-get-project to fetch the title and screen count.
Step 2: Show the user a warning and request explicit confirmation to proceed.
Step 3: If confirmed, call the MCP tool delete_project with the full path projects/ID, then confirm deletion and offer to list remaining projects.

Best Practices

Only use this skill when the user explicitly mentions 'Stitch'.
Always require explicit user confirmation before calling delete_project.
Present the project title and screen count before prompting for confirmation.
Use the full path projects/ID when calling delete_project.
After deletion, confirm completion and offer to list remaining projects; never access deleted data.

Example Use Cases

An admin wants to remove a test Stitch project named 'QA-Sprint-01' with 4 screens; the agent fetches the project, shows the title and count, asks for confirmation, and upon consent calls delete_project with the full path (projects/QA-123).
During a staging cleanup, a scratch Stitch project is identified. The agent retrieves details, confirms with the user, and deletes using the projects/ID path, then offers to list remaining projects.
In an orchestration flow, the system proposes cleanup of a completed project; the user explicitly approves, and the agent executes delete_project with the correct full path.
A user attempts to delete without explicit confirmation; the agent blocks the action and re-prompts for confirmation to prevent accidental deletion.
After a project is deleted, the agent confirms completion and asks if the user wants to see remaining projects via stitch-mcp-list-projects.

Frequently Asked Questions

Add this skill to your agents