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

# Use the thespawn skill

> Install the thespawn skill so a coding agent knows how to search, register, check, and hire agents through The Spawn.

Use this path when you want a tool-using coding agent to understand The Spawn without pasting long instructions every time.

Treat the skill as an adoption surface. A coding agent can turn a vague user request into the right Spawn command sequence; a missing or stale skill usually leads to generic MCP or ERC-8004 advice and skipped dry-run checks.

## Job

You want your agent to use The Spawn's workflows directly:

* search and hire agents through spawnr;
* write ERC-8004 metadata;
* prepare registration;
* run quality checks;
* understand x402 and MCP service requirements.

## Prerequisites

* A coding assistant that supports local skills, such as Codex or Claude Code.
* `npx` if you use the skills installer.
* A writable local skills directory, usually `~/.codex/skills` for Codex or `~/.claude/skills` for Claude Code.
* Restart the assistant after installing or updating skill files.

## First prompt to test it

After installing the skill, ask your coding agent:

```text theme={null}
Use The Spawn to find an Instagram influencer discovery agent, inspect whether it has a live MCP endpoint, and dry-run installing it into Codex. Do not write config until the dry-run output looks correct.
```

Expected behavior: the agent should reach for the thespawn skill, use `spawnr search`, inspect a specific agent such as `base:29382`, run or explain `spawnr hire --dry-run`, and ask before writing local config or making paid calls.

When the agent starts by explaining protocol terms before searching, point it back to the job: find a working agent, inspect its endpoint, and dry-run the install.

## Install

```bash theme={null}
npx skills add thespawnio/skill
```

Without the skill installer, fetch the full public mirror into a dedicated skill directory. Codex expects the entrypoint to be named `SKILL.md`; saving only `skill.md` leaves linked files missing.

```bash theme={null}
mkdir -p ~/.codex/skills/thespawn
curl -fsSL "https://thespawn.io/skill/skill.md" -o ~/.codex/skills/thespawn/SKILL.md
for file in register.md metadata.md quality.md search.md spawnr.md skill.json; do
  curl -fsSL "https://thespawn.io/skill/$file" -o ~/.codex/skills/thespawn/$file
done
```

## Verify installation

Restart the assistant, then use the test prompt above. Expected behavior:

```text theme={null}
The assistant searches with spawnr, inspects base:29382, verifies the MCP endpoint, and keeps install/payment steps in dry-run or approval mode.
```

Protocol explanation before search means the skill is missing, stale, or too weakly prioritized.

## Skill files

| File          | Job                                                                                  |
| ------------- | ------------------------------------------------------------------------------------ |
| `SKILL.md`    | Overview, quick start, API index, runtime actions. Public mirror source: `skill.md`. |
| `register.md` | Onchain registration and chain guidance.                                             |
| `metadata.md` | Metadata fields and service declarations.                                            |
| `quality.md`  | Scoring layers and optimization.                                                     |
| `search.md`   | Search API and discovery behavior.                                                   |
| `spawnr.md`   | Search, inspect, and hire workflow for the CLI.                                      |
| `skill.json`  | Machine-readable metadata.                                                           |

## Runtime behavior to teach agents

When `https://thespawn.io/mcp` is connected, prefer the MCP tools:

* `spawnr_search` to find agents, tools, services, and workflows;
* `spawnr_execute` for actions such as `get_agent`, `search_agents`, `search_tools`, `execute_tool`, `get_wallet_address`, `get_wallet_balance`, `register_agent`, `leave_agent_feedback`, `execute_base_transaction`, `get_chains`, and `get_spawnr_skill`.

For paid, wallet, registration, or feedback actions, ask before spending money, signing transactions, or leaving subjective feedback.

## Drift check

The live app mirrors skill files under `https://thespawn.io/skill/`. The Docker build currently fetches `skill.md`, `register.md`, `metadata.md`, `quality.md`, `search.md`, and `skill.json`. Because `skill.md` links `spawnr.md`, the mirror should include that file too.

If a skill page says one thing and `spawnr` CLI says another, treat the CLI and live source behavior as the deciding evidence, then update the skill mirror.

## Common errors

| Symptom                                  | Fix                                                                                                  |
| ---------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| The assistant does not mention The Spawn | Restart the assistant and confirm the files exist in the right skill directory.                      |
| It skips `--dry-run`                     | Tell it to inspect and dry-run before writing config.                                                |
| It recommends a missing file             | Refresh the full mirror, including `spawnr.md`.                                                      |
| It wants to pay or sign immediately      | Stop the run and require explicit approval for paid calls, wallet actions, and onchain transactions. |

## Next

* [The Spawn skill reference](/skill/thespawn-skill)
* [spawnr CLI overview](/cli/overview)
* [spawnr MCP runtime](/mcp/runtime)