wecom SKILL.md skillA
wecom from acedatacloud/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add acedatacloud/skills/wecom@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- acedatacloud/skills
- Path
skills/wecom/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Jul 3, 2026
- Size
- 12,840 bytes
- Repository stars
- 17
- License
- a license file GitHub does not identify
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
We drive the [WeCom server-side API](https://developer.work.weixin.qq.com/document/path/90664) (`https://qyapi.weixin.qq.com`) with `curl + jq` as a **self-built app (自建应用)**. > **Setup:** see [WeCom authentication](../_shared/wecom.md) for how to create the self-built app, > collect **CorpID / Secret / AgentId**, and grant it the contacts / docs / calendar / meeting > permissions. The skill reads `WECOM_CORP_ID`, `WECOM_CORP_SECRET` and `WECOM_AGENT_ID` from the > environment; on AceDataCloud they are injected automatically by the 企业微信 connector. WeCom uses a two-step token flow (identical in shape to the WeChat MP API): 1. Exchange `CorpID + Secret` for an `access_token` (TTL 7200s). 2. Pass that `access_token` as a **query string parameter** on every other call. **Never log or echo `$WECOM_CORP_SECRET`** — treat it like a password. Responses are JSON returned with **HTTP 200**; `errcode == 0` means success. On any non-zero `errcode`, show the original `errmsg` to the user verbatim (see the error table in [the setup doc](../_shared/wecom.md#response-shape--error-handling)). ## Recipes ### Step 0 — get an access_token (do this first, cache the result) …
Read the whole file at its exact version.
How to install
mdr add acedatacloud/skills/wecom@sha256:70f835eed3d9dd05The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_oqqly43lwuq34msg)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12840 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
acedatacloud/skills · 17 stars · license a license file GitHub does not identify · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oqqly43lwuq34msg GET https://markdownregistry.com/api/v1/resolve?ref=acedatacloud/skills/wecom GET https://markdownregistry.com/api/v1/blob/70f835eed3d9dd0509a431412ae85c5c3d70bca395537a686391c88cc384a356
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.