# Quickstart

> Install the SKaaS CLI, publish a skill as an immutable release, connect an assistant, and install a skill with a lockfile entry.

Source: https://skaas.io/docs/quickstart
Last updated: 2026-11-17

SKaaS is in pre-alpha. With access to a source checkout, you can run the Community edition locally and publish a release that an assistant can load. Hosted signup and the public CLI package are pending.

## Install

Get a checkout from your deployment operator. From the repository root, use Node 22.18 or later and pnpm 10:

```sh
pnpm install --frozen-lockfile
pnpm --filter skaas run build
skaas_checkout="$PWD"
skaas() { node "$skaas_checkout/cli/dist/skaas.mjs" "$@"; }
skaas --version
```

You can use `skaas` in this shell from any directory.

## Start your stack and sign in

In the [Self-hosting guide](/docs/self-hosting), follow **How do I start the application?** to start the default Compose stack. Open `http://localhost:8081/signup`, follow the sign-in link from the server log, and create an organization called Acme. In **Repositories**, create a private repository called Platform. The examples use the address `acme/platform`.

Point the CLI at the local API before signing in. The device flow prints a code and the address of the browser approval page.

```sh
skaas config set endpoint http://localhost:8080
skaas login
skaas whoami
```

On a machine without a keychain, set `skaas config set credential-store file` before signing in. You can also create a scoped token under **Settings → Tokens and MCP setup** and set `SKAAS_TOKEN` in the current shell.

## Publish a skill

In a working directory of your choice, create a skill and edit its `SKILL.md` to describe a real task and how to do it. Audit it before publishing.

```sh
skaas init release-notes
# Edit release-notes/SKILL.md before you continue.
skaas audit ./release-notes
skaas publish ./release-notes --repo acme/platform
```

The output names the skill and its immutable release. If your repository blocks publishing on High findings, a High or Critical finding stops the publish and the report explains what to fix.

## Connect an assistant

Assistants reach your skills over MCP. The CLI writes the configuration for Claude Code, Codex, Cursor, VS Code, Gemini CLI and OpenCode.

```sh
skaas connect claude-code --org acme
```

The default Compose stack serves the Acme read endpoint at `http://localhost:8080/mcp/v1/acme`. See [Connect an agent over MCP](/docs/mcp) for repository scope and authentication.

## Install and update locally

From a consumer project, install the skill you published. SKaaS records the exact release in `skaas.lock`.

```sh
skaas add acme/platform/release-notes
skaas verify
```

For the private example, keep the CLI signed in. A current approved public release can be installed anonymously by publisher address. Anonymous installs cannot verify signatures, so a signature policy of `require` needs credentials.

`skaas add` checks the signature of the release before it writes a file, when the organization signs its releases, and `skaas verify` checks everything that is installed again. See [the CLI overview](/docs/cli) for the setting that makes an unsigned release an error. `skaas update` shows the difference and the audit change before it applies anything. To go back, run `skaas rollback`. If something is wrong, run `skaas doctor`. It checks sign-in, cache freshness, the signature setting and whether the endpoints answer.

## Publish from CI

Once you publish by hand, move it to your pipeline without a stored secret. See [Publish from CI without a stored secret](/docs/ci-publishing).
