Update a skill's draft
Write a skill’s SKILL.md content (name, description, markdown body and the optional frontmatter) to its draft. Only the fields you send change; an omitted field keeps its current value, and a list or text field you send replaces the old one whole. The write goes to the live draft, the same draft the Athena editor shows, under the asset’s existing id. Once the asset has been published, runs keep using the published version until you publish the draft with POST /api/v0/assets/{asset_id}/publish; one never published runs from its draft. Requires edit access to the asset; an archived asset is refused with 409. Unknown fields are refused with 422. The frontmatter is validated as it will read after the write; a skill that would not be spec-compliant is refused with 422 and nothing is written. A new name also becomes the asset title.
Authentication
Path parameters
Headers
Request
Space-separated list of pre-approved tools (experimental); an empty string clears it
Environment requirements (max 500 chars); an empty string clears it
What the skill does and when to use it (max 1024 chars)
License name or reference; an empty string clears it
Additional string metadata; replaces the whole map
Skill name slug (lowercase letters, numbers, single hyphens; max 64 chars). Also becomes the asset title.
Response
Type of the asset: skill or collab_agent
Always false: the write changed the draft only. Publish it with POST /api/v0/assets/{asset_id}/publish.
Non-fatal notes, such as tool or toolkit IDs the registry does not know