From zeabur
Deletes a Zeabur service by ID after user confirmation. Triggered by phrases like 'delete service', 'remove service', or 'tear down service'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zeabur:zeabur-service-deleteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Always use `npx zeabur@latest` to invoke Zeabur CLI.** Never use `zeabur` directly or any other installation method. If `npx` is not available, install Node.js first.
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
Deleting a service removes its deployments, domains, and data. This is irreversible — always confirm with the user before proceeding.
Before deleting:
npx zeabur@latest service delete -i=false --id <service-id> -y
| Flag | Description |
|---|---|
--id | Service ID to delete |
-y, --yes | Skip confirmation prompt |
-i=false | Non-interactive mode (always use this) |
# 1. List services to find the target (use the `zeabur-service-list` skill)
npx zeabur@latest service list --project-id <project-id> -i=false --json
# 2. Confirm with user: "Delete <service-name> (<service-id>)?"
# 3. Delete
npx zeabur@latest service delete -i=false --id <service-id> -y
To delete an entire project instead, use the zeabur-project-delete skill.
npx claudepluginhub zeabur/agent-skills --plugin zeaburDeletes Zeabur projects by ID or name with safety confirmations. Lists projects first, then removes all services and data. Use for tearing down test or temporary projects.
Cleans up and removes all platform resources for an agent project — runtime, identity, auth, memory, registry, and API keys. Use when the user wants to tear down, decommission, or delete all resources for an agent.