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

# Save a skill

> Save a skill.


## OpenAPI

```yaml openapi.json post /v1/skills/learn
openapi: 3.1.0
info:
  title: Ocean One API
  version: 2.3.1
servers:
  - url: https://api.plungeai.com
paths:
  /v1/skills/learn:
    post:
      operationId: post-v1-skills-learn
      tags:
        - Skills
      summary: Save a skill
      description: "Saves a skill you wrote as a private card others cannot read, inject or delete — the card `skill_manage create` writes. Saving an existing name of your own replaces it; a name held by a platform skill or another user is 409. Inject it into a mission with `skills: [<name>]`. To have an agent distil a skill from a URL or text instead, use the `plungeai_learn` MCP tool."
      security:
        - ozkBearer: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - name
                - body
              properties:
                name:
                  type: string
                  pattern: ^[a-z0-9][a-z0-9-]{1,63}$
                  description: Kebab-case id, 2 to 64 characters
                body:
                  type: string
                  minLength: 1
                  maxLength: 65536
                  description: The skill, in markdown
                description:
                  type: string
                  maxLength: 60
                  description: One line; defaults to the body’s first line
                format:
                  type: string
                  enum:
                    - json
                    - yaml
                    - markdown
                    - text
                  description: "Response format override (precedence: this field → Accept header → mirror of the request Content-Type). Default json. yaml = the envelope with Markdown as block scalars; markdown = the same result the MCP plane renders; text = the bare result content. An unknown value → 400 invalid_format."
      responses:
        "201":
          description: Saved. Response format negotiates via the `format` field, an Accept header (application/json, text/yaml, text/markdown, text/plain), or the request Content-Type mirror; default JSON.
          content:
            application/json:
              schema:
                type: object
                properties:
                  skill:
                    $ref: "#/components/schemas/Skill"
            text/yaml:
              schema:
                type: string
            text/markdown:
              schema:
                type: string
            text/plain:
              schema:
                type: string
        "400":
          description: invalid_json — body is not valid JSON
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "401":
          description: unauthorized — missing, invalid or revoked ozk_ key
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "404":
          description: "not_found — no route for this method on this path: every other method answers it"
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "409":
          description: skill_name_taken — the name belongs to a platform skill or another user
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "422":
          description: invalid_params — name, body or description is missing or out of bounds
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
        "502":
          description: upstream_error — the skill store refused the write; nothing was saved, retry
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Error"
components:
  schemas:
    Error:
      type: object
      description: Standard error envelope. Every error response also carries an `X-Error-Code` response header equal to error.code, so a client branches on the header regardless of the negotiated body format (json | yaml | markdown | text). When the request created an execution, the `X-Execution-Id` response header is also set. Errors follow the negotiated format like success bodies.
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            message:
              type: string
            connect:
              type: object
              description: "On a 424 connection_required / credential_required: where the missing connection is made."
              properties:
                provider:
                  type: string
                method:
                  type: string
                  enum:
                    - oauth
                    - api_key
                    - wallet
                link:
                  type: string
                  example: POST /v1/connections/stripe/link
          required:
            - code
            - message
          additionalProperties: true
      required:
        - error
    Skill:
      type: object
      description: "A learned skill: a private card that agents inject with `skills: [<id>]`."
      properties:
        id:
          type: string
        description:
          type: string
      required:
        - id
        - description
  securitySchemes:
    ozkBearer:
      type: http
      scheme: bearer
      description: "ozk_ platform API key (Authorization: Bearer ozk_…)"
```