CA 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 A 87/100 · Runs to the end — weak spots: when it triggers, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Glob Grep Bash Agent AskUserQuestion Skill
-
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: 19. 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") - warning
body-longSKILL.md body ≈ 6569 tokens (recommended < 5000); move details to references/ - note
edit-residuethe text marks something as outdated (lines 82, 84, 85, 187, 203, 310): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 87/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 6569 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 27 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (21 tags): a typed call is more reliable
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
- -31 of 9 scripts are never mentioned in SKILL.md
- +4Structure: 20 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.