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.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.
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.
npxif you use the skills installer.- A writable local skills directory, usually
~/.codex/skillsfor Codex or~/.claude/skillsfor Claude Code. - Restart the assistant after installing or updating skill files.
First prompt to test it
After installing the skill, ask your coding agent: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
SKILL.md; saving only skill.md leaves linked files missing.
Verify installation
Restart the assistant, then use the test prompt above. Expected behavior: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
Whenhttps://thespawn.io/mcp is connected, prefer the MCP tools:
spawnr_searchto find agents, tools, services, and workflows;spawnr_executefor actions such asget_agent,search_agents,search_tools,execute_tool,get_wallet_address,get_wallet_balance,register_agent,leave_agent_feedback,execute_base_transaction,get_chains, andget_spawnr_skill.
Drift check
The live app mirrors skill files underhttps://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. |