Lists the caller org's OWN skills with their SKILL.md bodies.
Lists the caller org's OWN skills with their SKILL.md bodies.
GET /v1/tools/skills/authored
| Address | https://api.hanzo.ai/v1/tools/skills/authored |
| Method | GET |
| Operation | get_tools_skills_authored |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Lists the caller org's OWN skills with their SKILL.md bodies. GET /v1/tools/skills is the registry view — the brand's catalogue plus this org's, with activation flags and no bodies; this is the EDITABLE set, so it carries the content that view omits and nothing the org did not write.
Request
GET /v1/tools/skills/authored takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | authoredSkillList | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
skills | body | Skill[] | — | Skills is every skill this org authored, each with its SKILL.md content. |
skills[].content | body | string | — | Content is the SKILL.md body, markdown. |
skills[].createdAt | body | integer | — | CreatedAt is when the skill was last written, Unix seconds. |
skills[].description | body | string | — | Description is the one-line summary discovery shows for the skill. |
skills[].id | body | string | — | ID is the skill's id within the org. |
skills[].name | body | string | — | Name is the skill's name: one lowercase path segment (a-z0-9, _ or -). |
skills[].org | body | string | — | Org 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.
import { Configuration, ToolsApi } from 'hanzoai';
const api = new ToolsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getToolsSkillsAuthored();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolsApi(client).get_tools_skills_authored()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.ToolsAPI.GetToolsSkillsAuthored(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, tools_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = tools_api::get_tools_skills_authored(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new ToolsApi(client).getToolsSkillsAuthored();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/tools/skills/authored \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches tools through the tools tool, which names its 19 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_mcp_servers"
}
}
}'How is this guide?