SKILLEMALL.ai

BC wiki-intent-scope

当用户提供客户需求、研究对象(词条/主题词)、业务意图、政府/企业研究需求、市场进入问题、可行性研究需求、排名/背书目标或政策/咨询报告需求时,用于 Wiki 研究项目的任务与决策场景界定。解析客户自由表述,内部调用 wiki-normalize,识别研究对象、管理问题、研究意图、研究口径、风险和待确认项,并输出聊天摘要、人类可读的 scope.md 与机器可读的 scope.json。

ClawHub Agent Skills author: Leadleo v1.0.0 MIT-0 6 files body ≈ 969 tokens Open the sourceclawhub.ai analyzed 35 h ago

当用户提供客户需求、研究对象(词条/主题词)、业务意图、政府/企业研究需求、市场进入问题、可行性研究需求、排名/背书目标或政策/咨询报告需求时,用于 Wiki 研究项目的任务与决策场景界定。解析客户自由表述,内部调用…

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

Proceduretype and topics are labelled automatically from the skill text
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: 6. 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")

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. 70 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 969 tokens
  • 100Running it twice. No mutating operations
  • low 14 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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 195: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 70 items
  • +4Reference files are cited in the instructions (2 of 2)

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

External checks

ClawHub: clean
This appears to be a prompt-only research scoping helper with a broad trigger, but no evidence of malware, hidden execution, credential use, persistence, or data-changing behavior.
LLM: benign (medium) · VirusTotal: · 10 Jul 2026