skill-hub

Install a skill-platform skill into the tenant

Install a git-catalog skill by its catalog slug (e.g. celebrations), pinned to the skill's active manifest version with a default config seeded from the manifest's config_fields. A portable skill (which already runs by default from the trusted catalog) comes up ACTIVE — the install is how a workspace customizes or later turns it off, never a prerequisite. A delivery (sans) skill is born PAUSED: the admin completes required settings + runs activation review before any delivery. Idempotent per skill: a second install of the same skill is a 409.

Every install here reaches the whole workspace (there is no personal catalog install), so this route additionally requires skills:install, not just skills:create.

post/v1/skill-installations

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
  • Auth: HTTP bearer

Headers

X-Tenant-Idstring nullable

Request body

slugstring required

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.