BF WeCom Skill
name: wecom description: "Send messages to WeCom (企业微信) via webhooks using MCP protocol. Works with Claude Code, Claude Desktop, and other MCP clients."
name: wecom description: "Send messages to WeCom (企业微信) via webhooks using MCP protocol.
As a process F 31/100 · Will not run — weak spots: steps, result and completion, when it triggers
IntegrationGitHubAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
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:123High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xCA+ORZv…wO5/ywWF…Tag==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:154High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:226High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MfZ+71RA…HvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:233High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:239High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Zif+qXa4n+oYzK…TZQ/vlgJrCoNQlg==",
detector
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 31/100
- 0Steps. Prose only: no discrete steps
- 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. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (WeCom Skill) differs from the folder (wecom)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 779 tokens
- low The response is described with custom markup (4 tags): a typed call is more reliable
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 14 headings
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.