Replace skill bundle
Replaces a Skill’s bundle with a newly uploaded one and returns the updated Skill.
Upload the new bundle with Upload file first. file_id is the only field you can change: to change the description or surfaces, edit SKILL.md and upload a new bundle. The replacement must name the same Skill.
Replacing a bundle with identical contents changes nothing and returns the current Skill, so a retry is safe. version.num is checked before the bundle is replaced, but two replacements sent at the same moment with the same num can both succeed, and the later one is stored.
Authentication
JWT bearer token authentication. Include the Configuration API key in the Authorization header as ‘Bearer <token>’.
Path parameters
The id of the Skill, as returned when it was registered or listed.
Request
Files API id of the uploaded .zip or .skill bundle (purpose CONFIGURATIONS_ASSISTANT_SKILL). Required on create; on update it replaces the bundle. Write-only: the staged upload is consumed on registration and expires, so reads never return a file_id.
Response
Files API id of the uploaded .zip or .skill bundle (purpose CONFIGURATIONS_ASSISTANT_SKILL). Required on create; on update it replaces the bundle. Write-only: the staged upload is consumed on registration and expires, so reads never return a file_id.
Surfaces the skill is available on, from the bundle’s SKILL.md (e.g. slack, movewebchat:assistant). Empty means every surface.