CC teams-setup
Creates and manages dynamic teams of domain agents. Triggers: create team, agent team, team status, cleanup team.
Creates and manages dynamic teams of domain agents.
As a process C 52/100 · Has gaps — weak spots: steps, result and completion, running it twice
GeneratorAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: teams-setup (kochetkov-ma/claude-brewcode)
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-eval-dynamicscripts/prepare-tokenizer.py:921Dynamic code execution from decoded/untrusted input (detector / deny-list definition)exec(compile(sys.stdin.read(), '<stdin>', 'exec'), {'__name__': '__main__'})detector -
low Dangerous commands
cmd-eval-dynamicscripts/prepare-tokenizer.py:925Dynamic code execution from decoded/untrusted input (detector / deny-list definition)exec(compile(code, '<string>', 'exec'), {'__name__': '__main__'})detector
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
edit-residuethe text marks something as outdated (lines 46, 48, 60): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 30Running it twice. 12 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2874 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 113: 120–800 characters recommended
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 9 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 16 headings
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.