SKILLEMALL.ai
GitHub ↗ RU Sign in

BD bug-pattern-diagnosis

根据用户描述的 bug 现象（症状）匹配已沉淀的 bug 案例库，快速判断这是哪类问题、根因在哪、如何排查。每次成功诊断后会把新案例沉淀到案例库，持续积累经验。适用于用户报告"奇怪的报错 / 间歇性失败 / 某些环境才复现 / 日志很诡异"的场景。

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

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

AnalyzerInfrastructuretype 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
78/100
safety, quality, tests
Safety 60%
82
Quality 40%
72
Run on models
none yet
Process rating
D
43/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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

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 · 6

✓ No critical or high findings

Medium and low: 6
  • medium Exfiltration net-credential-use experience/BUG01.md:171
    Credential used in a network call (verify the destination is the intended service)
    curl -s -X POST "$URL" -H "Authorization: $TOKEN" -d "$BODY" \
  • medium Exfiltration net-credential-use experience/BUG03.md:418
    Credential used in a network call (verify the destination is the intended service)
    curl -H "Authorization: Bearer $TOKEN" \
  • medium Exfiltration net-credential-use experience/BUG04.md:441
    Credential used in a network call (verify the destination is the intended service)
    curl -H "Authorization: Bearer $TOKEN" \
  • low Obfuscation obf-base64-blob experience/BUG02.md:156
    Long base64-looking blob (quoted — discussed, not commanded)
    `cuavcloudservice/CuavCloudApplyService/CuavCloudTestService/src/main/java/com/cuav/cloud/test/application/sfl210/Sfl2…ava`
    quoted
  • low Obfuscation obf-base64-blob experience/BUG02.md:334
    Long base64-looking blob (quoted — discussed, not commanded)
    - 高压发送样例 1：`cuavcloudservice/CuavCloudApplyService/CuavCloudTestService/src/main/java/com/cuav/cloud/test/application/sfl210/Sfl2…ava`
    quoted
  • low Obfuscation obf-base64-blob experience/BUG02.md:336
    Long base64-looking blob (security demo / example; quoted — discussed, not commanded)
    - 重消息示例：`cuavcloudcbb/CuavCloudBasicCBB/InterfaceDefineCBB/src/main/java/com/cuav/cloud/protobuf/model/Dph1…ava`
    demoquoted

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 43/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
  • 60Tools and files. Uses tools (git) that frontmatter does not declare
  • 100Steps. 65 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1573 tokens
  • low 10 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 124: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 65 items
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: clean
This is a markdown-only bug-diagnosis skill with relevant case notes and no hidden installer, automatic execution, or exfiltration behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026