Skip to content
SKILLS
Documentation menu

Start

Getting started

Find, inspect, verify and install an artifact in a few minutes, without an account.

Skills is an open registry of reusable capabilities for AI agents: Agent Skills, MCP server listings, agent definitions, prompt packs, workflows and more. Reading, searching and downloading need no account.

1. Find something

Use the search box (press /), browse by type on Explore, or call the API:

curl -s "https://skills.spboucher.ai/api/v1/search?q=literature+review" | jq '.items[] | {name, type, summary, latestVersion}'

2. Inspect it before you trust it

Every artifact page shows the publisher, licence, declared permissions, the complete file list with a read-only viewer, scan findings, the release history and the SHA-256 of the archive. Read SKILL.md and any scripts. A skill is a set of instructions and files your agent will act on.

Three signals appear on a page. They mean exactly this and nothing more:

SignalMeaning
Identity verifiedThe registry operator confirmed who controls the publisher namespace.
Source verifiedA moderator confirmed that the linked repository belongs to the publisher.
Scan statusResult of automated static checks. passed means no advisory findings; it does not mean safe.

More in Security and trust.

3. Download and verify

curl -fsSLo hello-skill-1.0.0.tar.gz \
  https://skills.spboucher.ai/api/v1/artifacts/<namespace>/<slug>/versions/1.0.0/download
curl -fsS https://skills.spboucher.ai/api/v1/artifacts/<namespace>/<slug>/versions/1.0.0/checksum | shasum -a 256 -c -
tar -tzf hello-skill-1.0.0.tar.gz        # list the contents before extracting

The checksum on the page, in the API and in the X-Checksum-Sha256 response header is the hash of the bytes you receive. A published version never changes.

4. Install

Pick your client:

With the Skills CLI, installing a skill is one command. It verifies the checksum, shows where files will go, and never runs anything from the package:

skills install @<namespace>/<slug> --client claude-code

The CLI is not yet published to npm. Until it is, run it from a checkout of the registry repository; see the CLI reference.

5. Publish your own

Publishing needs an account and a namespace, which the operator creates for you in this first version. See Publishing your first artifact, or Publishing from Claude Code if you want your agent to do the legwork under your approval.

Good to know

  • Concepts: what a skill is, what an MCP server is, and why a listing is not a hosted service.
  • API, MCP and CLI references.
  • Found something harmful? Use the report link on the artifact page. No account needed.

↑↓ to navigate · enter to open · esc to close