> ## Documentation Index > Fetch the complete documentation index at: https://docs.prisme.ai/llms.txt > Use this file to discover all available pages before exploring further. # Update a skill ## OpenAPI ````yaml /api-reference/storage/swagger.yml patch /v1/skills/{skillId} openapi: 3.0.3 info: version: 1.0.0 title: Knowledges API description: > Public REST API for the Prisme.ai Knowledges (storage) workspace: knowledge bases, documents (uploaded files, web pages, remote files, connector documents), recurring web-crawl sources, semantic search, access control, per-knowledge-base API keys, and skills. Resource identifiers use the physical prefixes emitted by the implementation (`vs_` knowledge base, `vsf_` document, `seed_` web source, `kb-` API-key slug). This spec documents the public REST surface only. Internal helpers (private automations prefixed with `_`) and admin/GDPR lifecycle operations are not part of the public contract. contact: name: Prisme.ai url: https://prisme.ai servers: - url: https://{host}/v2/workspaces/slug:storage/webhooks description: Prisme.ai workspace webhooks variables: host: default: api.studio.prisme.ai description: API host (override for self-hosted or sandbox) security: - BearerAuth: [] - WorkspaceApiKeyAuth: [] tags: - name: Knowledge Bases description: >- Create, list, read, update, and delete knowledge bases (vector-backed document stores). - name: Documents description: >- Ingest and manage documents (uploaded files, web pages, remote files, connector documents) and their indexing. - name: Web Sources description: >- Recurring web crawl seeds that discover and index pages into a knowledge base. - name: Search description: Semantic search over a knowledge base. - name: Access description: Per-knowledge-base access bindings (user, group, org, agent principals). - name: API Keys description: Per-knowledge-base API keys for connector authentication. - name: Stats description: Aggregate dashboard statistics. - name: Skills description: Prompt/instruction registry entries. paths: /v1/skills/{skillId}: parameters: - name: skillId in: path required: true schema: type: string maxLength: 128 patch: tags: - Skills summary: Update a skill operationId: updateSkill requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SkillInput' responses: '200': description: Updated skill. content: application/json: schema: $ref: '#/components/schemas/Skill' '400': $ref: '#/components/responses/LegacyError400' '401': $ref: '#/components/responses/LegacyError401' '403': $ref: '#/components/responses/LegacyError403' '404': $ref: '#/components/responses/LegacyError404' security: - BearerAuth: [] components: schemas: SkillInput: type: object additionalProperties: true description: Writable fields for creating or updating a skill. properties: name: type: string display_name: type: string description: type: string instructions: type: string tools: type: array items: type: object additionalProperties: true Skill: type: object description: > Registry entry (prompt/instructions). Intentionally permissive. Note the implementation does NOT emit an `object` discriminator, and the field is `instructions` (plural). additionalProperties: true required: - id properties: id: type: string name: type: string display_name: type: string description: type: string instructions: type: string tools: type: array items: type: object additionalProperties: true user_id: type: string orgSlug: type: string nullable: true responses: LegacyError400: description: Caller validation failure (legacy flat envelope). content: application/json: schema: type: object description: | Legacy **flat** error envelope emitted by the not-yet-migrated `/v1/skills*`, `/v1/stats`, `/v1/cleanup/*` and `/v1/export/by-user` routes (all other routes use the nested `Error` envelope). The shape varies by route: `skills`/`stats` return `{ error: , code: }`; `cleanup`/`export` return `{ error: , message: }`. Same information, different field placement. These routes will migrate to the nested `Error` envelope. additionalProperties: true properties: error: type: string code: type: string message: type: string LegacyError401: description: Authentication missing or invalid (legacy flat envelope). content: application/json: schema: type: object description: | Legacy **flat** error envelope emitted by the not-yet-migrated `/v1/skills*`, `/v1/stats`, `/v1/cleanup/*` and `/v1/export/by-user` routes (all other routes use the nested `Error` envelope). The shape varies by route: `skills`/`stats` return `{ error: , code: }`; `cleanup`/`export` return `{ error: , message: }`. Same information, different field placement. These routes will migrate to the nested `Error` envelope. additionalProperties: true properties: error: type: string code: type: string message: type: string LegacyError403: description: Authorization denied (legacy flat envelope). content: application/json: schema: type: object description: | Legacy **flat** error envelope emitted by the not-yet-migrated `/v1/skills*`, `/v1/stats`, `/v1/cleanup/*` and `/v1/export/by-user` routes (all other routes use the nested `Error` envelope). The shape varies by route: `skills`/`stats` return `{ error: , code: }`; `cleanup`/`export` return `{ error: , message: }`. Same information, different field placement. These routes will migrate to the nested `Error` envelope. additionalProperties: true properties: error: type: string code: type: string message: type: string LegacyError404: description: Resource not found (legacy flat envelope). content: application/json: schema: type: object description: | Legacy **flat** error envelope emitted by the not-yet-migrated `/v1/skills*`, `/v1/stats`, `/v1/cleanup/*` and `/v1/export/by-user` routes (all other routes use the nested `Error` envelope). The shape varies by route: `skills`/`stats` return `{ error: , code: }`; `cleanup`/`export` return `{ error: , message: }`. Same information, different field placement. These routes will migrate to the nested `Error` envelope. additionalProperties: true properties: error: type: string code: type: string message: type: string securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- User session JWT or instance API key (`iak_*`). Send as `Authorization: Bearer `. WorkspaceApiKeyAuth: type: apiKey in: header name: x-prismeai-api-key description: Workspace- or knowledge-base-scoped API key. ````