> ## Documentation Index
> Fetch the complete documentation index at: https://docs.intelligence-management-platform.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish a skill (agent-facing)

> Publishes a skill bundle from an agent. If the name does not exist, creates a new skill at v1 and requires `?visibility=public|private`. If the name exists and the caller has write access, appends a new version. Returns 403 when the name exists but the caller lacks write access; returns 409 when the name exists but the caller cannot even read it (existence is not revealed). The request body must be raw zip/`.skill` bytes.



## OpenAPI

````yaml /openapi/openapi.json post /skills/registry/{name}
openapi: 3.1.0
info:
  title: IMP REST API
  version: 1.0.0
  description: >-
    REST endpoints of the IMP backend. GraphQL covers entity CRUD; REST covers
    agent runs, media, files, and system utilities. All requests require
    authentication unless the agent is public.
servers:
  - url: '{baseUrl}'
    variables:
      baseUrl:
        default: http://localhost:9001
        description: >-
          Base URL of your IMP backend. Self-hosted deployments typically run on
          port 9001.
security:
  - apiKey: []
  - bearer: []
tags:
  - name: Agents
    description: Endpoints for running, compacting, and querying agent instances.
  - name: Sessions
    description: Endpoints for managing files attached to agent sessions.
  - name: Media
    description: Transcription, speech synthesis, and image generation.
  - name: System
    description: Platform health and configuration utilities.
  - name: Budgets
    description: >-
      LiteLLM tag-budget management for users, roles, teams, projects, agents,
      and routines. Access requires `super_admin` or a role with
      `budget_management` write scope.
  - name: Skills
    description: >-
      Skills are versioned bundles of files (markdown, scripts, assets) mounted
      into the agent sandbox. These endpoints manage the skill registry and
      individual skill files.
  - name: Uploads
    description: >-
      Uppy-compatible S3 companion routes for single-part and multipart file
      uploads. Accept the standard API key. The `internal-key` header (set to
      `INTERNAL_SECRET`) is accepted only on `/s3/delete`, `/s3/download`,
      `/s3/list`, and `/s3/object` — it does **not** work on `/s3/sign` or the
      `/s3/multipart` routes.
  - name: Compliance
    description: >-
      GDPR / DSGVO operator endpoints for data-subject access (export) and
      erasure. Both require `super_admin`.
  - name: Artifacts
    description: >-
      Shareable artifact links — create, list, and revoke share links for files
      stored in S3.
paths:
  /skills/registry/{name}:
    post:
      tags:
        - Skills
      summary: Publish a skill (agent-facing)
      description: >-
        Publishes a skill bundle from an agent. If the name does not exist,
        creates a new skill at v1 and requires `?visibility=public|private`. If
        the name exists and the caller has write access, appends a new version.
        Returns 403 when the name exists but the caller lacks write access;
        returns 409 when the name exists but the caller cannot even read it
        (existence is not revealed). The request body must be raw zip/`.skill`
        bytes.
      operationId: publishSkillByName
      parameters:
        - name: name
          in: path
          required: true
          description: Skill name (unique).
          schema:
            type: string
        - name: visibility
          in: query
          required: false
          description: >-
            Required for new skills. `public` or `private`. Ignored when
            updating an existing skill.
          schema:
            type: string
            enum:
              - public
              - private
      requestBody:
        required: true
        content:
          application/zip:
            schema:
              type: string
              format: binary
          application/octet-stream:
            schema:
              type: string
              format: binary
      responses:
        '200':
          description: Publish result.
          content:
            application/json:
              schema:
                type: object
                properties:
                  name:
                    type: string
                  version:
                    type: integer
                  created:
                    type: boolean
                    description: True when a new skill row was created.
        '400':
          description: Empty body, missing `visibility`, or bundle validation error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Not authenticated.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Skill exists but caller lacks write access.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: Name unavailable (exists but caller cannot read it).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      properties:
        detail:
          type: string
          description: Human-readable error message.
        message:
          type: string
          description: Human-readable error message (alternate key used on some endpoints).
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Organisation API key. Format: `sk_<secret>/<keyname>` — the secret
        portion, a literal slash, and the human-readable key name. The header
        `exulu-api-key` is accepted as an alias. A `Bearer ` prefix is tolerated
        and stripped. Keys with an agent scope are only valid for the scoped
        agent instance.
    bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        NextAuth session JWT (HS256, signed with `NEXTAUTH_SECRET`). This is the
        token the IMP frontend uses automatically.

````