Create Skill Version changedapi/skills/versions/create
Nearest release: v2.1.238, published under an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+81added
Lines−0removed
From line
—
no hunk to open at
First seen
20 Aug 2026
this site's first read of the page
Recorded edits8to this page, all time
## Create Skill Version ### Path Parameters ### Returns ### Example #### Response
The whole hunk
81 lines, new page
/
lines
A whole new page. There's nothing to diff it against, so here is what it says.
---
title: Create Skill Version
url: https://platform.claude.com/docs/en/api/skills/versions/create
---
## Create Skill Version
**post** `/v1/skills/{skill_id}/versions`
Create Skill Version
### Path Parameters
- `skill_id: string`
Unique identifier for the skill.
The format and length of IDs may change over time.
### Returns
- `SkillVersion object { id, created_at, description, 3 more }`
- `id: string`
Unique identifier for this Skill Version. The id addresses the version in
paths and pins it in references.
- `created_at: string`
ISO 8601 timestamp of when the skill was created.
- `description: string`
Description of the skill version.
This is extracted from the SKILL.md file in the skill upload.
- `name: string`
The Skill's immutable kebab-case slug, set at creation from the first
upload's SKILL.md frontmatter `name` (or its enclosing directory). Every
later upload must resolve to the same value. Also the top-level directory
of the Skill's mounted files and the base name of a downloaded archive.
- `skill_id: string`
Unique identifier for the skill.
The format and length of IDs may change over time.
- `type: "skill_version"`
Object type.
For Skill Versions, this is always `"skill_version"`.
- `"skill_version"`
### Example
```http
curl https://api.anthropic.com/v1/skills/$SKILL_ID/versions \
-H 'Content-Type: multipart/form-data' \
-H 'anthropic-version: 2023-06-01' \
-H "X-Api-Key: $ANTHROPIC_API_KEY" \
-F files='["Example data"]'
```
#### Response
```json
{
"id": "id",
"created_at": "2024-10-30T23:58:27.427722Z",
"description": "description",
"name": "name",
"skill_id": "skill_01JAbcdefghijklmnopqrstuvw",
"type": "skill_version"
}
```
No line in this hunk matches that.