CC wecom
Read your WeCom (企业微信 / WeCom / Work Weixin) contacts, send app & group messages, create and read WeDoc docs/smart sheets, and manage schedules (日程) and meetings (会议) via the WeCom server-side API as a self-built app. Use when the user mentions 企业微信, WeCom, 通讯录成员/部门, 应用消息, 群机器人/应用群聊, 企业微信文档/智能表格, 企业微信日程 or 会议, or a qyapi.weixin.qq.com call.
Read your WeCom (企业微信 / WeCom / Work Weixin) contacts, send app & group messages, create and read WeDoc docs/smart sheets, and manage schedules (日程) and…
As a process C 51/100 · Has gaps — References files that are not bundled: ../_shared/wecom.md, ../_shared/wecom.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
exfil-secret-in-urlSKILL.md:56Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)RESP=$(curl -sS "https://qyapi.weixin.qq.com/cgi-bin/gettoken?corpid=…&corpsecret=…")
placeholder -
low Exfiltration
net-credential-useSKILL.md:56Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)RESP=$(curl -sS "https://qyapi.weixin.qq.com/cgi-bin/gettoken?corpid=…&corpsecret=…")
vendor-host
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../_shared/wecom.md - warning
missing-refreference to a missing file: ../_shared/wecom.md - note
frontmatter-keyunknown frontmatter key "connections" - note
frontmatter-keyunknown frontmatter key "allowed_tools"
Process rating: all ten parameters 51/100
- 0Tools and files. 2 referenced file(s) missing: ../_shared/wecom.md, ../_shared/wecom.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 22 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 8 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2886 tokens
- 100Progress reporting. Reports progress
- 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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 342: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (19 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.