Review
atelier-fashion/adlc-toolkit
Multi-agent code review covering correctness, quality, architecture, test coverage, and security
A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HKUDS/ClawTeam clawteam-dev --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/clawteam-dev .claude/skills/clawteam-dev && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .claude/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-devType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HKUDS/ClawTeam clawteam-dev --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/clawteam-dev .agents/skills/clawteam-dev && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .agents/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HKUDS/ClawTeam clawteam-dev --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/clawteam-dev .cursor/skills/clawteam-dev && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .cursor/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HKUDS/ClawTeam.git --path .agents/skills/clawteam-dev--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HKUDS/ClawTeam clawteam-dev --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/clawteam-dev .gemini/skills/clawteam-dev && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .gemini/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HKUDS/ClawTeam clawteam-devInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/clawteam-dev .github/skills/clawteam-dev && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .github/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HKUDS/ClawTeam --skill clawteam-dev -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HKUDS/ClawTeam clawteam-dev --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/ClawTeam.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/clawteam-dev .opencode/skills/clawteam-dev && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "clawteam-dev" agent skill from https://github.com/HKUDS/ClawTeam/tree/main/.agents/skills/clawteam-dev into .opencode/skills/clawteam-dev/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "clawteam-dev", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
clawteam-devA skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…
Clawteam Dev is an agent skill from HKUDS/ClawTeam. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/bootstrap_clawteam_dev.sh` and `scripts/link_local_clawteam_skills.sh`).
It sits in Testing & QA, covering Multi-agent orchestration. The repository describes itself as: "ClawTeam: Agent Swarm Intelligence" (One Command → Full Automation). The licence is MIT.
Read from SKILL.md and the folder at commit 0119833. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
pytestbashruffFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Clawteam Dev loads about 1.1k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 388 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from HKUDS/ClawTeam at commit 0119833, republished under its MIT licence (© HKUDS). 388 words, ~1,094 tokens.
.claude/skills/clawteam-dev/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.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.shThis 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 --versionUse 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/projectThis 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 -qUse 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 -qclawteam 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 5If 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 1Use the real ClawTeam commands instead of ad-hoc directory assumptions whenever possible:
clawteam team cleanup dev-smoke
clawteam team cleanup dev-harnessIf 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.© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in .agents/skills/clawteam-dev of HKUDS/ClawTeam.
Open the folder on GitHubat commit 0119833
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in HKUDS/ClawTeam, which our catalogue first saw on October 7, 2026.
Clawteam Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Clawteam Dev this skillHKUDS/ClawTeam | 5.5k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Reviewatelier-fashion/adlc-toolkit | 171 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Prompt Generatorcatlog22/Claude-Code-Workflow | 2.1k | 1 repos | ~4.7k | Automated safety check: Notes | MIT | |
| Workflow Reviewnabeelhyatt/coworkpowers | 114 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Multi Agent Task Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Agent Team OrchestrationaAAaqwq/AGI-Super-Team | 105 | 3 repos | ~1.4k | Automated safety check: Pass | MIT |
atelier-fashion/adlc-toolkit
Multi-agent code review covering correctness, quality, architecture, test coverage, and security
catlog22/Claude-Code-Workflow
Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.
nabeelhyatt/coworkpowers
Run parallel multi-agent review on completed knowledge work.
sickn33/agentic-awesome-skills
Route tasks to specialized AI agents with anti-duplication, quality gates, and 30-minute heartbeat monitoring
aAAaqwq/AGI-Super-Team
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows.
bybren-llc/safe-agentic-workflow
Agent Teams orchestration patterns for multi-agent SAFe workflows.
Categories
A skill your agent uses when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually…. Clawteam Dev is an agent skill from HKUDS/ClawTeam. 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.
Clawteam Dev fits situations like: working inside the ClawTeam repository itself: local development; validating multi-agent flows; checking whether a code change actually works end-to-end.
Run `npx skills add HKUDS/ClawTeam --skill clawteam-dev -a claude-code`. Or copy the skill folder (.agents/skills/clawteam-dev in HKUDS/ClawTeam) into .claude/skills/clawteam-dev in your project. Claude Code loads it when a task matches its description.
Run `npx skills add HKUDS/ClawTeam --skill clawteam-dev -a codex`. Or copy the skill folder (.agents/skills/clawteam-dev in HKUDS/ClawTeam) into .agents/skills/clawteam-dev in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HKUDS/ClawTeam --skill clawteam-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clawteam-dev, .gemini/skills/clawteam-dev, .github/skills/clawteam-dev and .opencode/skills/clawteam-dev in your project.
Going by SKILL.md and its folder, Clawteam Dev needs a shell for the scripts in its folder and the command-line tools its instructions call (pytest, bash and ruff). Our summary lists: Python 3; A Bash shell.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Clawteam Dev is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Clawteam Dev: Review (atelier-fashion/adlc-toolkit, 171 stars), Prompt Generator (catlog22/Claude-Code-Workflow, 2.1k stars), Workflow Review (nabeelhyatt/coworkpowers, 114 stars) and Multi Agent Task Orchestrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
HKUDS (a GitHub organization) maintains it in HKUDS/ClawTeam, which has 5,535 GitHub stars. The repository was last updated on May 9, 2026.
Source: HKUDS/ClawTeam on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.