Hanzo
OpenapiTools

Adds or revises one of the caller org's own skills, and answers 201 with the…

Adds or revises one of the caller org's own skills, and answers 201 with the stored record.

POST /v1/tools/skills

Addresshttps://api.hanzo.ai/v1/tools/skills
MethodPOST
Operationpost_tools_skills
AuthAuthorization: Bearer $HANZO_API_KEY

Adds or revises one of the caller org's own skills, and answers 201 with the stored record. The id is derived from the name, so writing the same name again REVISES that skill rather than accumulating near-duplicates that would then collide in the registry. An org's skills are private to it by construction — they live in a different store from the brand's embedded catalogue and have no path into the public gallery — and a brand skill always wins a name collision against an org's.

Request

3 fields, body application/json (required).

FieldInTypeRequiredDescription
contentbodystringContent is the SKILL.md body.
descriptionbodystringDescription is the one-line summary discovery shows for the skill.
namebodystringName is the skill's id within the org: one lowercase path segment (a-z0-9, _ or -).

Response

StatusBodyMeaning
201skillWrittencreated

201 body — 7 fields.

FieldInTypeAlwaysDescription
skillbodySkill
skill.contentbodystringContent is the SKILL.md body, markdown.
skill.createdAtbodyintegerCreatedAt is when the skill was last written, Unix seconds.
skill.descriptionbodystringDescription is the one-line summary discovery shows for the skill.
skill.idbodystringID is the skill's id within the org.
skill.namebodystringName is the skill's name: one lowercase path segment (a-z0-9, _ or -).
skill.orgbodystringOrg is the org that authored the skill — the validated caller's, never a value the body supplied.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Tools API · All Hanzo APIs · Interactive reference

How is this guide?

On this page