Menu
Audit locally visible WeCom messages for questions nobody answered, vague commitments, missing owners, and missing deadlines.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Brief one locally visible WeCom chat window: what happened, who owns it, what is missing, and what to ask next.
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-audit |
| description | Audit locally visible WeCom messages for questions nobody answered, vague commitments, missing owners, and missing deadlines. |
Use this skill when the user wants to know what was asked, promised, or left hanging in a WeCom conversation.
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.
Resolve one conversation or a small selected set with conversations.
Read a bounded window with history.
Use search only when the user gives keywords or when checking a known
topic:
sudo wecom-local search "roadmap" --in "Example Group" -n 50 --json
For each possible follow-up item, classify it:
unanswered_question: a question was asked and no answer appears in the
scanned window.vague_commitment: someone agreed but did not specify delivery, owner, or
acceptance.missing_owner: work exists but no responsible person is clear.missing_deadline: owner exists but timing is unclear.conflicting_status: later messages conflict with earlier status.Output: