Distribution

One publish reaches assistants through MCP, the CLI, a Claude Code marketplace file, a well-known index and a public catalog.

By The SKaaS team. Last updated . Markdown version

You publish a skill once. SKaaS then serves it through several surfaces, so each assistant can use the one it supports.

Which surfaces does SKaaS offer?

Which surfaces does SKaaS offer?
Surface For What SKaaS serves
Remote MCP server Any MCP host Five read tools and the MCP skills extension.
CLI install Codex, Cursor, Copilot, Gemini CLI, OpenCode, Devin, Claude Code Files in your agent's skill directory, plus skaas.lock.
Claude Code marketplace Claude Code A marketplace file whose sources are pinned by hash.
Well-known index Clients of the discovery draft, such as npx skills A JSON index of public skills with name, description, address and digest. The format is a draft, so it sits behind a version switch.
Public catalog People The library on this site. See the public catalog.
OpenCode bridge OpenCode An index and the files of each skill, read through the organization's token.
Bundles Manual installs and organization uploads Zip and .skill exports with a target profile applied.
GitHub mirror People who want a copy in their own repository A push-only copy of releases, committed to a repository that you own. See the GitHub App.
Claude Skills API Assistants that load skills from that API A sync of a release to your own workspace, with your own key. See Sync to the Claude Skills API.

Can a release be signed?

Yes. An organization signs its releases with its own key, and the CLI checks the signature before it installs. A setting decides whether an unsigned release is refused, warned about or ignored, and skaas verify checks what is already installed. See Signed releases and the CLI overview.

What does the prompt hook add?

An optional hook suggests at most three skills at prompt time. It matches locally and is built to stay silent on a weak match. See the CLI overview.