For the complete documentation index, see llms.txt. This page is also available as Markdown.

Discover & Use Skills

This page walks through installing AgentRoot in your AI agent, resolving a domain's published records, and installing a skill into your agent's local skills folder.

Install AgentRoot in your agent

Three options depending on how your agent loads tools:

Option 1: As a CLI

npm install -g agent-root
agent-root --version

Then call agent-root resolve <domain> directly, or wrap it in a tool definition for your agent.

Option 2: As an MCP server

Add AgentRoot to your agent's MCP config. The exact location varies per tool:

Tool
Config file

Claude Code

~/.claude.json (mcpServers block)

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json

Cursor

~/.cursor/mcp.json

Codex CLI

~/.codex/mcp.json

Generic config snippet:

{
  "mcpServers": {
    "agent-root": {
      "command": "npx",
      "args": ["-y", "agent-root", "mcp"]
    }
  }
}

After restart, the agent has access to agentroot_resolve, agentroot_install_record, and agentroot_list tools.

Option 3: As a library

Use programmatically when building your own agent or backend integration.

Resolve a domain

Discover what a domain offers:

Sample output:

This is the same data the agent uses internally to decide which skill to install for a given user intent.

Install a skill

Pick a record by id and install it:

Where the skill lands depends on which agent tool is detected first on PATH / config:

Tool
Skill install path

Claude Code / Claude Desktop

~/.claude/skills/doma.xyz/trade-tokens/

Cursor

~/.cursor/skills/doma.xyz/trade-tokens/

Codex CLI

~/.codex/skills/doma.xyz/trade-tokens/

Gemini CLI

~/.gemini/skills/doma.xyz/trade-tokens/

OpenCode

~/.opencode/skills/doma.xyz/trade-tokens/

Force a specific tool with --tool=<name>:

List installed skills

Output shows skill ID, source domain, install path, and verification status.

Skills are downloaded to disk and become part of your agent's runtime context. They update only when you re-install them; there is no auto-refresh. Re-run agent-root install after a publisher updates their SKILL.md.

Verify the install in your agent

After installing, prompt your agent with one of the skill's trigger phrases (listed in each skill's reference page). For example, after installing trade-tokens:

Example prompt: Buy 10 USDC worth of <token-name> token.

The agent should pick up the trigger, follow the workflow encoded in SKILL.md, and walk you through prerequisites + execution.

What's next

Last updated