wc-local

name	wc-local
description	Short Skill name for querying locally visible WeCom Desktop data through the wecom-local CLI on macOS.

wc-local

Use this skill when the user asks to inspect, query, search, summarize, or analyze locally visible WeCom Desktop data.

The Skill name is short. The binary is still wecom-local.

Prerequisites

• macOS.
• WeCom Desktop is installed, running, and signed in.
• wecom-local is built or installed.
• Runtime access usually needs sudo because it attaches to the local WeCom Desktop process.

Authorization UX

sudo timestamps can be scoped to the current terminal or TTY. If the user ran wecom-local auth prepare in a separate Terminal app, the Agent command session may still need authorization.

Preferred flow:

1. Run wecom-local auth status --json.
2. If authorization is needed, run wecom-local auth prepare or the target sudo wecom-local ... command only in an interactive terminal where the user can type the password or use Touch ID directly into the system prompt.
3. If no interactive terminal is available, stop and ask the user to run the exact local command themselves.

Never ask the user to paste their macOS password into chat, prompt text, an env var, a file, or an askpass script. The CLI does not store passwords.

Commands

Check readiness:

wecom-local auth status --json
wecom-local auth prepare
wecom-local doctor --json

Probe local store shape without reading row values:

wecom-local store-probe --json

List conversations:

sudo wecom-local conversations
sudo wecom-local conversations --query "example"

Read a conversation by id or unique display-name query as JSON:

sudo wecom-local history "R:0000000000" -n 100 --format json
sudo wecom-local history "Example Group" -n 100 --format json

Search decoded messages in one conversation:

sudo wecom-local search "roadmap" --in "Example Group" -n 20 --json

List members in one conversation:

sudo wecom-local members "Example Group" --format json
sudo wecom-local members "Example Group" --full --format json

Use default members first. Use --full only when the user explicitly needs locally visible account, email, phone, or external id fields.

Summarize one conversation:

sudo wecom-local stats "Example Group" --max-scan 1000 --json
sudo wecom-local stats "Example Group" --max-scan 1000 --include-members --json

Export to Markdown:

sudo wecom-local export "Example Group" \
  --format markdown \
  --output ./.local/wecom-local/conversation.md

If a display-name query is ambiguous, run conversations --query and retry with a narrower query or the returned conversation id.

Short Analysis Skills

Use the other wc-* skills for higher-level work:

• wc-brief: one conversation brief.
• wc-scan: selected conversations work scan.
• wc-audit: unanswered questions and follow-up gaps.
• wc-style: local evidence-based collaboration profile.
• wc-draft: next-message draft without sending.

These skills still call wecom-local. They do not implement Runtime Bridge access or read local databases directly.

Safety

Only query data the signed-in user can already view locally. Do not paste raw chat contents, real conversation ids, group names, contact names, keys, or exported files into public issues, README examples, or commits.