Loading
Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add JimLiu/baoyu-skills --skill baoyu-wechat-summary -a cursor -y
Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory (memory.md) across runs, with privacy guardrails baked in. Use when the user asks to "总结群聊", "群聊精华", "群聊摘要", "summarize group chat", "group chat digest", mentions a WeChat group name with a time range, says "帮我看看 XX 群最近聊了什么", "XX 群有什么值得看的", or asks to "回溯画像" / "初始化画像" / "backfill profiles". Adds the roast version when the user says "毒舌版", "roast 版", "再来个毒舌的", or similar.
Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory (memory.md) across runs, with privacy guardrails baked in. Use when the user asks to "总结群聊", "群聊精华", "群聊摘要", "summarize group chat", "group chat digest", mentions a WeChat group name with a time range, says "帮我看看 XX 群最近聊了什么", "XX 群有什么值得看的", or asks to "回溯画像" / "初始化画像" / "backfill profiles". Adds the roast version when the user says "毒舌版", "roast 版", "再来个毒舌的", or similar.
群聊精华提取专家。把零散的微信群聊记录提炼成结构化、可读性强的简报，并维护跨次运行的群聊历史与群友画像。底层依赖外部 wx-cli 二进制（wx 命令），不打包脚本。
⚠️ Sandbox restriction
wx-cli reads from
~/.wx-cli/(config, cache, daemon socket) and from WeChat's data directory (~/Library/Containers/com.tencent.xinWeChat/on macOS). Both paths are outside Claude Code's default sandbox. Everywxcommand in this skill needs to run withdangerouslyDisableSandbox: truefrom the start — don't waste a sandbox attempt first. The user can use/sandboxto view/edit restrictions.
本文件只保留工作流骨架；细节拆在 references/ 下，执行到对应步骤时再读，不要一开始全部读入：
| 参考文件 | 内容 | 何时读 |
|---|---|---|
| references/setup.md | 环境检查（wx-cli 安装/权限/初始化）、wx-cli 命令速查、排障手册 | 新环境首次运行，或任何 wx 命令失败时 |
| references/output-formats.md | 两版摘要的 Section 顺序、格式与内容规范、输出骨架、自检清单 | Round 2 动笔前 |
| references/profiles.md | 画像文件格式、更新规则、隐私红线、回溯流程 | Step 3.7 / 8.5 / Step 9 |
| references/group-memory.md | 群级事实记忆的写入门槛、防注入、格式 | Step 8.6 |
When this skill prompts the user, follow this tool-selection rule (priority order):
AskUserQuestion, request_user_input, clarify, ask_user, or any equivalent.Concrete AskUserQuestion references below are examples — substitute the local equivalent in other runtimes.
快速验证环境：wx --version 有输出且 wx sessions 返回数据即可继续。任何一步失败，或是首次在新环境运行 → 读 references/setup.md（完整环境检查、wx-cli 命令速查、排障手册），停在第一个失败项并给用户确切的修复命令。绝不自动安装、绝不替用户跑 sudo。
Check EXTEND.md in priority order — the first one found wins:
| Priority | Path | Scope |
|---|---|---|
| 1 | .baoyu-skills/baoyu-wechat-summary/EXTEND.md (relative to project root) | Project |
| 2 | ${XDG_CONFIG_HOME:-$HOME/.config}/baoyu-skills/baoyu-wechat-summary/EXTEND.md | XDG |
| 3 | $HOME/.baoyu-skills/baoyu-wechat-summary/EXTEND.md | User home |
| Result | Action |
|---|---|
| Found | Read, parse, apply. On first use in session, briefly remind: "Using preferences from [path]. Edit it to change defaults." |
| Not found | MUST run first-time setup (BLOCKING) before generating any digest — do NOT silently use defaults. |
EXTEND.md is plain text with key: value or key=value lines, # for comments, case-insensitive keys.
| Key | Type | Default | Purpose |
|---|---|---|---|
self_wxid | string | (required) | The owning account's wxid. Messages whose from_wxid matches this are attributed to the user. |
self_display | string | (required) | Display name to substitute for the user's own messages in digest text. |
default_version | normal / roast / both | normal | Which version(s) to generate when the user doesn't say otherwise. |
default_time_range | string (e.g. 7d, 24h, 1d) | (none) | Default range when the user omits time and there's no incremental anchor. |
data_root | path | {project_root}/wechat | Override where digest folders live. |
bot_aliases | comma-separated strings | bot, 精华bot | Names that trigger the 「@bot 答疑」 section. A message containing @<alias> (case-insensitive) is treated as a question/request aimed at the digest bot. Pick names that do NOT match any real group member or existing bot, to avoid ambiguity. |
A starter template lives at EXTEND.md.example.
If no EXTEND.md is found, do NOT silently proceed.
Step A — Try to auto-discover self_wxid and self_display first. Run (in order, stop at the first that succeeds):
# 1. If wx-cli exposes a whoami, use it
wx whoami --json 2>/dev/null
# 2. Otherwise, find self-sent messages in recent sessions
wx sessions --json --limit 20 2>/dev/null
For option 2, scan the sessions for any private/group thread the user has sent into and read one of their own from_wxid / from_nickname pairs. If you can confidently pre-fill both values, use them as defaults in the question below; otherwise leave the fields blank for the user to fill in.
Step B — Confirm with one AskUserQuestion call (batched), pre-filling whatever auto-discovery found:
self_wxid (e.g., wxid_abc123) — fall-back hint: the user can find it with wx contacts --query "<own nickname>", or by inspecting any of their own sent messages in wx sessions --jsonself_display (e.g., 宝玉) — how they want their messages attributeddefault_version — pick one of normal / roast / bothdata_root — where digest folders live. Default: {project_root}/wechat. Enter a custom absolute path (e.g. ~/Documents/wechat-digests) or leave blank for default.Write EXTEND.md to the chosen path. If the user provided a non-default data_root, include it as an uncommented line; otherwise omit it (the default applies automatically). Confirm "Preferences saved to [path]. Edit it any time to change defaults.", then continue with the digest workflow.
Extract:
history.json for this group, use last_digest.last_message_time as the starthistory.json exists yet, fall back to default_time_range from EXTEND.md if set, else last 24 hours.default_version in EXTEND.md.include_roast=true. Keywords "只要正经的"/"normal only"/"不要毒舌" → force include_normal=true, include_roast=false. "都来一份"/"两个版本都要"/"both" → both.include_normal/include_roast must end up true.Convert relative ranges into absolute --since YYYY-MM-DD --until YYYY-MM-DD pairs using today's local date.
wx contacts --query "<group_name>" --json
Filter for entries whose username ends in @chatroom. If multiple groups match, use AskUserQuestion to disambiguate. If none match, fall back to wx sessions --json and search there before asking the user.
Once resolved, compute the folder path:
{data_root}/{group_id}-{sanitized_group_name}/
where data_root is from EXTEND.md (default {project_root}/wechat).
Sanitize the group name — replace any of / \ : * ? " < > | NUL and control characters with _. Trim trailing dots and whitespace. Don't strip emoji or Chinese characters.
Group-rename detection: list existing folders under {data_root}/ and find any folder whose name starts with {group_id}-. If one exists but the suffix differs (group was renamed), rename the existing folder to the new {group_id}-{sanitized_new_name} form. If a target with the new name already exists (rare), keep both and prefer the existing one for this run.
群主是谁必须有据可查，不能凭历史摘要、群友玩笑或印象推断（群主可能换届，历史摘要里的说法会过期）：
wx members "<group_name_or_id>" --json
Always redirect the fetch to a $TMPDIR file — this file is the single source of truth for the whole run: Round 3's attribution audit greps it, and the statistics are computed from it. Never write the digest purely from conversation memory.
For small batches (single-day digest, typically < 200 messages), you may additionally pipe JSON into the agent directly for reading:
wx history "<group_name_or_id>" --since YYYY-MM-DD --until YYYY-MM-DD -n 5000 --json
For large batches (weekly / monthly digests, > 200 messages), the $TMPDIR redirect also keeps the raw payload out of conversation context:
wx history "<group_name_or_id>" --since YYYY-MM-DD --until YYYY-MM-DD -n 5000 --json > "$TMPDIR/wx-messages.json"
wc -c "$TMPDIR/wx-messages.json"
jq 'length' "$TMPDIR/wx-messages.json"
Then read the file in slices via Read with offset + limit, or process with jq queries (e.g. jq '.[0:200]', jq '[.[] | {id, from_nickname, timestamp, content: (.content | .[0:50])}]' for a lightweight skeleton pass). Reading all 500+ messages at once will burn token budget unnecessarily.
Notes:
--since is inclusive; --until is interpreted as a date (the whole day). If the user asked for "today only", set both to today.-n 5000 is a defensive cap; for very active groups, raise it and re-fetch.timestamp to be safe (some daemons may return adjacent days).Incremental mode: after the fetch, drop any message whose timestamp is <= the last_message_time from history.json, and write the filtered set back to the $TMPDIR file (so audits and stats run on exactly what the digest covers). Caution: last_message_time is MM-DD HH:MM — plain string comparison breaks across a year boundary (12-31 vs 01-01); compare by date semantics there. If zero messages remain, tell the user "上次摘要后没有新消息，已跳过生成" and exit.
wx history --json returns an array of message objects. Use the fields that are present; tolerate missing fields:
id / msg_id / local_id — message identifier (use whichever wx-cli emits). Reference IDs in working notes as anchors when building the skeleton.from_wxid — stable sender identifierfrom_nickname — display name (may be the group remark or original nickname)content — text payload. Examples:
[图片] → opaque placeholder; see image handling below[表情] → emoji/sticker; skip in body unless surrounded by discussion[视频] / [文件] → media reference; skip unless discussed[链接] <title> or [链接/文件] <title> → shared article; the title IS the information — quote it and credit the sharer[系统] ... revokemsg → revoked; exclude from digest and from leaderboardtimestamp — convert to MM-DD HH:MM for display (and use full ISO for generated_at)chat_type — sanity-check groupquote_id, reply_to, quoted_msg_id, or any nested quote object. If present, use it as strong attribution. If absent, fall back to context but flag the inferred link as uncertain.self_display for every message whose from_wxid matches self_wxid (from EXTEND.md). Apply this in the leaderboard, portraits, and body text. The user MUST appear under their real display name and count toward stats — never skip them.nil, null, test, admin, user, undefined), single emoji, or otherwise low-information. For each, run wx contacts --query "<nick>" --json --limit 5 and pick a meaningful name in this priority: remark > nickname > wxid. Apply the substitution everywhere in the digest.nil、空白、单标点这类占位符样式的名字绝不允许原样出现在摘要里。contacts 查不到 remark 时，用「昵称（wxid 后 4 位）」形式区分（如 nil（…n77g）），确保读者知道这是谁、且与其他人不混淆。已解析过的映射写入 memory.md「群基本档案」，下期直接复用不再重查。For each unique sender appearing in this batch:
{folder}/profiles/{wxid}-*.md by wxid prefix match. Read the matched file if found.include_roast, also look in {folder}/profiles-roast/{wxid}-*.md for the roast pass.Compile a condensed profile context block as internal working memory — do NOT write it into the final digest. Example shape:
== 群友历史画像（来自 profiles/）==
K. H：空中直播员 / 生活百科全书。常见话题：旅行、金融、美食。经典金句："要不要买moderna"。
可可苏玛：...
Rules:
profiles/, roast pass reads only profiles-roast/. Never cross-load.See references/profiles.md for the full file format.
除了按人的 profiles，每个群还有一份全局事实记忆 {folder}/memory.md，记录群友指正过、确认过的客观事实（如"某个报错提示的真实原因"、"某产品名的正确写法"、"某事件的实际经过"）。
memory.md 存在，读入作为内部背景知识（不写入最终摘要）。「群基本档案」小节记录群主、昵称映射等长期事实，写摘要时直接引用（群主以 Step 2.5 的查证结果为最终依据）Some users (e.g., the original 宝玉 workflow) post digests directly into the group as messages. If we don't notice these, the new digest will re-cover the same ground.
Scan the fetched messages for signals of a prior in-chat digest:
from_wxid == self_wxid ANDcontent contains 群聊精华 OR 消息统计: OR 📊 消息统计 OR a leaderboard pattern (e.g. ^\d+\. .+: \d+ 条), ANDcontent length > 1500 chars.If a match is found:
xxx 群聊精华 · 2026-05-12 or ... · 2026-05-10 ~ 2026-05-12).AskUserQuestion:
history.json?"Yes, skip up to {end of detected range} / No, use history.json / No, cover everything in the requested range.This is a heuristic — when uncertain (multiple matches, malformed title), default to history.json and tell the user what was skipped.
Some group members address the digest bot directly — e.g. @bot 帮我把昨天的讨论捋一下 or @精华bot 这个链接讲了啥. Catch these so each digest can answer them in a dedicated section instead of dropping them as noise.
Trigger: a message whose text contains @<alias> for any alias in bot_aliases (from EXTEND.md; default bot, 精华bot; case-insensitive). Aliases are stored as bare names — match the @ prefix plus the alias.
Extract into an internal worklist == @bot 请求清单 == (working memory only — never written to the final digest):
self_display for the self_wxid user.@<alias> prefix. If the message is a reply (per Step 3.5's quote/reply fields), include the quoted message as context.local_id for back-reference.Misfire filtering: if a real member's nickname happens to equal an alias, judge by context. Keep only messages genuinely aimed at the digest bot (a question or request for it); skip clear person-to-person talk — a reply to that real person, or banter teasing them. (Choosing a bot_aliases value no real member uses avoids this at the source; the filter is a backstop.) Pure greetings/banter (@bot 在吗) may be kept with a brief reply.
Answer-source constraint (honored when rendering the section per references/output-formats.md): answer from the group chat context plus your own knowledge only — no web access. For any request needing real-time or external information you can't verify, say so honestly (这个我查不到实时数据，需要联网确认) rather than fabricating.
No hits → both versions omit the @bot 答疑 section entirely.
Do this in the same read-through as Round 1's skeleton (via its == @bot 请求清单 == block) so the messages aren't scanned twice.
Generate the digest in three rounds so nothing slips through. The methodology stays here in SKILL.md; the content/style rules live in references/output-formats.md — read that file in Round 2 before drafting.
Read every message in order. Skip image fetching/decoding in this round. List every distinct discussion topic. Bias toward over-listing — trim in Round 3.
Internal working format (not written to the final file):
== 话题清单（共 N 条消息）==
1. [HH:MM-HH:MM] 话题名称（参与者：A, B, C）— 一句话概括（锚点：54052 宝玉:"原话片段" → 54063 鸭哥:"回应片段"）
2. [HH:MM-HH:MM] 话题名称（参与者：D, E）— 一句话概括（锚点 id：54100-54112）
...
== 可能需要图片上下文的话题 ==
- 话题 3：锚点 id=49661（图片是讨论主体）
== 发言统计 ==
1. XXX — N 条 2. YYY — N 条 ...
== @bot 请求清单（如有）==
1. {提问者真名}（锚点 id：54080）— {去掉 @别名的请求正文}（reply 时附被回复内容）
（本期无 @bot 请求则写「无」）
Topic principles:
id 发言人:"原话片段" — sender and quote fragment copied verbatim from the raw messages, not paraphrased. In Round 2, jump back to these anchors and verify content, don't guess from context. If quote_id / reply_to is present, use the ID chain — that's the most reliable attribution. Pinning "who said what" at the skeleton stage is the first line of defense against misattribution (张冠李戴).Flag-for-images criteria (any one triggers): an explicit comment on an image (看发型是X？, 这是谁？, 笑死), multiple people piling onto the same image without saying what it is, an image as the core information (晒单/截图/资料), an explanatory line right after an image (gpt-image-2, 太可怕了), or cross-sender ambiguity (B says "这个看着像 X" but the previous image is from A).
For each topic in the skeleton, jump back to its anchor IDs and expand into full content with quotes and clear attribution. Then write the digest file.
Image handling (limited — wx-cli does not decode chat images):
For each flagged topic, check whether a description file already exists at {folder}/imgs/{message_id}.txt. If yes, read it (one-line plain text) and weave its content into the topic. If no, treat the image as opaque ([图片]) and write around it — describe what the surrounding messages tell us, but don't invent visual content.
The imgs/ directory exists as an extension point: a user (or a future wx-cli capability) can drop {message_id}.txt files with one-line descriptions, and the skill will pick them up. The skill itself does NOT generate these files in this version.
Use the profile context block (from Step 3.7):
Roast pass — profile usage extras (only when generating the roast version):
Writing order: write the body categories first, then the opening overview based on the finished body (so the hook is accurate).
Section order in the output file (fixed): 标题行 → 开头概览（群聊摘要）→ 正文分类（群话题）→ 痛点（可选）→ @bot 答疑（可选）→ 消息统计 + 排行榜 → 群友画像 → 结尾。
Detailed structure, voice, formatting rules, and content guidelines are in references/output-formats.md. Load that file now if not already loaded.
Walk the Round 1 skeleton against the finished digest. Check:
Attribution audit (mandatory — never skip): for every direct quote (text in quotation marks) and every "X 说 / X 发 / X 分享" attribution in the draft, grep the raw $TMPDIR messages file and confirm the words actually came from that sender:
grep "原话片段" "$TMPDIR/wx-messages.json" # or jq 'map(select(.content | contains("原话片段")))'
归因校验：共 N 处引用，通过 X 处，修正 Y 处Fix in place. When clean, confirm and proceed.
If include_normal:
{folder}/YYYY-MM-DD.md{folder}/YYYY-MM-DD_YYYY-MM-DD.mdIf include_roast:
-roast suffix: YYYY-MM-DD-roast.md or YYYY-MM-DD_YYYY-MM-DD-roast.md.Both versions share the same statistics (message count, leaderboard) and the same underlying skeleton.
Maintain two files in the group folder:
history.json — single record, fast readAlways reflects only the most recent normal digest. Overwrite on each run when include_normal=true.
{
"group_id": "12345678901@chatroom",
"group_name": "相亲相爱一家人",
"folder": "12345678901@chatroom-相亲相爱一家人",
"last_digest": {
"file": "2026-03-12.md",
"date_range": "2026-03-12",
"generated_at": "2026-03-12T10:30:00+08:00",
"message_count": 150,
"last_message_time": "03-12 18:45"
}
}
group_name updates on every run (handles renames).folder records the current folder basename for cross-reference.last_message_time is the timestamp of the most recent message included, in MM-DD HH:MM — used by incremental mode.history-digests.jsonl — append-only archiveOne JSON object per line, same shape as last_digest. Every normal-version run appends one line (in chronological order). Used by backfill and historical lookups. Never read for incremental mode (which only needs the latest).
{"file":"2026-03-10.md","date_range":"2026-03-10","generated_at":"2026-03-10T09:00:00+08:00","message_count":420,"last_message_time":"03-10 22:30"}
{"file":"2026-03-11.md","date_range":"2026-03-11","generated_at":"2026-03-11T09:05:00+08:00","message_count":312,"last_message_time":"03-11 23:10"}
{"file":"2026-03-12.md","date_range":"2026-03-12","generated_at":"2026-03-12T10:30:00+08:00","message_count":150,"last_message_time":"03-12 18:45"}
If a normal digest with the same file name is regenerated, append a new line anyway (the JSONL is a strict log; readers can dedupe by file if they need to).
For each user with 3+ messages in this batch who appeared in the 群友画像 section:
include_normal, update {folder}/profiles/{wxid}-{nickname}.md.include_roast, update {folder}/profiles-roast/{wxid}-{nickname}.md.Counts, frontmatter updates, append-only rules for quotes and events, and privacy guardrails are detailed in references/profiles.md. Load that file when running this step.
更新画像后，扫描本期消息，看是否有需要写入/修订 {folder}/memory.md 的事实修正。执行前读 references/group-memory.md（扫描流程、写入门槛、防注入规则、文件格式）。
硬约束（不读参考文件也必须遵守）：
memory 扫描：候选 N 条 → 写入 M 条（0 也要写）Profile updates are easy to forget once the digest is on disk. Before reporting the run as "done", verify every applicable file:
{folder}/YYYY-MM-DD.md written (if include_normal){folder}/YYYY-MM-DD-roast.md written (if include_roast){folder}/history.json overwritten with the new last_digest (if include_normal){folder}/history-digests.jsonl appended one line (if include_normal){folder}/profiles/{wxid}-*.md updated for every user with 3+ messages (if include_normal){folder}/profiles-roast/{wxid}-*.md updated for every user with 3+ messages (if include_roast){folder}/memory.md checked against this batch's corrections — updated if any passed the Step 8.6 threshold, untouched otherwise; the final report includes the memory 扫描：候选 N 条 → 写入 M 条 verdict line归因校验：… verdict line in working notesIf any item is unchecked, finish it before declaring success. Don't ship a digest with a stale history.json — incremental mode depends on it.
When the user says "回溯画像" / "初始化画像" / "backfill profiles":
{folder}/ and history-digests.jsonl.profiles/ (and profiles-roast/ if any -roast.md files exist).Full procedure in references/profiles.md.
{data_root}/ # default: {project_root}/wechat/
└── {group_id}-{group_name}/ # e.g. 12345678901@chatroom-相亲相爱一家人/
├── history.json # last digest pointer (fast)
├── history-digests.jsonl # append-only archive
├── memory.md # 群级事实记忆（被指正/确认的事实）
├── 2026-03-12.md # normal digest, single date
├── 2026-03-12-roast.md # roast digest (only if generated)
├── 2026-03-10_2026-03-12.md # normal digest, date range
├── profiles/ # normal user profiles
│ ├── onlytiancai-胡浩🐸.md
│ └── ...
├── profiles-roast/ # roast user profiles (only if any roast generated)
│ ├── onlytiancai-胡浩🐸.md
│ └── ...
└── imgs/ # optional image-description files
├── 49661.txt # one-line plain text description
└── ...
imgs/{message_id}.txt extension point but does not auto-populate it. When a topic depends heavily on an image with no description file, the digest should say so honestly rather than invent visual content.wx history suddenly returns nothing after a WeChat restart, the keys may be stale. Tell the user to run sudo wx init --force (while WeChat is running) and retry.