GET
/
v1
/
skills
/
{skill_id}
/
versions
/
{version}
cURL
curl "https://api.anthropic.com/v1/skills/skill_01AbCdEfGhIjKlMnOpQrStUv/versions/1759178010641129" \
     -H "x-api-key: $ANTHROPIC_API_KEY" \
     -H "anthropic-version: 2023-06-01" \
     -H "anthropic-beta: skills-2025-10-02"
{
  "created_at": "2024-10-30T23:58:27.427722Z",
  "description": "A custom skill for doing something useful",
  "directory": "my-skill",
  "id": "skillver_01JAbcdefghijklmnopqrstuvw",
  "name": "my-skill",
  "skill_id": "skill_01JAbcdefghijklmnopqrstuvw",
  "type": "skill_version",
  "version": "1759178010641129"
}

Headers

anthropic-beta
string[]

Optional header to specify the beta version(s) you want to use.

To use multiple betas, use a comma separated list like beta1,beta2 or specify the header multiple times for each beta.

anthropic-version
string
required

The version of the Claude API you want to use.

Read more about versioning and our version history here.

x-api-key
string
required

Your unique API key for authentication.

This key is required in the header of all API requests, to authenticate your account and access Anthropic's services. Get your API key through the Console. Each key is scoped to a Workspace.

Path Parameters

skill_id
string
required

Unique identifier for the skill.

The format and length of IDs may change over time.

version
string
required

Version identifier for the skill.

Each version is identified by a Unix epoch timestamp (e.g., "1759178010641129").

Response

Successful Response

created_at
string
required

ISO 8601 timestamp of when the skill version was created.

Examples:

"2024-10-30T23:58:27.427722Z"

description
string
required

Description of the skill version.

This is extracted from the SKILL.md file in the skill upload.

Examples:

"A custom skill for doing something useful"

directory
string
required

Directory name of the skill version.

This is the top-level directory name that was extracted from the uploaded files.

Examples:

"my-skill"

id
string
required

Unique identifier for the skill version.

The format and length of IDs may change over time.

Examples:

"skillver_01JAbcdefghijklmnopqrstuvw"

name
string
required

Human-readable name of the skill version.

This is extracted from the SKILL.md file in the skill upload.

Examples:

"my-skill"

skill_id
string
required

Identifier for the skill that this version belongs to.

Examples:

"skill_01JAbcdefghijklmnopqrstuvw"

type
string
default:skill_version
required

Object type.

For Skill Versions, this is always "skill_version".

version
string
required

Version identifier for the skill.

Each version is identified by a Unix epoch timestamp (e.g., "1759178010641129").

Examples:

"1759178010641129"