SKILLEMALL.ai

BD ManualGen

智能业务分析与操作手册生成专家 v6 — 六层递进式骨架生长架构 + 知识图谱编织 + 增量回灌。从界面到模块到区域到功能到按钮到字段,逐层沉淀节点与证据,最终编织成网,输出真正详细的用户操作手册。核心能力:L0骨架→L1模块→L2区域→L3功能→L4操作→L5细节→图谱构建→Snake跨模块链→单版手册。适用:大项目增量生成/追求细致不是概括/需要端到端跨模块流程。不适用:单次简单问答/纯编码任务/只看摘要不看细节。

ClawHub Agent Skills author: songzhou666 v0.1.1 MIT-0 55 files body ≈ 6 319 tokens Open the sourceclawhub.ai analyzed 3 d ago

智能业务分析与操作手册生成专家 v6 — 六层递进式骨架生长架构 + 知识图谱编织 +…

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

ProcedureCustomer supportAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
D
49/100
Unfinished process
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 54. 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")
  • warning body-long SKILL.md body ≈ 6319 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 49/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
  • 30Running it twice. 1 mutating operations with no state check
  • 70Execution cost. Instruction body is 6319 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 74 steps
  • 100Consistency. Name and required fields are in place
  • low 17 top-level sections: this looks like several domains in one skill

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
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 211: enough signal without eating the budget
  • +4Structure: 50 headings
  • +3Step-by-step instructions: 74 items
  • +4Has examples (10 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

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

External checks

ClawHub: suspicious
This skill is not clearly malicious, but it needs review because it can automatically scan a project and persist or modify many files without a clear confirmation step.
LLM: suspicious (high) · 12 Aug 2026