Create skill

POST/v1/skills

Create a custom skill with markdown instructions, files, icon, and category.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
idstringNoOptional stable ID for mirroring an existing project-scoped Skill.
namestringYesHuman-readable name.
descriptionstringNoHuman-readable description.
markdownstringNo—
filesobject[]No—
files[].namestringNoHuman-readable name.
files[].contentstringNoRaw text content.
files[].languagestringNo—
iconstringNo—
categoryresearch | creative | productivity | development | customNo—
metadataobjectNoFree-form metadata object.
isActivebooleanNo—

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201Skill createdapplication/json
FieldTypeRequiredDescription
skillobjectNo—
skill.idstringNoUnique identifier.
skill.userIdstringNoUser ID.
skill.organizationIdstringNo—
skill.createdByUserIdstringNo—
skill.namestringNoHuman-readable name.
skill.descriptionstringNoHuman-readable description.
skill.markdownstringNo—
skill.filesobject[]No—
skill.files[].namestringNoHuman-readable name.
skill.files[].contentstringNoRaw text content.
skill.files[].languagestringNo—
skill.iconstringNo—
skill.categoryresearch | creative | productivity | development | customNo—
skill.metadataobjectNoFree-form metadata object.
skill.isActivebooleanNo—
skill.createdAtstringNoISO 8601 timestamp.
skill.updatedAtstringNoISO 8601 timestamp.
Create skill
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow