# Clawteam Dev

Use this skill when working inside the ClawTeam repository itself: local development...

- Repository: https://github.com/HKUDS/ClawTeam (5547 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-05-09
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add HKUDS/ClawTeam --skill clawteam-dev -g -a claude-code -y`
Codex: `npx skills add HKUDS/ClawTeam --skill clawteam-dev -g -a codex -y`
Cursor: `npx skills add HKUDS/ClawTeam --skill clawteam-dev -g -a cursor -y`
Gemini CLI: `npx skills add HKUDS/ClawTeam --skill clawteam-dev -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# ClawTeam Local Development

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.

## Development Bootstrap

Standardize the local development environment with the bootstrap script:

```bash
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:

- Creates a fixed uv environment at `~/.clawteam-venv`
- Installs the current repository into that environment with dev dependencies
- Writes `~/.local/bin/clawteam` to point at the fixed environment
- Adds a `clawteam()` shell function block to `~/.bashrc`

After it finishes:

```bash
source ~/.bashrc
clawteam --version
```

Use this bootstrap whenever you want the same `clawteam` command across different
Python environments on the machine.

## Project Skill Wiring

To wire another local project so its `./.agents` and `./.claude` directories use
this repository's local ClawTeam skills directly:

```bash
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/clawteam`

Run the same script again any time you want to refresh or recreate those links.

## Typical Uses

- Run targeted local validation after code changes
- Reproduce a spawn / board / task / inbox / harness bug
- Smoke-test the real CLI in tmux or subprocess mode
- Review ClawTeam workflows end-to-end from the current repository checkout

## Fast Validation

Prefer the smallest validation that proves the change.

```bash
ruff check clawteam/ tests/
pytest tests/<target_file>.py -q
```

Use broader runs only when the change crosses modules:

The rest: https://github.com/HKUDS/ClawTeam/blob/HEAD/.agents/skills/clawteam-dev/SKILL.md