clawteam-dev

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured development reference with copy-paste commands and clean one-level-deep references to real bundle scripts. Its main weaknesses are minor verbose restatements and the absence of explicit validate-fix-retry feedback loops for its validation workflows.

Suggestions

Remove the redundant 'This script lives in `scripts/...` inside this skill folder' lines since the preceding command already shows the path, or merge them into the code-block caption to tighten conciseness.

Add an explicit feedback loop for the validation workflow, e.g. 'If `pytest` or `task wait` fails, read the failure, fix the change, and re-run the same targeted command before escalating to broader tests.'

Make the validation escalation a single ordered checklist with explicit gates (ruff -> targeted pytest -> broad pytest -> smoke -> harness) so the sequence and its checkpoints are unambiguous rather than spread across sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and tight bullets, but includes mildly redundant restatements such as 'This script lives in `scripts/...` inside this skill folder' (path already shown in the command) and several 'Use this when ...' framing sentences that restate each section's purpose; it fits 'mostly efficient but could be tightened' rather than the 'every token earns its place' anchor at 3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands throughout (e.g. `bash scripts/bootstrap_clawteam_dev.sh`, `ruff check clawteam/ tests/`, `clawteam team spawn-team dev-smoke ...`, `clawteam task wait dev-smoke --timeout 300`), matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear escalation sequence is present (targeted ruff/pytest -> broader pytest -> smoke test -> harness) with some verification commands (`clawteam --version`, `clawteam board show`, `clawteam task wait --timeout`), but explicit error-recovery feedback loops (validate -> fix -> re-run) are not spelled out and the structure is a command reference rather than a single gated workflow, fitting the 'sequence present but checkpoints implicit' anchor better than the full feedback-loop/checklist anchor at 3.	2 / 3
Progressive Disclosure	Well-organized into clear sections that reference two real one-level-deep bundle scripts (`scripts/bootstrap_clawteam_dev.sh`, `scripts/link_local_clawteam_skills.sh`) with explicit, signaled paths; no nested references and content is appropriately split between the overview and the executable scripts, matching the 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description with an explicit 'Use this skill when' trigger, multiple concrete actions, and a clear niche that minimizes conflict risk. Voice is appropriately third-person/imperative with no first/second-person penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'local development, debugging, reviewing, testing, validating multi-agent flows' and 'standardize the local `clawteam` command' / 'wire project-local `.agents` and `.claude` skills', matching the 'lists multiple specific concrete actions' anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Clearly answers both 'what' (bootstrap scripts, wire local skills) and 'when' via the explicit 'Use this skill when ...' clause, satisfying the 'what AND when with explicit triggers' anchor rather than the 'when implied only' anchor at 2.	3 / 3
Trigger Term Quality	Explicit 'Use this skill when working inside the ClawTeam repository itself' followed by natural developer triggers ('debugging, reviewing, testing, validating multi-agent flows, checking whether a code change actually works end-to-end') gives good coverage of terms a user would actually say; not reduced to 2 because it goes beyond a single keyword.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'working inside the ClawTeam repository itself' and explicitly 'not a general end-user usage guide', giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: win4r/ClawTeam-OpenClaw
Path: .agents/skills/clawteam-dev/SKILL.md
Commit: 8dac3fc

Reviewed: about 15 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.