Add the SKaaS remote MCP servers to an assistant. The read server has five tools and pins every load to a release hash. The authoring server saves drafts and cannot publish.
The skaas command line tool in one page. Every command by use, the exit codes, where installs go, how to roll back, signature checks and the verify command, and the prompt hook.
Hybrid search combines exact, keyword and semantic matching, and each result says why it matched. How it stays silent, how it was tuned, and what the retrieval evaluation shows and does not show.
How SKaaS releases are made, hashed and compared, how an assistant pins one, and how to roll back or withdraw a release.
One publish reaches assistants through MCP, the CLI, a Claude Code marketplace file, a well-known index and a public catalog.
Write the tasks a skill should answer and the ones it should ignore, run them on every publish, and block a publish that breaks one.
Track an upstream source, review each proposed update with its file diff and audit change, then apply or dismiss it.
Let a GitHub Actions workflow publish skills with a key that lives for minutes. Write a trust policy, exchange the workflow's OIDC token for a one-repository key, and publish with it.
Install the SKaaS GitHub App to publish skills from a repository on push, audit pull requests as a check, and keep a push-only mirror of your releases in a repository that you own.
Send releases of a repository to your own Claude Skills API workspace with your own key. Set a sync target, start a sync, and read the five outcomes, including what the destination refuses.
How an organization becomes a publisher, why a public skill is listed only after a moderator approves it, how anyone can report one, and what a takedown does to the skill.
See what people search for, what finds nothing and which results get loaded, and who read which release. Learn what is logged, for how long and what stays out of the log.
Explore how skills relate to each other. See the neighbors of a skill, paths between two, what depends on one, dependency cycles, orphans and clusters of skills that compete for the same task.
Import public HTTPS skill sources into draft channels, inspect pinned guide and resource files, then explicitly promote or discard the reviewed draft.