Skip to main content
POST
Update skill

Restrictions

Usage

  • Only description, description_en, and team_id are editable; the skill body is changed by re-uploading.
  • description only updates when non-empty — there is no way to clear it via this field; description_en is nilable, so send an empty string to explicitly clear it.
  • Reassigning team_id to a different team runs a second authorization check beyond edit access, verifying the caller may target the destination team.
  • Every call is recorded in the account audit log.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Editable skill metadata.

skill_id
string
required

Target skill ID.

description
string

New description. Cannot contain < or >. Sending an empty string leaves the current value unchanged — there is no way to clear it via this field.

Maximum string length: 1024
description_en
string | null

New English description. Cannot contain < or >. Omit to leave unchanged; send an empty string to explicitly clear it.

Maximum string length: 1024
team_id
integer<int64> | null

Reassign team scope: 0 = account-wide; >0 = team. Omit to leave unchanged.

Response

Success

Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
object

An AI SRE skill — a packaged SKILL.md bundle the agent can load.