docs: add skill.md setup guide for agent bots#135
Conversation
Installation guide for AI agent bots (openclaw, Moltis, etc.) to set up CSA and Weave via mise, with interactive pattern selection by category. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a692d6d551
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # Compile them for your project: | ||
| for pattern in commit ai-reviewed-commit code-review pr-codex-bot; do | ||
| weave compile .weave/deps/cli-sub-agent/patterns/$pattern/PATTERN.md \ | ||
| --output .csa/plans/$pattern.toml |
There was a problem hiding this comment.
Create plans directory before compiling selected patterns
After Step 3, the guide only guarantees .csa/config.toml exists, but this command writes to .csa/plans/$pattern.toml without creating .csa/plans; weave compile --output ultimately writes the file directly and fails with ENOENT when the parent directory is missing. Users following any per-category install flow (A/B/C/D) will hit a hard failure unless they manually run mkdir -p .csa/plans first (which is currently only shown in the “Install All” section).
Useful? React with 👍 / 👎.
skill.md
Outdated
| [concurrency] | ||
| max_global_slots = 4 |
There was a problem hiding this comment.
Use supported global concurrency keys in config example
This config snippet documents [concurrency] max_global_slots, but CSA’s global config schema does not define that section/key, so it is ignored at load time; the supported concurrency settings are [defaults].max_concurrent and optional [tools.<tool>].max_concurrent. As written, users will believe they changed slot limits while CSA continues using default concurrency values.
Useful? React with 👍 / 👎.
- P1: add mkdir -p .csa/plans before weave compile in all category install blocks to prevent write failure on missing directory - P2: add verification notes and alternative install links for curl|sh commands (mise, rustup) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d5d3a7f5a7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
skill.md
Outdated
| [concurrency] | ||
| max_global_slots = 4 |
There was a problem hiding this comment.
Replace unsupported global concurrency setting
The config example sets [concurrency] max_global_slots = 4, but CSA's global schema reads concurrency from defaults.max_concurrent (and optional tools.<tool>.max_concurrent) in crates/csa-config/src/global.rs; there is no concurrency.max_global_slots field. Because this TOML key is ignored during deserialization, users following this guide will think they limited concurrency while CSA still runs with the default per-tool limit.
Useful? React with 👍 / 👎.
skill.md
Outdated
| | Claude Code + Codex | `["claude-code", "codex"]` | | ||
| | Codex + Gemini CLI | `["codex", "gemini-cli"]` | | ||
| | All tools available | `["claude-code", "codex", "gemini-cli", "opencode"]` | | ||
| | Single tool only | Set `[review] tool = "<tool>"` explicitly | |
There was a problem hiding this comment.
Add single-tool override for debate workflow
The single-tool recommendation only says to set [review] tool, but the same template leaves [debate] tool = "auto"; in auto mode, debate enforces heterogeneous tool selection and returns an error when no counterpart is available (debate_auto_resolution_error in crates/cli-sub-agent/src/debate_cmd.rs). On single-tool setups, this guidance still causes csa debate to fail unless [debate] tool is also explicitly configured.
Useful? React with 👍 / 👎.
- Replace invalid [concurrency] max_global_slots with correct [defaults] max_concurrent (matches GlobalConfig schema) - Add [debate] tool to single-tool config recommendation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
skill.md— installation guide for AI agent bots (openclaw, Moltis, etc.) to set up CSA and Weave via miseTest plan
skill.mdrenders correctly on GitHubskills/AGENTS.md🤖 Generated with Claude Code