SKILLEMALL.ai

BC Multi-Agent Deployment Skill for OpenClaw

Deploy a production-ready multi-agent fleet in OpenClaw. Includes step-by-step setup guide, workspace templates, and Python automation scripts for agent creation, routing config, memory sync, and cloud deployment — based on a real working 4-agent production setup.

ClawHub Agent Skills author: abhinas90 v1.0.2 MIT-0 7 files · 1 script body ≈ 879 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

TemplateInfrastructureAI 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%
66
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
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.
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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"

Process rating: all ten parameters 59/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 40Consistency. Frontmatter name (Multi-Agent Deployment Skill for OpenClaw) differs from the folder (multi-agent-deployment)
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 21 steps
  • 100Execution cost. Instruction body is 879 tokens

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 264: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (6 code blocks)

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

External checks

ClawHub: suspicious
This skill appears purpose-aligned, but it can overwrite OpenClaw configuration and agent memory files and restart a remote VPS container without strong safety controls.
LLM: suspicious (medium) · VirusTotal: · 31 May 2026