Rename a skill
Rename a skill. The new name must be unique within the requester’s org.
2026-06-01 — added to support publish-with-rename in PublishDialog.
Other tables reference skills by ID, so this is a single-row update on
skills.name. No cascading writes; agent bindings, fork lineage,
SkillShare grants, and install records continue to point at the same ID.
Enforces edit permission: only the creator, owning workspace editors, or org admins can rename.
Authorizations
Enter your API key (e.g. dai_sk_test_key_001)
Headers
Path Parameters
The skill's stable ID (prefixed 'sk_').
"sk_abc123"
Cookies
Body
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.
1 - 200