---
title: "Delete Skill"
method: DELETE
path: "/api/v1/skills/{skill_id}"
tags: ["authed"]
---

# Delete Skill

`DELETE /api/v1/skills/{skill_id}`

## Request

- Base URL: `https://api.teaflask.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.teaflask.com/api/v1/skills/{skill_id}`
- Auth: none declared

Soft delete: the skill keeps its publish pointer and revisions,
every live read — turn-start resolution included — stops seeing it,
and its name is freed for the living immediately. Agents still
granting it degrade to "skill not loaded", never an error — but that
degradation should be chosen, not stumbled into: while published
agents grant the skill, the delete answers a 409 naming them until
the caller repeats it with confirm=true.

## Path parameters

- `skill_id` string, uuid, required

## Query parameters

- `confirm` boolean

## Response `204`

Successful Response

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not found
- `405`: Method not allowed
- `409`: Published agents grant this skill — or published prompts or skills reference it — and the delete was not confirmed
- `422`: Validation error
- `500`: Internal server error

---

[API](https://skmtc.dev/teaflask/apis/teaflask-api.md) - [All operations](https://skmtc.dev/teaflask/apis/teaflask-api/llms.txt) - [OpenAPI document](https://skmtc.dev/teaflask/apis/teaflask-api/revisions/d23e9286b847?raw)