post_v1_skills
PutSkill adds or revises one of the caller org's own skills, and answers 201 with the stored record.
PutSkill 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.
| Tool | post_v1_skills |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | POST /v1/skills |
| Product | skills |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
content | string | — | — | — | Content is the SKILL.md body. Required, at most 256 KiB. |
description | string | — | — | — | Description is the one-line summary discovery shows for the skill. |
name | string | — | — | — | Name is the skill's id within the org: one lowercase path segment (a-z0-9, _ or -). Writing an existing name REVISES that skill. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_skills",
"arguments": {
"content": "<content>",
"description": "<description>",
"name": "<name>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_skills | POST /v1/skills | skills | Adds or revises one of the caller org's own skills, and answers 201 with the stored… |
The same capability over plain HTTP is in the skills API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?