> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills

> Skill files an AI agent can fetch and follow — one per StateSet system — with the URL convention, what each covers, and how to load them into an agent harness.

A **skill** is a short document written for an agent rather than a person: what a system is, how
to authenticate, the handful of calls that matter, the encodings that trip agents up, and the
guardrails to keep. An agent that has read the skill can use the system without having read the
reference.

Every skill page here is also published as plain Markdown at the same path with a `.md`
extension, which is the form an agent should fetch:

```
https://docs.stateset.com/<page>.md
```

## The skills

| Skill                                                                       | Fetch                            | Covers                                                                               |
| --------------------------------------------------------------------------- | -------------------------------- | ------------------------------------------------------------------------------------ |
| [iCommerce Engine](/stateset-icommerce-skill)                               | `/stateset-icommerce-skill.md`   | The embedded commerce engine, its CLI, sequencer sync, and the 938-tool MCP surface  |
| [NSR](/stateset-nsr-skill)                                                  | `/stateset-nsr-skill.md`         | Verified decisions with proofs; teaching rules; verifying and reporting outcomes     |
| [Sandbox](/stateset-sandbox-skill)                                          | `/stateset-sandbox-skill.md`     | Isolated execution: create, run, read files, tear down                               |
| [Voice](/stateset-voice-skill)                                              | `/stateset-voice-skill.md`       | Voice agents, number routing, calls, transcripts, latency, the MCP server            |
| [Computer Use](/computer-use-skill)                                         | `/computer-use-skill.md`         | Preview, trigger, wait for and read the result of a computer-use job                 |
| [Sync Server](/stateset-sync-server-skill)                                  | `/stateset-sync-server-skill.md` | Tenant-scoped order and inventory sync across 180+ integrations, by REST, CLI or MCP |
| [iCommerce skills catalogue](/stateset-icommerce/stateset-icommerce-skills) | —                                | The skills the iCommerce agent itself ships with, and how to add one                 |

## Loading a skill

<CodeGroup>
  ```bash Claude Code theme={null}
  # skills live in ~/.claude/skills/<name>/SKILL.md
  mkdir -p ~/.claude/skills/stateset-nsr
  curl -sL https://docs.stateset.com/stateset-nsr-skill.md -o ~/.claude/skills/stateset-nsr/SKILL.md
  ```

  ```bash Any agent theme={null}
  # fetch at run time and put the text in the system prompt or a tool result
  curl -sL https://docs.stateset.com/stateset-nsr-skill.md
  ```
</CodeGroup>

Each skill opens with YAML frontmatter — `name`, `description` — so a harness that indexes skills
by description can pick the right one from the task alone.

## Skills and MCP servers

A skill tells an agent *how to think about* a system; an [MCP server](/mcp-servers) gives it
*tools to act on* one. They pair: the skill names which tools to prefer, which to preview before
running, and which take an idempotency key. Load the skill, connect the server.

## Writing your own

The skills above share a shape worth copying: what the system is in two sentences, how to
connect, the two or three calls that cover most work, the encodings that break, the rule to keep.
Under a hundred and fifty lines. A skill that tries to be the reference is one the agent will not
finish reading.