Learn when and where to publish instructions in the Server-hosted skills guide.

Skills API

Owner-qualified CRUD for canonical SKILL.md documents.

OpenAPI JSON

Routes

Use GET and POST on each collection, then GET, PUT, and DELETE on /{skill_slug}.

  • /api/v1/users/{username}/skills; self is accepted as the username.
  • /api/v1/teams/{team_slug}/skills
  • /api/v1/users/{username}/repos/{repo_slug}/skills
  • /api/v1/teams/{team_slug}/repos/{repo_slug}/skills

Request and response

Create and update requests use one JSON field containing the complete canonical document:

{"content":"---\nname: release-notes\ndescription: Prepare release notes\n---\n\nVerify links."}

Lists are paginated and omit content. Detail and mutation responses include content. Public UUIDs, hashes, slugs, descriptions, and timestamps are returned; internal database IDs are never returned.

Access

  • User and personal-repository skills are available to their owner.
  • Team members can read team and team-repository skills; team owners can create, update, and delete them.
  • Archived repository skills remain readable, while every mutation returns 403 Forbidden.
  • Duplicate names return 409 Conflict; invalid canonical documents return 400 Bad Request.