Upload New Skill Version

Prerequisites

Endpoint and authentication configured. For details, see Overview and authentication. Before uploading a new version, upload the zip package via File to obtain a file_id.

Endpoint

POST /skills/{skill_id}/versions The request body contains only file_id. The version number is generated by the server; the new version also undergoes a security scan; agents mounted with older versions are not affected.

Request example

curl -X POST "$AGENTSTUDIO_URL/skills/skill_xxx/versions" \
  -H "Authorization: Bearer $DASHSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"file_id": "file_xxx"}'

Response example

{
  "id": "skillver_xxx",
  "skill_id": "skill_xxx",
  "type": "skill_version",
  "name": "pdf3.0",
  "description": "Description parsed from SKILL.md",
  "version": "1.1",
  "status": "checking",
  "created_at": "2026-06-15T08:23:11.456+00:00",
  "updated_at": "2026-06-15T08:23:11.456+00:00"
}

Response fields

Field	Type	Description
`id`	string	Version ID, format: `skillver_xxx`
`skill_id`	string	Parent skill ID
`type`	string	Always `skill_version`
`name` / `description`	string	Parsed from `SKILL.md` inside this version's zip
`version`	string	Version number, generated by the server
`status`	string	Scan status: `checking` / `active` / `rejected`. Only `active` can be mounted
`created_at` / `updated_at`	string	Creation / last update time, ISO 8601
`additional_properties`	object	Returned only when `status=rejected`; contains `error_info`: security review issues listed by file path within the zip

​Prerequisites

​Endpoint

​Request example

​Response example

​Response fields

Prerequisites

Endpoint

Request example

Response example

Response fields