SKILLEMALL.ai
GitHub ↗ RU Sign in

BD agent-orchestrator

|

ClawHub Agent Skills author: KirkRaman v1.0.2 MIT-0 5 files body ≈ 1 531 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

ProcedureAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
55
Run on models
none yet
Process rating
D
49/100
Unfinished process
When it triggers w 12
0
Failures and branches w 10
0
Running it twice w 4
30
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 3, column 1: name: agent-orchestrator name: agent-orchestrator ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-short description under 40 chars: too little signal for triggering
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/100

  • 0When it triggers. No condition that starts the skill
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 2 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 40Consistency. Frontmatter name (agent-orchestrator) differs from the folder (kirk-agent-orchestrator)
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 39 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1531 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 1: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 39 items
  • +4Has examples (9 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

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

External checks

ClawHub: suspicious
This orchestration skill has a plausible purpose, but it can create and manage agent workspaces and send local or scraped data to a third-party API without clear user-facing consent or scoping.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026