spb/skills-spboucher-ai

1---2title: Install in Claude Code3description: Where skills go, how to add local and remote MCP servers, and how to check what you installed.4order: 105section: Install6---78# Install in Claude Code910Paths 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.1112## Skills1314| Scope | Location |15|---|---|16| Personal (all projects) | `~/.claude/skills/<slug>/SKILL.md` |17| Project (shared with the repo) | `.claude/skills/<slug>/SKILL.md` |1819### With the Skills CLI2021```bash22skills inspect @<namespace>/<slug>                    # permissions, files, findings — read first23skills install @<namespace>/<slug> --client claude-code            # personal24skills install @<namespace>/<slug>@1.2.0 --client claude-code --project   # pinned, project scope25```2627The 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.2829### By hand3031```bash32V=1.2.0; S=<slug>; N=<namespace>33curl -fsSLo $S-$V.tar.gz https://skills.spboucher.ai/api/v1/artifacts/$N/$S/versions/$V/download34curl -fsS https://skills.spboucher.ai/api/v1/artifacts/$N/$S/versions/$V/checksum | shasum -a 256 -c -35tar -tzf $S-$V.tar.gz36mkdir -p ~/.claude/skills/$S && tar -xzf $S-$V.tar.gz -C ~/.claude/skills/$S37```3839Start a new Claude Code session; the skill is discovered from its `description`.4041### Roll back or remove4243```bash44rm -rf ~/.claude/skills/<slug>                                   # remove45cp -R ~/.skills-registry/backups/<slug>-<timestamp> ~/.claude/skills/<slug>   # restore the previous copy46```4748## MCP servers4950An MCP listing tells you how to connect; the registry does not run the server. See [Concepts](/docs/concepts).5152### Local server (stdio)5354The artifact page gives the exact command. The shape is:5556```bash57claude mcp add --transport stdio --env API_KEY=<value> <name> -- <command> [args...]58```5960Or commit a project-scoped entry in `.mcp.json`, keeping secrets in your environment:6162```json63{64  "mcpServers": {65    "<name>": { "command": "<command>", "args": ["…"], "env": { "API_KEY": "${API_KEY}" } }66  }67}68```6970The command runs on your machine with your privileges. Download the source archive (`skills download @<namespace>/<slug>`) and read it first.7172### Remote server (Streamable HTTP)7374```bash75claude mcp add --transport http <name> https://example.org/mcp76claude mcp add --transport http <name> https://example.org/mcp --header "Authorization: Bearer $THEIR_TOKEN"77```7879The endpoint is operated by the publisher. What you send goes to them.8081### Scopes8283`claude mcp add --scope local` (default) and `--scope user` write to `~/.claude.json`; `--scope project` writes `.mcp.json` in the project root.8485## The registry's own MCP server8687To let Claude Code search this registry directly:8889```bash90claude mcp add --transport http skills-registry https://skills.spboucher.ai/mcp91```9293See [MCP reference](/docs/mcp).9495## Secrets9697Environment variables an MCP server needs are set on your machine. They are never sent to the registry, and the registry never asks for them.98