Appearance
Skills
Instructions an assistant loads on demand.
11 tools — 6 read, 5 write.
| Tool | What it does | |
|---|---|---|
add_skill_file | write | Attach a small file (script, reference, asset) to a skill's portable bundle inline. |
create_skill | write | Create a new skill (reusable instruction recipe) in this organization. |
delete_skill | write | Delete a skill by name. |
get_skill | read | Get a single skill's full record (id, body, parameters, allowed_tools, timestamps). |
get_skill_bundle_url | read | Get a short-lived signed URL to download the skill's portable bundle (SKILL.md + attached files) as a zip. |
list_skill_files | read | List the files attached to a skill's bundle (relative path, MIME type, size). |
list_skills | read | List all skills (reusable instruction recipes) available in this organization. |
list_skills_admin | read | List all skills with administrative metadata (ids, timestamps). |
load_skill | read | Load a skill's full instruction body and parameter schema. |
remove_skill_file | write | Remove a file from a skill's bundle by relative path. |
update_skill | write | Update an existing skill. |
Calling these
Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.
See How the API works for auth, errors and the shared envelope.