spb/skills-spboucher-ai

1---2title: Other clients3description: Use any Agent Skills consumer or MCP client, and understand local versus remote MCP servers.4order: 135section: Install6---78# Other clients910Everything in the registry is reachable with `curl`, `shasum` and `tar`. No client-specific tooling is required.1112## Any Agent Skills consumer1314```bash15V=1.2.0; S=<slug>; N=<namespace>16BASE=https://skills.spboucher.ai/api/v1/artifacts/$N/$S/versions/$V1718curl -fsSLo $S-$V.tar.gz $BASE/download        # 1. download19curl -fsS $BASE/checksum | shasum -a 256 -c -  # 2. verify20tar -tzf $S-$V.tar.gz                          # 3. inspect21mkdir -p <skills-dir>/$S && tar -xzf $S-$V.tar.gz -C <skills-dir>/$S   # 4. extract22```2324`<skills-dir>` is wherever your agent looks for skills. Many tools read `~/.agents/skills` (user) and `.agents/skills` (project); the directory name must equal the skill's `name`, which is the artifact slug.2526With the CLI:2728```bash29skills install @<namespace>/<slug> --client generic-agent-skills          # ~/.agents/skills/<slug>30skills install @<namespace>/<slug> --client generic-agent-skills --dir ./vendor/skills/<slug>31```3233Release archives are plain gzip-compressed tar files containing only regular files with relative paths. The registry rejects archives with links, absolute paths or `..` segments before they are published.3435## Any MCP client3637Ask for the facts and wire them into your client's own configuration:3839```bash40curl -s "https://skills.spboucher.ai/api/v1/artifacts/<namespace>/<slug>/versions/latest/install?client=generic-mcp" | jq .41```4243The response gives the transport, the command and arguments or the URL, the environment variables the server expects, and any warnings.4445### Local server or remote endpoint?4647| | Local (stdio) | Remote (Streamable HTTP) |48|---|---|---|49| Who runs it | You, on your machine | The publisher, on their infrastructure |50| What you configure | A command and arguments | A URL, sometimes a header |51| Where your data goes | Stays local unless the server itself calls out | To the operator of the endpoint |52| What to check first | The source code you are about to run | Who operates it, and their terms |53| Secrets | Environment variables on your machine | A token issued by that operator |5455In both cases the registry is only the directory. It never receives your secrets and does not sit between you and the server.5657### Three separate decisions58591. **Download** — fetching and verifying an archive changes nothing on your system.602. **Configure** — adding an entry to a client makes the server available to it.613. **Execute** — the server actually runs when your client starts it or connects.6263The registry and its CLI stop after the first two and never run a package's installer or scripts on your behalf.6465## Pinning and updating6667Always install a specific version in shared or reproducible setups (`@namespace/slug@1.2.0`). To update, read the release notes and the file changes of the new version, then install it; the CLI keeps the previous copy so you can roll back. See [Versioning and safe updates](/docs/versioning).68