← Search

WeCom meeting manager
Productivity 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit c4b9b66
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: a logged-in WeCom enterprise account…

WeCom meeting manager

Create, search, update and cancel WeCom online meetings, fetch transcripts and meeting minutes/todos

At a glance
What
Create, search, update and cancel WeCom online meetings, fetch transcripts and meeting minutes/todos
Cost
Free
Needs
a logged-in WeCom enterprise account, the wecom-cli binary on PATH; note the skill is written in Chinese and its fixed disambiguation phrasing must be used verbatim
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

WeCom Meeting is a free Muse skill that manages the WeCom online-meeting lifecycle: creating, listing, searching, updating and canceling meetings with a join link, via the wecom-cli CLI. It fetches the raw verbatim transcript page by page, versus the AI-generated notes, minutes and todos, with strict operation reference docs for each operation.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit c4b9b66

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a logged-in WeCom enterprise account, the wecom-cli binary on PATH; note the skill is written in Chinese and its fixed disambiguation phrasing must be used verbatim Install "WeCom meeting manager" for me. Give my agent the wecomcli-meeting contract from wecomteam's repo: create/list/get/search/cancel/update meetings via wecom-cli meeting [action] --json with per-operation reference docs read before executing, free/busy checks before create/update, meeting-room lookup via the wecomcli-calendar skill, name-to-userid resolution via wecomcli-contact, fetch raw transcripts via meeting original get (page to the end) vs AI notes/todos via meeting get, the meeting-vs-calendar disambiguation rules, and the output format standards (no meeting codes or join links shown) Repository: https://raw.githubusercontent.com/wecomteam/wecom-cli/c4b9b6610c7ca2854441bfa336a5b458daeeb707/skills/wecomcli-meeting/SKILL.md Pinned version: install the code at commit c4b9b6610c7ca2854441bfa336a5b458daeeb707 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "wecomteam-wecom-cli-wecomcli-meeting". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. log in to my WeCom account and install the wecom-cli binary before creating any meetings). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit c4b9b66 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : registry.npmjs.org
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
c4b9b66 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.