Skip to main content
A skill is a folder of instructions, scripts and reference files that teaches an agent a task. An internal skill belongs to an organization: every member’s agent can find it with search_skills, sees it listed in its context, and loads it with get_skill. Nobody outside the organization can see it. Internal skills need a shared organization; in a personal organization, use private. Names are unique where the skill lives: a public name across Danube, an internal name within its organization, a private name among your own skills.

Upload a skill folder

A skill folder follows the Agent Skills layout, the same one Claude Code reads from .claude/skills/:
SKILL.md
Upload it from Dashboard > Skills, from the CLI, or through the API:
POST /v1/organizations/{org_id}/skills/upload does the same with the organization in the path. Without org_id, an internal skill goes to the organization the request acts for (the danube-org-id header or an organization API key). Limits: a 5 MB archive that unpacks to at most 10 MB and 200 files; text files up to 500 KB, binary files up to 2 MB. Files in other folders (for example FORMS.md or templates/) keep their path, so links from SKILL.md still work. A skill that contains a credential is refused.

Publish a new version

Uploading a skill whose name already exists answers 409. Upload with replace to publish a new version in place: the skill keeps its id, and version goes up by one. Replacing needs the right to edit that skill (below).

Share a skill with your organization

A private skill you wrote can move into an organization when it is ready for the team. Open it in Dashboard > Skills and click Share with <organization> (pick the organization when you belong to several). The skill moves: it keeps its id, its link and its versions, becomes internal, and every member’s agent can find and load it. You keep editing it, and the organization’s owners and admins can manage it too. Make private on a shared skill moves it back to your own skills; members and their agents lose access at once. Only the author shares a skill or makes it private. Sharing is refused with 409 when the organization already has a skill with that name (rename yours first), and making a skill private is refused with 409 when you already have a private skill with that name. Sharing needs the right to publish in that organization (below).

Use a skill

In an agent session, search_skills covers public skills, your organizations’ internal skills and your own private ones, with the last two first. get_skill returns SKILL.md and the text of every file, plus a download_url. To install a skill for Claude Code, download it as a zip ready for .claude/skills/:
The API is GET /v1/skills/{id}/download with your API key; it accepts the skill’s id or name.

Who can publish

Owners and admins of the organization can always publish, edit and delete its internal skills. Plain members can publish and share too, unless an owner or admin turns off Members can share skills and workflows in Dashboard > Organization > Settings (the skills_member_publish setting of PATCH /v1/organizations/{org_id}/settings, on by default). The same setting governs sharing workflows. A member can edit and delete the internal skills they published. Viewers never publish.

API