BD wecom-deep-op
基于微信官方插件 @wecom/wecom-openclaw-plugin v1.0.13+,封装的一站式企业微信自动化解决方案 - 你可以方便操作文档、日历、会议、待办、通讯录所有企业微信MCP能力,充分发挥OpenClaw与企业微信的协同能力。
As a process D 46/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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:83High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…VHO+q2xB…AGd+Kl0mmq/MprG…MzA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:127High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…VHO+q2xB…AGd+Kl0mmq/MprG…MzA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:304High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…ywo+qwL+oL8H…C1U+vRfLQDvw==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:320High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-Yqfm+XDx0+Prh3…1yC+JWZ2…IL7+vK+Clp7…D7g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:333High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xZl+RoGR…fbT/ZgrF…0EA==",
detector -
low Exfiltration
exfil-secret-in-urlSKILL.md:383Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"baseUrl": "https://qyapi.weixin.qq.com/mcp/bot/combined?uaKey=…"
placeholder
Files scanned: 30. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 46/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
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 100Steps. 49 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2112 tokens
- 100Running it twice. No mutating operations
- low 13 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
- -236 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 124: enough signal without eating the budget
- +4Structure: 57 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (34 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
This appears to be a legitimate WeCom automation skill, but it should be reviewed carefully because it can read, edit, cancel, and delete real enterprise data using a bot credential without built-in confirmation safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026