DC wecom-agent-ops-center
企微 AI Agent 可观测性工具 — 心跳监控、进程守护、敏感信息扫描、网络白名单,2 分钟接入
企微 AI Agent 可观测性工具 — 心跳监控、进程守护、敏感信息扫描、网络白名单,2 分钟接入
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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".
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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 18
✓ No critical or high findings
Medium and low: 18
-
medium Exfiltration
net-redirectable-api-keyconfig.js:44Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-redirectable-api-keyconnector.js:55Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Secrets in code
secret-private-keycore/secrets-scanner.js:111Private key material (detector / deny-list definition; key header without key body)pattern: /-----BEGIN PRIVATE KEY----- …/g,
detectorheader only -
medium Secrets in code
secret-private-keycore/secrets-scanner.js:117Private key material (detector / deny-list definition; key header without key body)pattern: /-----BEGIN PRIVATE KEY----- …/g,
detectorheader only -
medium Secrets in code
secret-private-keycore/secrets-scanner.js:123Private key material (detector / deny-list definition; key header without key body)pattern: /-----BEGIN PRIVATE KEY----- …/g,
detectorheader only -
medium Exfiltration
net-redirectable-api-keymsg-converter.js:20Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-redirectable-api-keytest-msg-converter.js:7Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
low Dangerous commands
cmd-privilegedeploy-pairing-server.sh:18Privilege escalation / world-writable permissions (string literal in code, not executed)ssh $SERVER "sudo mkdir -p $REMOTE_DIR && sudo chown ubuntu:ubuntu $REMOTE_DIR"
code literal -
low Dangerous commands
cmd-privilegedeploy-pairing-server.sh:30Privilege escalation / world-writable permissions (string literal in code, not executed)ssh $SERVER "sudo tee /etc/systemd/system/pairing-server.service > /dev/null << 'EOF'
code literal -
low Dangerous commands
cmd-background-processdeploy-pairing-server.sh:48Starts a background / autostarted processsudo systemctl daemon-reload && sudo systemctl enable pairing-server && sudo systemctl restart pairing-server"
-
low Dangerous commands
cmd-background-processdeploy-v2.4.0.sh:63Starts a background / autostarted processnohup node connector.js > logs/connector.log 2>&1 &
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:43High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:74High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:86High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:126High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…FrF+LTRo…W3g==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:135High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
quoted -
low Dangerous commands
cmd-background-processREADME.md:83Starts a background / autostarted processsudo systemctl enable --now wecom-agent-ops-center
-
low Dangerous commands
cmd-background-processSKILL.md:99Starts a background / autostarted processsudo systemctl enable --now wecom-agent-ops-center
Files scanned: 55. 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 "display_name" - note
frontmatter-keyunknown frontmatter key "homepage"
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. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 934 tokens
- 100Running it twice. No mutating operations
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 50: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 15 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.