authored-skills

Enable an authored skill in this workspace

Enable the tenant skill's active (approved) version. An INSTRUCTION skill is enabled immediately (its guidance reaches Patricia through the prompt, so there is nothing to schedule); the response lists any recommended integrations the workspace hasn't connected yet, to nudge the teammate. A SANS (scheduled) skill is born PAUSED + a default config, exactly like a catalog skill: the admin completes settings + runs activation review before delivery.

The optional body chooses how widely to enable it. Omit it (or send team) for the whole workspace, exactly as before, when the caller holds skills:install. Without skills:install, an absent body enables it for yourself alone instead; an EXPLICIT team is refused (403) rather than silently narrowed. Send personal to enable it for yourself alone: only your conversations carry the skill's guidance. Personal needs an INSTRUCTION skill (400 otherwise) and a caller whose membership links to a chat profile (400 otherwise, so an API key can never own one). Either way the workspace holds ONE install of a skill, so a second Enable is a 409.

post/v1/authored-skills/{skill_id}/install

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/authored-skills/{skill_id}/install
  • Auth: HTTP bearer

Path parameters

skill_idstring uuid required

Headers

X-Tenant-Idstring nullable

Request body

visibility'team' | 'personal'

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).

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[]
recommended_to_connectstring[]

Changes

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