List authored — GET /v1/tool/skills/authored

Lists the caller org's OWN skills with their SKILL.md bodies.

GET /v1/tool/skills/authored

Tool → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/tool/skills/authored`
Method	`GET`
Operation	`get_tool_skills_authored`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the caller org's OWN skills with their SKILL.md bodies. GET /v1/tool/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/tool/skills/authored takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	tool.authoredSkillList	ok
`default`	problem-details	refused

200 body — 9 fields.

Field	In	Type	Always	Description
`skills`	body	tool.Skill[]	—	Skills is every skill this org authored, each with its SKILL.md content.
`skills[].admitted`	body	boolean	—	Admitted is whether an admin of the org, or a SuperAdmin, wrote this content.
`skills[].content`	body	string	—	Content is the SKILL.md body, markdown.
`skills[].createdAt`	body	integer (int64)	—	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.
`skills[].source`	body	string	—	Source is the repository the skill was read from, "<project>/<name>" or "<name>"; empty for a skill written through the API.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo tool skills authored

.ts

.py

.go

.rs

.java

import { Configuration, ToolApi } from 'hanzoai';

const api = new ToolApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getToolSkillsAuthored();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ToolApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ToolApi(client).get_tool_skills_authored()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ToolAPI.GetToolSkillsAuthored(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, tool_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = tool_api::get_tool_skills_authored(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ToolApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ToolApi(client).getToolSkillsAuthored();

curl https://api.hanzo.ai/v1/tool/skills/authored \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches tool through the tool tool, which names its 17 operations with its own verbs — this one among them, under a name only MCP 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_tools"
         }
       }
     }'

Tool API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList plugins NextList skills