skill-hub

Update an installed skill to its newest published version

Move one installed skill onto the newest published version of that same skill, carrying its settings forward. The install itself is untouched: same skill, same sharing scope, same owner, and a skill that was running stays running while a paused one stays paused. There is no version to pick — the newest published one is the only destination, and going back to an older one is not offered here. expected_version_id is an optional compare-and-set guard: send back the available_version_id the page showed, and a version published in the meantime returns 409 rather than applying a different update. A skill that is already up to date is a 409. A LIVE delivery skill whose settings would not carry onto the newer version is a 409 that says so, rather than an upgrade that silently stops it posting.

post/v1/skill-installations/{installation_id}/upgrade

Request

  • Base URL: https://api.patricia.app (the document declares no server; this is the origin it was published from)
  • URL: https://api.patricia.app/v1/skill-installations/{installation_id}/upgrade
  • Auth: HTTP bearer

Path parameters

installation_idstring uuid required

Headers

X-Tenant-Idstring nullable

Request body

expected_version_idstring uuid nullable

Response

Successful Response

idstring uuid required
skill_idstring uuid required
manifest_version_idstring uuid required
status_codestring required
config_versioninteger required
projection_generationinteger required
activated_atstring date-time nullable required
first_live_atstring date-time nullable required
killed_atstring date-time nullable required
kill_reasonstring nullable required
titlestring nullable
slugstring nullable
descriptionstring nullable
listing_state'unlisted' | 'testing' | 'listed'

Who can discover and install a global skill.

is_portableboolean nullable
archetype_codestring nullable
can_edit_definitionboolean nullable
removableboolean

Whether this installation may be removed from the workspace.

visibility_code'team' | 'personal' required

Who, within a tenant, an installed skill is visible to (skill_installation.visibility_code).

The skill-side counterpart of IntegrationVisibility: TEAM is any actor in the tenant, PERSONAL is only the actor who installed it (owner_actor_id). A TEAM install is safe to surface in the shared, per-tenant prompt cache; a PERSONAL install is surfaced only through the per-run, actor-scoped progressive-disclosure loader (never the shared prompt, which would leak it across actors).

is_mineboolean nullable
can_change_visibilityboolean
has_settingsboolean nullable
is_catalog_defaultboolean
effectively_enabledboolean
update_availableboolean
available_version_idstring uuid nullable
outdated_configboolean
outdated_config_reasonsstring[]

Changes

No recorded changes to this operation across all 1 revision of this API.