Install in Claude Code

Paths and commands below follow the Claude Code documentation as checked on 2026-11-09. The artifact page shows the same instructions filled in for that artifact and version.

Skills

With the Skills CLI

skills inspect @<namespace>/<slug>                    # permissions, files, findings — read first
skills install @<namespace>/<slug> --client claude-code            # personal
skills install @<namespace>/<slug>@1.2.0 --client claude-code --project   # pinned, project scope

The CLI downloads the archive, verifies its SHA-256 against the release metadata, shows the destination and the declared permissions, asks for confirmation, and copies the files. It does not run any script from the package. If the destination already exists it stops unless you pass --force (or use skills update), and it keeps the previous copy under ~/.skills-registry/backups/. A .skills-registry.json file in the installed directory records the name, version and checksum.

By hand

V=1.2.0; S=<slug>; N=<namespace>
curl -fsSLo $S-$V.tar.gz https://skills.spboucher.ai/api/v1/artifacts/$N/$S/versions/$V/download
curl -fsS https://skills.spboucher.ai/api/v1/artifacts/$N/$S/versions/$V/checksum | shasum -a 256 -c -
tar -tzf $S-$V.tar.gz
mkdir -p ~/.claude/skills/$S && tar -xzf $S-$V.tar.gz -C ~/.claude/skills/$S

Start a new Claude Code session; the skill is discovered from its description.

Roll back or remove

rm -rf ~/.claude/skills/<slug>                                   # remove
cp -R ~/.skills-registry/backups/<slug>-<timestamp> ~/.claude/skills/<slug>   # restore the previous copy

MCP servers

An MCP listing tells you how to connect; the registry does not run the server. See Concepts.

Local server (stdio)

The artifact page gives the exact command. The shape is:

claude mcp add --transport stdio --env API_KEY=<value> <name> -- <command> [args...]

Or commit a project-scoped entry in .mcp.json, keeping secrets in your environment:

{
  "mcpServers": {
    "<name>": { "command": "<command>", "args": ["…"], "env": { "API_KEY": "${API_KEY}" } }
  }
}

The command runs on your machine with your privileges. Download the source archive (skills download @<namespace>/<slug>) and read it first.

Remote server (Streamable HTTP)

claude mcp add --transport http <name> https://example.org/mcp
claude mcp add --transport http <name> https://example.org/mcp --header "Authorization: Bearer $THEIR_TOKEN"

The endpoint is operated by the publisher. What you send goes to them.

Scopes

claude mcp add --scope local (default) and --scope user write to ~/.claude.json; --scope project writes .mcp.json in the project root.

The registry's own MCP server

To let Claude Code search this registry directly:

claude mcp add --transport http skills-registry https://skills.spboucher.ai/mcp

See MCP reference.

Secrets

Environment variables an MCP server needs are set on your machine. They are never sent to the registry, and the registry never asks for them.