Use this skill when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually works end-to-end. Use the repository bootstrap scripts to standardize the local `clawteam` command and to wire project-local `.agents` and `.claude` skills back to this repository. This skill is repository-development oriented, not a general end-user usage guide.
This skill is for developing and validating ClawTeam inside the ClawTeam repository. Use it when the task is about changing ClawTeam itself, testing local behavior, or verifying multi-agent workflows against the current checkout.
Standardize the local development environment with the bootstrap script:
bash scripts/bootstrap_clawteam_dev.sh
This script lives in scripts/bootstrap_clawteam_dev.sh inside this skill folder.
This script does all of the following:
~/.clawteam-venv~/.local/bin/clawteam to point at the fixed environmentclawteam() shell function block to ~/.bashrcAfter it finishes:
source ~/.bashrc
clawteam --version
Use this bootstrap whenever you want the same clawteam command across different
Python environments on the machine.
To wire another local project so its ./.agents and ./.claude directories use
this repository's local ClawTeam skills directly:
bash scripts/link_local_clawteam_skills.sh /path/to/project
This script lives in scripts/link_local_clawteam_skills.sh inside this skill folder.
This creates these symlinks inside the target project:
./.agents/skills/clawteam./.claude/skills/clawteamRun the same script again any time you want to refresh or recreate those links.
Prefer the smallest validation that proves the change.
ruff check clawteam/ tests/
pytest tests/<target_file>.py -q
Use broader runs only when the change crosses modules:
pytest tests/test_cli_commands.py -q
pytest tests/test_spawn_backends.py -q
pytest tests/test_harness.py tests/test_event_bus.py -q
clawteam command availabletmux availableclaude or codex if you are spawning real workersUse this when you need a real multi-agent workflow check instead of unit tests.
clawteam team spawn-team dev-smoke -d "Local ClawTeam smoke test" -n leader
clawteam task create dev-smoke "Smoke test worker" -o worker1 -p high
clawteam spawn --team dev-smoke --agent-name worker1 --task "Report your status to leader and mark the task completed when done."
clawteam board show dev-smoke
clawteam task wait dev-smoke --timeout 300 --poll-interval 5
If you are validating harness behavior specifically:
clawteam harness conduct dev-harness \
--goal "Create a small implementation plan and execute it with one worker" \
--cli codex \
--agents 1
Use the real ClawTeam commands instead of ad-hoc directory assumptions whenever possible:
clawteam team cleanup dev-smoke
clawteam team cleanup dev-harness
If a crashed tmux session or worktree is left behind, clean it up explicitly after inspecting it.
clawteam commands over editing state files directly.board, task wait, and team status to observe behavior before assuming a bug is in the spawn layer.