Menú
Brief one locally visible WeCom chat window: what happened, who owns it, what is missing, and what to ask next.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Short Skill name for querying locally visible WeCom Desktop data through the wecom-local CLI on macOS.
Short Skill name for querying locally visible WeCom Desktop data through the wecom-local CLI on macOS.
Short Skill name for querying locally visible WeCom Desktop data through the wecom-local CLI for private knowledge workflows.
Audit locally visible WeCom messages for questions nobody answered, vague commitments, missing owners, and missing deadlines.
Draft the next WeCom message from local chat context without sending it automatically.
Scan selected locally visible WeCom chats for active groups, unfinished work, unanswered questions, and follow-up needs.
| name | wc-brief |
| description | Brief one locally visible WeCom chat window: what happened, who owns it, what is missing, and what to ask next. |
Use this skill when the user wants a straight answer from one WeCom group or chat, without reading the whole thread by hand.
This skill is an analysis wrapper around wecom-local. It must not implement
Runtime Bridge access.
If sudo authorization is needed, 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. If no interactive prompt is available, stop and ask the user
to run the exact local command themselves.
Check readiness when needed:
wecom-local auth status --json
wecom-local auth prepare
wecom-local doctor --json
Resolve the target conversation:
sudo wecom-local conversations --query "Example Group"
If multiple conversations match, stop and ask for a narrower reference or a conversation id from the local result. Do not guess.
Read a bounded window:
sudo wecom-local history "Example Group" -n 200 --format json
sudo wecom-local stats "Example Group" --max-scan 200 --include-members --json
Increase -n / --max-scan only when the user asks for a larger window.
Answer in this shape. Keep it short unless the user asks for a report:
这事卡在哪: the concrete bottleneck.已经说清楚的: decisions, owners, dates, deliverables.还差什么: missing owner, deadline, scope, evidence, or acceptance.下一句怎么问: direct questions the user can send next.风险: only risks supported by the messages..local/wecom-local/ and keep it out of Git.