Apply Skill Version

Server URLloading...

POST

/skills/{skill_id}/apply-version

Send

Path

Commit a proposed new version (the evolve half of the human-approval gate).

ProposeSkillVersion only records metadata.pending_version (body + rationale); the live bundle is never touched until a human reviews and calls this. Applying swaps the SKILL.md body, preserves the existing assets, bumps the version, and clears the proposal. Stage is unchanged: applying to an active skill republishes it live (the call itself is the approval); a draft/stale skill still needs a separate activate.

Reject-on-drift: if the live bundle changed since the proposal was made (base_content_hash no longer matches), the proposal is stale — 409, so the agent re-proposes against the current body rather than silently clobbering an intervening recompile. Filesystem and graph are not transactional, so a failed graph write restores the prior bundle.

Path Parameters

Response Body

curl -X POST "https://example.com/skills/string/apply-version"

{}

{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}