SKILLEMALL.ai
GitHub ↗ RU Sign in

BF skill-orchestrator

技能总指挥 — 全司Skill统一调度/优化/管理/发布系统。优化（触发达尔文进化）、调度（任务→最佳Skill匹配+链式编排）、管理（清单/健康/版本/审计）、发布（安全扫描→GitHub/ClawHub）

ClawHub Agent Skills author: dxy0905 v1.0.0 MIT-0 2 files body ≈ 1 642 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

技能总指挥 — 全司Skill统一调度/优化/管理/发布系统。优化（触发达尔文进化）、调度（任务→最佳Skill匹配+链式编排）、管理（清单/健康/版本/审计）、发布（安全扫描→GitHub/ClawHub）

As a process F 30/100 · Will not run — References files that are not bundled: references/publishing-workflow.md

ProcedureGitHubAI and agentstype 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
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
63
Run on models
none yet
Process rating
F
30/100
Will not run
References files that are not bundled: references/publishing-workflow.md
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: 2. 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: references/publishing-workflow.md

Process rating: all ten parameters 30/100

Will not run. References files that are not bundled: references/publishing-workflow.md
  • 0Tools and files. 1 referenced file(s) missing: references/publishing-workflow.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (skill-orchestrator) differs from the folder (skill-orchestrator-qszf)
  • 100Steps. 27 steps
  • 100Execution cost. Instruction body is 1642 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 104: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 28 headings
  • +3Step-by-step instructions: 27 items
  • +4Has examples (11 code blocks)

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

External checks

ClawHub: suspicious
This skill mostly matches its skill-management purpose, but it explicitly teaches bypassing token redaction for a GitHub PAT and includes persistent auto-load guidance, so it should be reviewed before installation.
LLM: suspicious (high) · VirusTotal: · 5 Jun 2026