BD bitchat
Bitchat integration skill for OpenClaw
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:174High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wIN//F77/IADDSs58i+MDaO…jeo+YFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:440High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Q3k+EAV0…l5Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:508High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…iZ0+mux7…LQp/o3fv…GFA+tGGB…FNf/WwxpYg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:570High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…UfA+m01k/Rtvf…AYx+wV2A…hrw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:589High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…fSo+CahavNft+zty5…2Hl/9mko…QvQ==",
detector
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 344 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 38: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.
External checks
ClawHub: suspicious
This is a coherent Bitchat messaging plugin, but its default open inbound messaging and unauthenticated webhook can let nearby peers or reachable callers inject messages into OpenClaw sessions.
LLM: suspicious (high) · VirusTotal: · 29 May 2026