SKILLEMALL.ai
GitHub ↗ RU Sign in

BC auto-complex-task-planner

自动复杂任务规划器。智能判断任务复杂度，自动创建子 agent 执行，支持优先级队列、任务模板、进度追踪、增强质量审核。 使用场景： - "帮我调研 XXX"（复杂调研任务） - "开发一个 XXX 功能"（开发任务） - "批量处理 XXX"（批量操作） - "生成 XXX 报告/文档"（文档生成） - "紧急！XXX"（高优先级任务） 自动并行执行独立任务，效率提升 80%+。

ClawHub Agent Skills author: sixtysixsone v2.0.0 MIT-0 5 files body ≈ 433 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

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

ProcedureAI 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
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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.
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 description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "chinese_name"
  • note frontmatter-key unknown frontmatter key "created"
  • note frontmatter-key unknown frontmatter key "updated"

Process rating: all ten parameters 53/100

  • 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
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. No external tools needed
  • 100Steps. 31 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 433 tokens
  • 100Running it twice. No mutating operations

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -227 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 192: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 31 items
  • +4Has examples (3 code blocks)

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

External checks

ClawHub: suspicious
The skill appears purpose-aligned, but it automatically delegates broad tasks to sub-agents and stores raw task details without enough user control or privacy disclosure.
LLM: suspicious (high) · VirusTotal: · 29 May 2026