SKILLEMALL.ai

BF skill2team

Design profile-based agent teams from skills, workflows, prompts, tools, or briefs.

ClawHub Agent Skills author: c-narcissus v1.9.2 MIT-0 80 files body ≈ 3 197 tokens Open the sourceclawhub.ai analyzed 2 d ago

Design profile-based agent teams from skills, workflows, prompts, tools, or briefs.

As a process F 45/100 · Will not run — References files that are not bundled: assets/prompt-templates/, scripts/validate_package.py

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
F
45/100
Will not run
References files that are not bundled: assets/prompt-templates/, scripts/validate_package.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/validate_package.py

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: assets/prompt-templates/, scripts/validate_package.py
  • 0Tools and files. 2 referenced file(s) missing: assets/prompt-templates/, scripts/validate_package.py
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 100Steps. 14 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3197 tokens
  • 100Progress reporting. Reports progress

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 83: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 14 items
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (22 of 37)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.

External checks

ClawHub: clean
Skill2Team is a disclosed agent-team design and Codex packaging skill whose configuration changes are expected for its purpose and guarded by manifests and smoke-test requirements.
LLM: benign (high) · VirusTotal: · 28 Jun 2026