What is a Skill?
A Skill packages your team’s method for a repeatable deliverable — call prep, discovery scripts, battlecards, one-pagers, QBR decks — as instructions an AI assistant can load and follow. Skills use the Anthropic Agent Skills format: a rootSKILL.md with the instructions, plus optional bundled reference files the instructions point to.
The difference from a prompt in a doc somewhere: Skills live in Octave, so every assistant connected to your workspace — Claude, Cursor, or anything else speaking MCP — discovers the same skills, follows the same current version, and your team’s method improves in one place.
Progressive disclosure
Skills load in three levels, so assistants read only what the task needs:- Discovery —
find_skillmatches a task description against skill names and descriptions;list_skillsbrowses the catalog. Neither loads any instructions. - Instructions —
get_skillloads theSKILL.mdbody plus a listing of bundled files. - Reference files —
get_skill_filereads one bundled file, only when the instructions call for it.
Skill lifecycle
Skills have adraft → published lifecycle and can be deactivated. Draft and deactivated skills stay invisible to assistants — find_skill and the listing surface only published, active skills — so you can iterate on a method without agents following a half-finished version.
Each skill’s folder is stored as a managed Asset (type skill). The Skill API keeps the searchable registry and the stored files in sync, which is why skill files are edited through the Skill API rather than the generic asset surface.
Managing Skills via API
GET /api/v2/skill/list— list skills, with status and text filtersGET /api/v2/skill/get— load a skill by oId or exact name, including itsSKILL.mdbody and file listingGET /api/v2/skill/file— read one bundled filePOST /api/v2/skill/find— find the best-matching skill for a task descriptionPOST /api/v2/skill/create/POST /api/v2/skill/update/POST /api/v2/skill/delete— manage skills