| name | wc-local |
| description | Short Skill name for querying locally visible WeCom Desktop data through the wecom-local CLI for private knowledge workflows. |
wc-local for Hermes
Use this skill to query locally visible WeCom Desktop conversations for private
archive material and downstream analysis.
The Skill name is short. The binary is still wecom-local.
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.
Use an interactive system prompt in the same terminal/TTY that will run the
query. Do not ask the user to paste their macOS password into chat, prompt
text, an env var, a file, or an askpass script. If no interactive prompt is
available, stop and ask the user to run the exact local command themselves.
Commands
Check the local environment:
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
Discover conversations:
sudo wecom-local conversations
sudo wecom-local conversations --query "example"
Read a conversation by id or unique display-name query:
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
Write 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.
Knowledge Boundary
The CLI queries data already visible to the signed-in WeCom Desktop account.
Hermes ingestion should preserve local privacy boundaries and avoid syncing raw
chat exports, real conversation ids, group names, contact names, keys, or
decrypted databases to public repositories.