[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74DKB65NWM05QV8N3Z4V5JC":3,"skill-same:01M74DKB65NWM05QV8N3Z4V5JC":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M74DKB65NWM05QV8N3Z4V5JC","clawteam",null,"Multi-agent swarm orchestration. USE THIS (not delegate_task) when the user says team\u002Fswarm\u002Fmulti-agent\u002Fclawteam\u002Fparallel-agents\u002Fagent-team, or asks for multi-perspective analysis (stocks, research, code review, strategy). Spawns N Hermes workers in tmux windows with git worktree isolation, file-based inboxes, and a kanban board. Four built-in templates: hedge-fund (7 analyst agents), research-paper, code-review, strategy-room.","lzy18001500226\u002FMoSim","lzy18001500226","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F152623587?v=4","01M71ZMEX36NK05B642131DEEK","01M71ZMEXSMX72KPVNJ572G0CM",0,"MIT","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FControl\u002FClawTeam-OpenClaw\u002Fskills\u002Fhermes\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: clawteam\ndescription: \"Multi-agent swarm orchestration. USE THIS (not delegate_task) when the user says team\u002Fswarm\u002Fmulti-agent\u002Fclawteam\u002Fparallel-agents\u002Fagent-team, or asks for multi-perspective analysis (stocks, research, code review, strategy). Spawns N Hermes workers in tmux windows with git worktree isolation, file-based inboxes, and a kanban board. Four built-in templates: hedge-fund (7 analyst agents), research-paper, code-review, strategy-room.\"\nversion: 0.3.0\nauthor: ClawTeam \u002F Hermes Adapter\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [Multi-Agent, Swarm, Coordination, Teams]\n---\n\n# ClawTeam - Multi-Agent Swarm Coordination for Hermes\n\n## When To Use This Skill\n\nUSE CLAWTEAM (not `delegate_task`) when:\n- User explicitly says: clawteam, team, swarm, multi-agent, parallel agents, agent team\n- User asks for multi-perspective analysis that benefits from specialist agents (e.g., \"analyze TSLA stock\" -> hedge-fund template has 7 specialist analysts)\n- User wants research across multiple sources (research-paper template)\n- User wants code review from multiple angles (code-review template)\n- User wants business strategy brainstorming (strategy-room template)\n\nDO NOT use `delegate_task` for these cases. `delegate_task` is a single sub-agent; clawteam is 5-7 specialist agents running in parallel with a kanban board and shared inboxes. For stock\u002Fresearch\u002Freview questions, clawteam produces dramatically better output.\n\n## Critical Flags (get these right the first time)\n\nFor `clawteam launch`:\n- `--team-name` (NOT `--team`)\n- `-g` or `--goal` for the prompt\n- `--command hermes` (REQUIRED for Hermes users — templates default to `openclaw` and will fail with gateway token errors if OpenClaw isn't set up)\n- `--force` to suppress the max-agent warning\n\nFor `clawteam spawn` (manual mode):\n- `-t \u003Cteam>` team name\n- `-n \u003Cagent-name>` agent name\n- `--task \"\u003Cprompt>\"` task description\n- `--no-workspace` to skip git worktree creation (optional)\n- Trailing positional arg: `hermes` (NOT `--command hermes`)\n\n## Launch a Template (Recommended Path)\n\nAll built-in templates default to `command = [\"openclaw\"]`. Hermes users MUST pass `--command hermes`:\n\n```bash\n# Stock analysis (7 specialist analysts: portfolio-manager, buffett, growth, technical, fundamentals, sentiment, risk-manager)\nclawteam launch hedge-fund --team-name tesla --goal \"Analyze TSLA\" --command hermes --force\n\n# Research paper summary\nclawteam launch research-paper --team-name papers --goal \"Survey arxiv 2024.X\" --command hermes --force\n\n# Code review (multiple perspectives)\nclawteam launch code-review --team-name review1 --goal \"Review PR #42\" --command hermes --force\n\n# Business strategy\nclawteam launch strategy-room --team-name strat --goal \"Q2 planning\" --command hermes --force\n```\n\n## CRITICAL: Timing Expectations (DO NOT cleanup early)\n\nSpawned Hermes workers need substantial time to produce output:\n- **Boot: 20-40 seconds per worker** (loading 62 tools + 113 skills + MCP servers)\n- **Research\u002Fanalysis: 1-5 minutes** depending on task complexity\n- **Hedge-fund template (7 analysts running in parallel): typically 2-5 minutes total**\n\nAfter launching a team, WAIT before checking results. NEVER check inboxes within the first 60 seconds — they will be empty and you will incorrectly conclude the team failed.\n\nCorrect polling pattern for a hedge-fund team:\n\n```bash\n# Launch\nclawteam launch hedge-fund --team-name \u003Cname> --goal \"\u003Cprompt>\" --command hermes --force\n\n# Wait for boot (mandatory, do not skip)\nsleep 60\n\n# Poll the board every 30 seconds until tasks move to COMPLETED.\n# Maximum total wait: ~5 minutes. Use tmux capture to see worker progress.\nfor i in 1 2 3 4 5 6 7 8; do\n  sleep 30\n  echo \"=== tick $i ($(( i * 30 + 60 ))s elapsed) ===\"\n  clawteam board show \u003Cname>\n  # Check if any non-leader task is COMPLETED (then continue monitoring)\n  # Break the loop only when most\u002Fall tasks show COMPLETED\ndone\n\n# Only read inboxes after tasks show COMPLETED on the board\nfor agent in portfolio-manager buffett-analyst growth-analyst technical-analyst fundamentals-analyst sentiment-analyst risk-manager; do\n  echo \"=== $agent ===\"\n  clawteam inbox peek \u003Cname> --agent $agent\ndone\n\n# Clean up ONLY after you've read the reports\nclawteam team cleanup \u003Cname> --force\n```\n\nIf inboxes are still empty after 5 minutes, something is wrong (token auth, model provider, or worker crashed). Inspect instead of giving up:\n\n```bash\nclawteam team status \u003Cname>                                  # Check liveness of each agent\ntmux list-windows -t clawteam-\u003Cname> 2>\u002Fdev\u002Fnull             # Confirm tmux panes exist\ntmux capture-pane -t clawteam-\u003Cname>:0 -p 2>&1 | tail -30    # Inspect worker 0's output\n```\n\n## Manual Inbox\u002FCleanup Commands (reference)\n\n```bash\nclawteam board show \u003Cteam>                   # Kanban view\nclawteam board live \u003Cteam>                   # Auto-refreshing board\nclawteam inbox peek \u003Cteam> --agent \u003Cname>    # Peek one agent's inbox\nclawteam team status \u003Cteam>                  # Agent liveness + health\nclawteam team cleanup \u003Cteam> --force         # Delete team (only after reading reports)\n```\n\n## Manual Team Setup (For Custom Teams)\n\nWhen no template fits:\n\n```bash\n# 1. Create team\nclawteam team spawn-team my-team -d \"Goal description\" -n leader\n\n# 2. Spawn Hermes workers (hermes is a positional arg at the end, NOT --command hermes)\nclawteam spawn -t my-team -n researcher --task \"Research X\" --no-workspace hermes\nclawteam spawn -t my-team -n writer --task \"Write report based on researcher's findings\" --no-workspace hermes\n\n# 3. Monitor\nclawteam board show my-team\n```\n\n## How The Hermes Adapter Builds Commands\n\nWhen ClawTeam spawns a Hermes worker, the adapter builds:\n\n```\nhermes chat --yolo --source tool -q \"\u003Ctask prompt>\"\n```\n\nNotes on each flag:\n- `chat` subcommand inserted only if user passed bare `hermes`\n- `--yolo` when `skip_permissions=True` (default for clawteam)\n- `--source tool` is intended to tag the session so clawteam spawns don't clutter `hermes sessions list`. **Known limitation on Hermes ≤ 0.8.0:** the flag is accepted but not propagated to the SQLite store — sessions still record as `source=cli`. ClawTeam passes the flag correctly; the fix belongs upstream (`run_agent.py:1057` and `:6600` short-circuit on `self.platform=\"cli\"` before reading `HERMES_SESSION_SOURCE`). See [Known upstream issues](#known-upstream-issues) below for the one-line patch.\n- `-q \"\u003Cprompt>\"` passes the task as a one-shot query\n- No `--continue` — Hermes auto-generates a fresh session ID per spawn\n- `-m \u003Cmodel>` added if `--model` was passed to clawteam\n\n## Known upstream issues\n\n### `--source tool` ignored by Hermes ≤ 0.8.0\n\nHermes's `cmd_chat` correctly sets `HERMES_SESSION_SOURCE` from the flag, but the agent constructor's session-create call reads `self.platform` first:\n\n```python\n# hermes-agent\u002Frun_agent.py:1057 and :6600 (pre-fix)\nsource=self.platform or os.environ.get(\"HERMES_SESSION_SOURCE\", \"cli\"),\n```\n\n`cli.py` hardcodes `platform=\"cli\"`, which is truthy, so the env var never wins. One-line fix (swap the precedence):\n\n```python\nsource=os.environ.get(\"HERMES_SESSION_SOURCE\") or self.platform or \"cli\",\n```\n\nVerify post-fix with: `hermes chat --yolo --source tool -q \"ping\" && hermes sessions list --source tool`. Until this lands upstream, ClawTeam-spawned Hermes workers appear interleaved with your interactive sessions — annoying, not broken.\n\n## MCP Inheritance\n\nSpawned Hermes workers inherit any MCP servers configured in `~\u002F.hermes\u002Fconfig.yaml`. If you have a knowledge base, memory store, or other MCP tool wired into Hermes, every worker gets that capability automatically.\n\nInclude MCP-related instructions in task prompts if you want workers to use them:\n```bash\nclawteam spawn -t research -n analyst --task \"Research topic X. Use available MCP tools to check prior work and store findings.\" --no-workspace hermes\n```\n\n## Command Reference\n\n### Team Management\n\n| Command | Description |\n|---------|-------------|\n| `clawteam team spawn-team \u003Cname> -d \"\u003Cdesc>\" -n \u003Cleader>` | Create team |\n| `clawteam team discover` | List all teams |\n| `clawteam team status \u003Cteam>` | Show team status |\n| `clawteam team cleanup \u003Cteam> --force` | Delete team |\n\n### Launching Templates\n\n| Command | Description |\n|---------|-------------|\n| `clawteam launch \u003Ctemplate> --team-name \u003Cname> --goal \"\u003Cprompt>\" --command hermes --force` | One-command team launch |\n| `clawteam template list` | List available templates |\n\n### Spawning Agents Manually\n\n| Command | Description |\n|---------|-------------|\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" hermes` | Spawn Hermes worker |\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" --skip-permissions hermes` | Spawn with --yolo |\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" -m claude-sonnet-4 hermes` | Spawn with specific model |\n\n### Task Management\n\n| Command | Description |\n|---------|-------------|\n| `clawteam task create \u003Cteam> \"\u003Cdesc>\" -o \u003Cowner>` | Create task |\n| `clawteam task create \u003Cteam> \"\u003Cdesc>\" -o \u003Cowner> --blocked-by \u003Cid>` | Create with dependency |\n| `clawteam task update \u003Cteam> \u003Cid> --status completed` | Complete task |\n| `clawteam task list \u003Cteam>` | List all tasks |\n\n### Messaging\n\n| Command | Description |\n|---------|-------------|\n| `clawteam msg send \u003Cteam> --from \u003Cname> --to \u003Cname> \"\u003Cmsg>\"` | Direct message |\n| `clawteam msg broadcast \u003Cteam> --from \u003Cname> \"\u003Cmsg>\"` | Broadcast to all |\n| `clawteam inbox peek \u003Cteam> --agent \u003Cname>` | Peek at inbox |\n| `clawteam inbox receive \u003Cteam>` | Drain your own inbox |\n\n### Monitoring\n\n| Command | Description |\n|---------|-------------|\n| `clawteam board show \u003Cteam>` | Kanban board |\n| `clawteam board attach \u003Cteam>` | Tmux tiled view (requires terminal) |\n| `clawteam board live \u003Cteam>` | Auto-refreshing board |\n| `clawteam board serve --port 8080` | Web dashboard |\n\n## Known Failure Modes\n\n1. **risk-manager crash**: The risk-manager agent is prone to crashing mid-execution (`\"Agent 'risk-manager' exited unexpectedly. Reset N task(s) to pending\"`). This can leave the team's final synthesis incomplete. If this happens, read tmux scrollback for the portfolio-manager (leader) window first — it may have the final recommendation before the crash.\n\n2. **Inbox empty despite COMPLETED tasks**: Hermes workers write to tmux scrollback, not to the inbox system. The kanban board reflects task state but not content. Always capture tmux panes to read actual output.\n\n3. **Workers do not persist findings**: Agent outputs live in tmux scrollback and are lost when the session is cleaned up. Capture the panes before running `team cleanup`, or instruct agents (via the task prompt) to write to any MCP-backed persistence store configured in `~\u002F.hermes\u002Fconfig.yaml`.\n\n## CRITICAL: Inbox Peek Is Unreliable — Use Tmux Capture\n\n`clawteam inbox peek` often returns EMPTY even when tasks show COMPLETED on the board. The actual agent outputs live in **tmux scrollback**, not in the inbox system.\n\n**Always use tmux pane capture to read agent reports:**\n\n```bash\n# List all tmux windows for the team\ntmux list-windows -t clawteam-\u003Cteam-name> 2>\u002Fdev\u002Fnull\n\n# Capture each window's scrollback (each window = one agent)\nfor win in $(tmux list-windows -t clawteam-\u003Cteam-name> -F '#{window_index}' 2>\u002Fdev\u002Fnull); do\n  echo -e \"\\n\\n=== Window $win ===\"\n  tmux capture-pane -t clawteam-\u003Cteam-name>:$win -p 2>&1 | tail -100\ndone\n```\n\n**Also:** If you have an MCP-backed persistence store (knowledge base, memory system) wired into `~\u002F.hermes\u002Fconfig.yaml`, include instructions in the goal so agents write findings there. This gives you a persistent fallback when tmux sessions are lost. Exact tool names depend on which MCP server you use.\n\n## Anti-Patterns (Do Not Do)\n\n- Don't use `delegate_task` when the user asks for multi-agent\u002Fswarm\u002Fteam analysis. Use clawteam.\n- Don't pass `--team` (the flag is `--team-name`).\n- Don't pass `--command hermes` to `spawn` (it's a positional arg at the end). That flag only works on `launch`.\n- Don't forget `--command hermes` on `launch` — templates default to openclaw.\n- Don't assume templates will use Hermes by default. They don't. Always pass `--command hermes`.\n- Don't clean up the team before reading final reports — BUT `inbox peek` alone is unreliable; always ALSO capture tmux panes.\n- Don't rely on `clawteam inbox peek` alone — tasks can be COMPLETED on the board while inbox messages are empty. Tmux scrollback capture is the source of truth.\n","# ClawTeam - Multi-Agent Swarm Coordination for Hermes\n\n## When To Use This Skill\n\nUSE CLAWTEAM (not `delegate_task`) when:\n- User explicitly says: clawteam, team, swarm, multi-agent, parallel agents, agent team\n- User asks for multi-perspective analysis that benefits from specialist agents (e.g., \"analyze TSLA stock\" -> hedge-fund template has 7 specialist analysts)\n- User wants research across multiple sources (research-paper template)\n- User wants code review from multiple angles (code-review template)\n- User wants business strategy brainstorming (strategy-room template)\n\nDO NOT use `delegate_task` for these cases. `delegate_task` is a single sub-agent; clawteam is 5-7 specialist agents running in parallel with a kanban board and shared inboxes. For stock\u002Fresearch\u002Freview questions, clawteam produces dramatically better output.\n\n## Critical Flags (get these right the first time)\n\nFor `clawteam launch`:\n- `--team-name` (NOT `--team`)\n- `-g` or `--goal` for the prompt\n- `--command hermes` (REQUIRED for Hermes users — templates default to `openclaw` and will fail with gateway token errors if OpenClaw isn't set up)\n- `--force` to suppress the max-agent warning\n\nFor `clawteam spawn` (manual mode):\n- `-t \u003Cteam>` team name\n- `-n \u003Cagent-name>` agent name\n- `--task \"\u003Cprompt>\"` task description\n- `--no-workspace` to skip git worktree creation (optional)\n- Trailing positional arg: `hermes` (NOT `--command hermes`)\n\n## Launch a Template (Recommended Path)\n\nAll built-in templates default to `command = [\"openclaw\"]`. Hermes users MUST pass `--command hermes`:\n\n```bash\n# Stock analysis (7 specialist analysts: portfolio-manager, buffett, growth, technical, fundamentals, sentiment, risk-manager)\nclawteam launch hedge-fund --team-name tesla --goal \"Analyze TSLA\" --command hermes --force\n\n# Research paper summary\nclawteam launch research-paper --team-name papers --goal \"Survey arxiv 2024.X\" --command hermes --force\n\n# Code review (multiple perspectives)\nclawteam launch code-review --team-name review1 --goal \"Review PR #42\" --command hermes --force\n\n# Business strategy\nclawteam launch strategy-room --team-name strat --goal \"Q2 planning\" --command hermes --force\n```\n\n## CRITICAL: Timing Expectations (DO NOT cleanup early)\n\nSpawned Hermes workers need substantial time to produce output:\n- **Boot: 20-40 seconds per worker** (loading 62 tools + 113 skills + MCP servers)\n- **Research\u002Fanalysis: 1-5 minutes** depending on task complexity\n- **Hedge-fund template (7 analysts running in parallel): typically 2-5 minutes total**\n\nAfter launching a team, WAIT before checking results. NEVER check inboxes within the first 60 seconds — they will be empty and you will incorrectly conclude the team failed.\n\nCorrect polling pattern for a hedge-fund team:\n\n```bash\n# Launch\nclawteam launch hedge-fund --team-name \u003Cname> --goal \"\u003Cprompt>\" --command hermes --force\n\n# Wait for boot (mandatory, do not skip)\nsleep 60\n\n# Poll the board every 30 seconds until tasks move to COMPLETED.\n# Maximum total wait: ~5 minutes. Use tmux capture to see worker progress.\nfor i in 1 2 3 4 5 6 7 8; do\n  sleep 30\n  echo \"=== tick $i ($(( i * 30 + 60 ))s elapsed) ===\"\n  clawteam board show \u003Cname>\n  # Check if any non-leader task is COMPLETED (then continue monitoring)\n  # Break the loop only when most\u002Fall tasks show COMPLETED\ndone\n\n# Only read inboxes after tasks show COMPLETED on the board\nfor agent in portfolio-manager buffett-analyst growth-analyst technical-analyst fundamentals-analyst sentiment-analyst risk-manager; do\n  echo \"=== $agent ===\"\n  clawteam inbox peek \u003Cname> --agent $agent\ndone\n\n# Clean up ONLY after you've read the reports\nclawteam team cleanup \u003Cname> --force\n```\n\nIf inboxes are still empty after 5 minutes, something is wrong (token auth, model provider, or worker crashed). Inspect instead of giving up:\n\n```bash\nclawteam team status \u003Cname>                                  # Check liveness of each agent\ntmux list-windows -t clawteam-\u003Cname> 2>\u002Fdev\u002Fnull             # Confirm tmux panes exist\ntmux capture-pane -t clawteam-\u003Cname>:0 -p 2>&1 | tail -30    # Inspect worker 0's output\n```\n\n## Manual Inbox\u002FCleanup Commands (reference)\n\n```bash\nclawteam board show \u003Cteam>                   # Kanban view\nclawteam board live \u003Cteam>                   # Auto-refreshing board\nclawteam inbox peek \u003Cteam> --agent \u003Cname>    # Peek one agent's inbox\nclawteam team status \u003Cteam>                  # Agent liveness + health\nclawteam team cleanup \u003Cteam> --force         # Delete team (only after reading reports)\n```\n\n## Manual Team Setup (For Custom Teams)\n\nWhen no template fits:\n\n```bash\n# 1. Create team\nclawteam team spawn-team my-team -d \"Goal description\" -n leader\n\n# 2. Spawn Hermes workers (hermes is a positional arg at the end, NOT --command hermes)\nclawteam spawn -t my-team -n researcher --task \"Research X\" --no-workspace hermes\nclawteam spawn -t my-team -n writer --task \"Write report based on researcher's findings\" --no-workspace hermes\n\n# 3. Monitor\nclawteam board show my-team\n```\n\n## How The Hermes Adapter Builds Commands\n\nWhen ClawTeam spawns a Hermes worker, the adapter builds:\n\n```\nhermes chat --yolo --source tool -q \"\u003Ctask prompt>\"\n```\n\nNotes on each flag:\n- `chat` subcommand inserted only if user passed bare `hermes`\n- `--yolo` when `skip_permissions=True` (default for clawteam)\n- `--source tool` is intended to tag the session so clawteam spawns don't clutter `hermes sessions list`. **Known limitation on Hermes ≤ 0.8.0:** the flag is accepted but not propagated to the SQLite store — sessions still record as `source=cli`. ClawTeam passes the flag correctly; the fix belongs upstream (`run_agent.py:1057` and `:6600` short-circuit on `self.platform=\"cli\"` before reading `HERMES_SESSION_SOURCE`). See [Known upstream issues](#known-upstream-issues) below for the one-line patch.\n- `-q \"\u003Cprompt>\"` passes the task as a one-shot query\n- No `--continue` — Hermes auto-generates a fresh session ID per spawn\n- `-m \u003Cmodel>` added if `--model` was passed to clawteam\n\n## Known upstream issues\n\n### `--source tool` ignored by Hermes ≤ 0.8.0\n\nHermes's `cmd_chat` correctly sets `HERMES_SESSION_SOURCE` from the flag, but the agent constructor's session-create call reads `self.platform` first:\n\n```python\n# hermes-agent\u002Frun_agent.py:1057 and :6600 (pre-fix)\nsource=self.platform or os.environ.get(\"HERMES_SESSION_SOURCE\", \"cli\"),\n```\n\n`cli.py` hardcodes `platform=\"cli\"`, which is truthy, so the env var never wins. One-line fix (swap the precedence):\n\n```python\nsource=os.environ.get(\"HERMES_SESSION_SOURCE\") or self.platform or \"cli\",\n```\n\nVerify post-fix with: `hermes chat --yolo --source tool -q \"ping\" && hermes sessions list --source tool`. Until this lands upstream, ClawTeam-spawned Hermes workers appear interleaved with your interactive sessions — annoying, not broken.\n\n## MCP Inheritance\n\nSpawned Hermes workers inherit any MCP servers configured in `~\u002F.hermes\u002Fconfig.yaml`. If you have a knowledge base, memory store, or other MCP tool wired into Hermes, every worker gets that capability automatically.\n\nInclude MCP-related instructions in task prompts if you want workers to use them:\n```bash\nclawteam spawn -t research -n analyst --task \"Research topic X. Use available MCP tools to check prior work and store findings.\" --no-workspace hermes\n```\n\n## Command Reference\n\n### Team Management\n\n| Command | Description |\n|---------|-------------|\n| `clawteam team spawn-team \u003Cname> -d \"\u003Cdesc>\" -n \u003Cleader>` | Create team |\n| `clawteam team discover` | List all teams |\n| `clawteam team status \u003Cteam>` | Show team status |\n| `clawteam team cleanup \u003Cteam> --force` | Delete team |\n\n### Launching Templates\n\n| Command | Description |\n|---------|-------------|\n| `clawteam launch \u003Ctemplate> --team-name \u003Cname> --goal \"\u003Cprompt>\" --command hermes --force` | One-command team launch |\n| `clawteam template list` | List available templates |\n\n### Spawning Agents Manually\n\n| Command | Description |\n|---------|-------------|\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" hermes` | Spawn Hermes worker |\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" --skip-permissions hermes` | Spawn with --yolo |\n| `clawteam spawn -t \u003Cteam> -n \u003Cname> --task \"\u003Cprompt>\" -m claude-sonnet-4 hermes` | Spawn with specific model |\n\n### Task Management\n\n| Command | Description |\n|---------|-------------|\n| `clawteam task create \u003Cteam> \"\u003Cdesc>\" -o \u003Cowner>` | Create task |\n| `clawteam task create \u003Cteam> \"\u003Cdesc>\" -o \u003Cowner> --blocked-by \u003Cid>` | Create with dependency |\n| `clawteam task update \u003Cteam> \u003Cid> --status completed` | Complete task |\n| `clawteam task list \u003Cteam>` | List all tasks |\n\n### Messaging\n\n| Command | Description |\n|---------|-------------|\n| `clawteam msg send \u003Cteam> --from \u003Cname> --to \u003Cname> \"\u003Cmsg>\"` | Direct message |\n| `clawteam msg broadcast \u003Cteam> --from \u003Cname> \"\u003Cmsg>\"` | Broadcast to all |\n| `clawteam inbox peek \u003Cteam> --agent \u003Cname>` | Peek at inbox |\n| `clawteam inbox receive \u003Cteam>` | Drain your own inbox |\n\n### Monitoring\n\n| Command | Description |\n|---------|-------------|\n| `clawteam board show \u003Cteam>` | Kanban board |\n| `clawteam board attach \u003Cteam>` | Tmux tiled view (requires terminal) |\n| `clawteam board live \u003Cteam>` | Auto-refreshing board |\n| `clawteam board serve --port 8080` | Web dashboard |\n\n## Known Failure Modes\n\n1. **risk-manager crash**: The risk-manager agent is prone to crashing mid-execution (`\"Agent 'risk-manager' exited unexpectedly. Reset N task(s) to pending\"`). This can leave the team's final synthesis incomplete. If this happens, read tmux scrollback for the portfolio-manager (leader) window first — it may have the final recommendation before the crash.\n\n2. **Inbox empty despite COMPLETED tasks**: Hermes workers write to tmux scrollback, not to the inbox system. The kanban board reflects task state but not content. Always capture tmux panes to read actual output.\n\n3. **Workers do not persist findings**: Agent outputs live in tmux scrollback and are lost when the session is cleaned up. Capture the panes before running `team cleanup`, or instruct agents (via the task prompt) to write to any MCP-backed persistence store configured in `~\u002F.hermes\u002Fconfig.yaml`.\n\n## CRITICAL: Inbox Peek Is Unreliable — Use Tmux Capture\n\n`clawteam inbox peek` often returns EMPTY even when tasks show COMPLETED on the board. The actual agent outputs live in **tmux scrollback**, not in the inbox system.\n\n**Always use tmux pane capture to read agent reports:**\n\n```bash\n# List all tmux windows for the team\ntmux list-windows -t clawteam-\u003Cteam-name> 2>\u002Fdev\u002Fnull\n\n# Capture each window's scrollback (each window = one agent)\nfor win in $(tmux list-windows -t clawteam-\u003Cteam-name> -F '#{window_index}' 2>\u002Fdev\u002Fnull); do\n  echo -e \"\\n\\n=== Window $win ===\"\n  tmux capture-pane -t clawteam-\u003Cteam-name>:$win -p 2>&1 | tail -100\ndone\n```\n\n**Also:** If you have an MCP-backed persistence store (knowledge base, memory system) wired into `~\u002F.hermes\u002Fconfig.yaml`, include instructions in the goal so agents write findings there. This gives you a persistent fallback when tmux sessions are lost. Exact tool names depend on which MCP server you use.\n\n## Anti-Patterns (Do Not Do)\n\n- Don't use `delegate_task` when the user asks for multi-agent\u002Fswarm\u002Fteam analysis. Use clawteam.\n- Don't pass `--team` (the flag is `--team-name`).\n- Don't pass `--command hermes` to `spawn` (it's a positional arg at the end). That flag only works on `launch`.\n- Don't forget `--command hermes` on `launch` — templates default to openclaw.\n- Don't assume templates will use Hermes by default. They don't. Always pass `--command hermes`.\n- Don't clean up the team before reading final reports — BUT `inbox peek` alone is unreliable; always ALSO capture tmux panes.\n- Don't rely on `clawteam inbox peek` alone — tasks can be COMPLETED on the board while inbox messages are empty. Tmux scrollback capture is the source of truth.\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"description":7},"ClawTeam \u002F Hermes Adapter","0.3.0",{"hermes":26},{"tags":27},[28,29,30,31],"Multi-Agent","Swarm","Coordination","Teams","main","e0ec177d00f087cb04e90206b2f7d3aa2f5a1350","References\u002FAgent\u002FControl\u002FClawTeam-OpenClaw\u002Fskills\u002Fhermes","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim","https:\u002F\u002Fgithub.com\u002Flzy18001500226","2026-08-31 23:29:00",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lzy18001500226\u002FMoSim --skill clawteam",{"tool":44,"command":45},"bunx","bunx skills add lzy18001500226\u002FMoSim --skill clawteam",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lzy18001500226\u002FMoSim --skill clawteam","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FControl\u002FClawTeam-OpenClaw\u002Fskills\u002Fhermes\u002FSKILL.md",true,[],[53,63,71,79,87,95],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M78RK6JGRPTD3TDSMTQWDQ9P","skill-installer","Install Codex skills into $CODEX_HOME\u002Fskills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-installer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":62},"01M78RK29KVRDQXSMVZX1GQTJN","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":62},"01M78RJPF3210Y5DA9VJ6JMMG6","openai-docs","Use for Codex models\u002Fpricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs\u002Fproducts and ChatGPT Work. Also use for model choice\u002Fmigration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat\u002FWork\u002FCodex comparisons. Do not use for generic app\u002Fsoftware tasks that merely mention Codex.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fopenai-docs\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":62},"01M78RJH7X67C5AY8ZVS7RQNWJ","imagegen","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002Fsrc\u002FAgent\u002Fcodex-main\u002Fcodex-rs\u002Fskills\u002Fsrc\u002Fassets\u002Fsamples\u002Fimagegen\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":57,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":62},"01M78RBBAYMJ6T3ZMAYHCFM6G7","skill-creator-cc","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fskill-creator-cc\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":103},"01M76VV9V2R9FZTVGMJZV7Y996","prd-writing-guide","Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Flzy18001500226\u002FMoSim\u002Fblob\u002Fmain\u002FReferences\u002FAgent\u002FWorkflow\u002Fokwinds\u002Fmiscellany\u002Fagent\u002Fskills\u002Fprd-writing-guide\u002FSKILL.md",[],[],"2026-11-12 13:55:43"]