Update a skill

⚠️ This endpoint is deprecated and will be removed in a future release.

• For content updates, use Create a skill version: POST /api/v1/cloud/skills/{skill_id}/versions. When content is updated through this endpoint, a new version is created internally rather than overwriting in place.
• name cannot be changed: the skill name must stay consistent across all versions; sending a name different from the current one returns 400.
• Patch updates to description / metadata still work, but are also scheduled for removal.

​

Path parameters

​

Headers

​

Request body

​

Example request

curl -X PUT https://api.qoder.com.cn/api/v1/cloud/skills/skill_019e3bba474b73cfaf19eae9b5f5e66d \
  -H "Authorization: Bearer $QODER_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "description": "Updated skill description",
    "metadata": {"team":"docs","stage":"updated"}
  }'

​

Example response

{
  "id": "skill_019e3bba474b73cfaf19eae9b5f5e66d",
  "type": "skill",
  "display_title": "test-skill-api-doc",
  "description": "Updated skill description",
  "source": "custom",
  "latest_version": "1759178010641129",
  "metadata": {
    "team": "docs",
    "stage": "updated"
  },
  "created_at": "2026-05-18T15:35:24.248164Z",
  "updated_at": "2026-05-18T15:36:01.767469Z"
}

​

Response notes

• updated_at is refreshed to the operation time.
• Updating content creates a new version; latest_version points to it.
• Metadata-only updates do not create a new version.
• Fields not included in the request body retain their previous values.

​

Errors

​

Related