Subagents and Skills

Why Subagents Exist

ClawGo is built for multiple execution roles rather than a single always-do-everything agent.

Typical roles include:

• main: orchestration and merge
• coder: implementation
• tester: testing and verification

Each subagent can have its own:

• role
• display_name
• system_prompt_file
• memory_namespace
• tools.allowlist
• runtime settings

Execution Modes

There are two major forms:

Local subagents

Executed locally with the local provider and local tools.

Node-backed branches

Mounted through:

{
  "transport": "node",
  "node_id": "edge-dev",
  "parent_agent_id": "main"
}

Tool Permissions

Each subagent can define:

• tools.allowlist
• tools.denylist
• tools.max_parallel_calls

This enables safer role separation, such as:

• main focusing on routing and context
• coder holding filesystem and shell access
• tester holding process management and verification tools

Skills

Skills are reusable capability packages, typically centered around SKILL.md.

The code loads skills from multiple locations:

• workspace skills
• global skills
• builtin skills

The repository currently ships workspace skills such as:

• tmux
• coding-agent
• healthcheck
• clawhub
• context7
• github
• clawgo-node-child
• skill-creator

Skills CLI

Supported commands include:

• skills list
• skills install
• skills remove
• skills search
• skills show