Skip to main content
POST
Rename a skill

Authorizations

Authorization
string
header
required

Enter your API key (e.g. dai_sk_test_key_001)

Headers

Authorization
string

Path Parameters

skill_id
string
required

The skill's stable ID (prefixed 'sk_').

Example:

"sk_abc123"

Cookies

decimal_session
string | null

Body

application/json

Validated request for POST /skills/{id}/rename.

2026-06-01 — added to support publish-with-rename in PublishDialog. A user wants to publish a fork under a public name different from their local name; the dialog renames the local skill first, then publishes under the new name. The new name must be a valid slug (same rule as fork); org-uniqueness + the public-slug freeze are checked in the route/service where org_id and visibility are available.

new_name
string
required
Required string length: 1 - 200

Response

Skill renamed.

status
string
required
Allowed value: "ok"
skill_id
string
required
old_name
string
required
new_name
string
required