mirror of
https://github.com/JimLiu/baoyu-skills.git
synced 2026-08-08 09:53:02 +08:00
更新 baoyu-wechat-summary 技能：调整输出顺序并拆分环境/群记忆参考文件
This commit is contained in:
Jim Liu 宝玉
@@ -1,6 +1,6 @@
|
||||
# Output formats — normal & roast digest
|
||||
|
||||
This reference defines the two digest variants the skill produces: the **normal** version (default, sober summary) and the **roast** version (毒舌，sarcastic critique, opt-in). Load this file during Step 4 (skeleton) and keep it open through Step 6 (audit).
|
||||
This reference defines the two digest variants the skill produces: the **normal** version (default, sober summary) and the **roast** version (毒舌，sarcastic critique, opt-in). Load this file during Round 1 (skeleton) and keep it open through Round 3 (audit).
|
||||
|
||||
Both versions share the same overall layout and writing rules; the differences are tone, the leaderboard annotations, the portraits, and the footer. Write the normal version first when both are requested — it's the anchor for incremental mode and the source of truth for the profile updates.
|
||||
|
||||
@@ -8,19 +8,21 @@ Both versions share the same overall layout and writing rules; the differences a
|
||||
|
||||
## 1. Normal version
|
||||
|
||||
### 1.1 Five-part structure
|
||||
### 1.1 Section order (fixed)
|
||||
|
||||
```
|
||||
[Title line]
|
||||
[📊 Stats block + Top 10 leaderboard]
|
||||
[Opening summary — 1-2 paragraphs of prose]
|
||||
[群友画像 — one entry per active user (3+ msgs)]
|
||||
[Categorized body — 3-6 self-named sections per day]
|
||||
[Optional pain-point section]
|
||||
[Optional @bot Q&A section]
|
||||
[① Opening summary — 1-2 paragraphs of prose]
|
||||
[② Categorized body — 3-6 self-named sections per day]
|
||||
[③ Optional pain-point section]
|
||||
[④ Optional @bot Q&A section]
|
||||
[⑤ 📊 Stats block + Top 10 leaderboard]
|
||||
[⑥ 群友画像 — one entry per active user (3+ msgs)]
|
||||
[Fixed footer]
|
||||
```
|
||||
|
||||
摘要在前、话题居中、排行榜和画像收尾 — 读者先看到内容，数据和人物放在后面翻阅。
|
||||
|
||||
### 1.2 Title line
|
||||
|
||||
- Single line, no markdown heading.
|
||||
@@ -33,7 +35,66 @@ Example:
|
||||
相亲相爱一家人 群聊精华 · 2026-03-12
|
||||
```
|
||||
|
||||
### 1.3 Statistics block
|
||||
### 1.3 Opening summary（群聊摘要）
|
||||
|
||||
- Comes immediately after the title line.
|
||||
- 1-2 paragraphs, plain prose, no headings, no bullets.
|
||||
- Hook the reader: lead with the most distinctive thread of the day (a heated debate, a surprising announcement, a market move someone reacted to).
|
||||
- Reference 2-4 of the day's category titles in the prose so the reader knows what's coming.
|
||||
- Mention 1-2 specific people only if their contribution is central; otherwise stay topic-focused.
|
||||
- No timestamps, no message counts (those live in the stats block).
|
||||
|
||||
### 1.4 Categorized body（群话题）
|
||||
|
||||
- 3-6 self-named categories per day.
|
||||
- Each category is a thematic bucket — name it for the *topic*, not generic ("讨论"、"闲聊" are forbidden labels).
|
||||
- Category header: `{emoji} {标题}` — one emoji prefix, then a short noun phrase.
|
||||
- Suggested emoji: 🛠 工具/技术，📦 产品发布，📰 新闻/市场，💬 观点辩论，😄 笑料/段子，📚 学习分享，💸 钱与消费，🍜 生活日常。
|
||||
- Body inside each category: prose with embedded quotes. Use `•` bullets when listing 3+ parallel items; otherwise paragraphs.
|
||||
- Attribution: name the speaker on first mention in a thread (`蛙总说他...`). For follow-on lines in the same thread, attribution can be implicit if the chain is short and clear.
|
||||
- Quotes: use 「」 for direct quotes. Quote when the wording is vivid, surprising, or characteristic; paraphrase otherwise.
|
||||
- Merge: a multi-person discussion is one entry, not a list of one-line replies.
|
||||
- Links: preserve the full URL inline. Article titles stay verbatim.
|
||||
|
||||
Example:
|
||||
|
||||
```
|
||||
🛠 Claude Code 4.7 实测
|
||||
|
||||
蛙总下午把 4.7 装上后第一反应是「比 4.6 慢一倍」，老王跟着复现，怀疑是 Opus 默认配置导致。阿喵贴了官方文档 https://docs.claude.com/.../opus-4-7 ，提到可以切回 Sonnet 4.6 跑速测，三人最终结论：复杂任务 4.7 强，日常用 4.6 更顺手。
|
||||
```
|
||||
|
||||
### 1.5 Pain-point section (optional)
|
||||
|
||||
- Include only when the day's chat contains at least one concrete unresolved or partially-resolved problem.
|
||||
- Heading: `今日待解决问题` or `本周悬而未决`.
|
||||
- One entry per problem. Format:
|
||||
```
|
||||
问题：<一句话描述>
|
||||
提出者：<昵称>
|
||||
背景：<1-2 句来龙去脉>
|
||||
状态：<✅ 已解决 / ⚠️ 部分解决 / ❌ 仍未解决>
|
||||
方案：<若有人提了方案，写在这；否则写"暂无方案">
|
||||
```
|
||||
- Skip the section entirely if there are no genuine pain points — don't pad with trivial questions.
|
||||
|
||||
### 1.6 @bot 答疑 section (optional)
|
||||
|
||||
- 仅当 SKILL.md Step 3.9 本批捕获到至少一条真实 @bot 请求时出现；否则整段省略。
|
||||
- Heading: `🤖 @bot 答疑`
|
||||
- 一条请求一个条目（• 请求行 + 缩进的 🤖 答复行）。多人问同一件事合并成一答。
|
||||
- **请求行措辞自由发挥**：点出提问者真名 + 自然转述其请求即可，别套「X 问：」这类固定句式。
|
||||
- 语气：真诚、热心、有用的助手——与普通版整体一致。答复落地、给具体建议，别空泛。
|
||||
- 来源：仅群聊上下文 + 自有知识，不联网。需实时/外部数据又无法核实的，如实说明（`这个我查不到实时数据，需要联网确认`），不编造。
|
||||
- Format（遵守 §3：不用 markdown、列表用 •、标题一个 emoji）：
|
||||
```
|
||||
🤖 @bot 答疑
|
||||
|
||||
• {提问者 + 自然转述的请求}
|
||||
🤖 {真诚、简洁、有用的回答；查不到实时信息就如实说明}
|
||||
```
|
||||
|
||||
### 1.7 Statistics block（消息统计 + 排行榜）
|
||||
|
||||
- Starts with `📊 消息统计: 共 N 条消息`.
|
||||
- Followed by a leaderboard, top 10 senders by message count, one per line.
|
||||
@@ -56,15 +117,7 @@ Example:
|
||||
...
|
||||
```
|
||||
|
||||
### 1.4 Opening summary
|
||||
|
||||
- 1-2 paragraphs, plain prose, no headings, no bullets.
|
||||
- Hook the reader: lead with the most distinctive thread of the day (a heated debate, a surprising announcement, a market move someone reacted to).
|
||||
- Reference 2-4 of the day's category titles in the prose so the reader knows what's coming.
|
||||
- Mention 1-2 specific people only if their contribution is central; otherwise stay topic-focused.
|
||||
- No timestamps, no message counts (those live in the stats block).
|
||||
|
||||
### 1.5 群友画像 section
|
||||
### 1.8 群友画像 section
|
||||
|
||||
- Heading line: `群友画像`
|
||||
- One entry per user with 3+ messages this batch.
|
||||
@@ -85,56 +138,6 @@ Example:
|
||||
• 临近收盘转为沉默，与昨日大放厥词的状态对比明显
|
||||
```
|
||||
|
||||
### 1.6 Categorized body
|
||||
|
||||
- 3-6 self-named categories per day.
|
||||
- Each category is a thematic bucket — name it for the *topic*, not generic ("讨论"、"闲聊" are forbidden labels).
|
||||
- Category header: `{emoji} {标题}` — one emoji prefix, then a short noun phrase.
|
||||
- Suggested emoji: 🛠 工具/技术，📦 产品发布，📰 新闻/市场，💬 观点辩论，😄 笑料/段子，📚 学习分享，💸 钱与消费，🍜 生活日常。
|
||||
- Body inside each category: prose with embedded quotes. Use `•` bullets when listing 3+ parallel items; otherwise paragraphs.
|
||||
- Attribution: name the speaker on first mention in a thread (`蛙总说他...`). For follow-on lines in the same thread, attribution can be implicit if the chain is short and clear.
|
||||
- Quotes: use 「」 for direct quotes. Quote when the wording is vivid, surprising, or characteristic; paraphrase otherwise.
|
||||
- Merge: a multi-person discussion is one entry, not a list of one-line replies.
|
||||
- Links: preserve the full URL inline. Article titles stay verbatim.
|
||||
|
||||
Example:
|
||||
|
||||
```
|
||||
🛠 Claude Code 4.7 实测
|
||||
|
||||
蛙总下午把 4.7 装上后第一反应是「比 4.6 慢一倍」，老王跟着复现，怀疑是 Opus 默认配置导致。阿喵贴了官方文档 https://docs.claude.com/.../opus-4-7 ，提到可以切回 Sonnet 4.6 跑速测，三人最终结论：复杂任务 4.7 强，日常用 4.6 更顺手。
|
||||
```
|
||||
|
||||
### 1.7 Pain-point section (optional)
|
||||
|
||||
- Include only when the day's chat contains at least one concrete unresolved or partially-resolved problem.
|
||||
- Heading: `今日待解决问题` or `本周悬而未决`.
|
||||
- One entry per problem. Format:
|
||||
```
|
||||
问题：<一句话描述>
|
||||
提出者：<昵称>
|
||||
背景：<1-2 句来龙去脉>
|
||||
状态：<✅ 已解决 / ⚠️ 部分解决 / ❌ 仍未解决>
|
||||
方案：<若有人提了方案，写在这；否则写"暂无方案">
|
||||
```
|
||||
- Skip the section entirely if there are no genuine pain points — don't pad with trivial questions.
|
||||
|
||||
### 1.8 @bot 答疑 section (optional)
|
||||
|
||||
- 仅当 SKILL.md Step 3.9 本批捕获到至少一条真实 @bot 请求时出现；否则整段省略。
|
||||
- Heading: `🤖 @bot 答疑`
|
||||
- 一条请求一个条目（• 请求行 + 缩进的 🤖 答复行）。多人问同一件事合并成一答。
|
||||
- **请求行措辞自由发挥**：点出提问者真名 + 自然转述其请求即可，别套「X 问：」这类固定句式。
|
||||
- 语气：真诚、热心、有用的助手——与普通版整体一致。答复落地、给具体建议，别空泛。
|
||||
- 来源：仅群聊上下文 + 自有知识，不联网。需实时/外部数据又无法核实的，如实说明（`这个我查不到实时数据，需要联网确认`），不编造。
|
||||
- Format（遵守 §3：不用 markdown、列表用 •、标题一个 emoji）：
|
||||
```
|
||||
🤖 @bot 答疑
|
||||
|
||||
• {提问者 + 自然转述的请求}
|
||||
🤖 {真诚、简洁、有用的回答；查不到实时信息就如实说明}
|
||||
```
|
||||
|
||||
### 1.9 Footer
|
||||
|
||||
Fixed line, last in file:
|
||||
@@ -149,7 +152,7 @@ No date, no signature, no version number.
|
||||
|
||||
## 2. Roast version (毒舌版)
|
||||
|
||||
Roast 版基于普通版的话题骨架和素材，用毒舌、尖锐、挑衅的风格重写。整体结构与普通版相同（统计区块、开头概览、群友画像、正文分类、@bot 答疑（毒舌值班版，如有）、结尾），但风格完全不同。痛点部分省略。仅当 `include_roast=true` 时生成。标题加 "毒舌版" 后缀。
|
||||
Roast 版基于普通版的话题骨架和素材，用毒舌、尖锐、挑衅的风格重写。整体结构与普通版相同，Section 顺序也一致（标题行、开头概览、正文分类、@bot 答疑（毒舌值班版，如有）、统计区块 + 排行榜、群友画像、结尾），但风格完全不同。痛点部分省略。仅当 `include_roast=true` 时生成。标题加 "毒舌版" 后缀。
|
||||
|
||||
风格要求：
|
||||
- 你是一位以尖锐和挑衅风格著称的专业评论员
|
||||
@@ -159,7 +162,7 @@ Roast 版基于普通版的话题骨架和素材，用毒舌、尖锐、挑衅
|
||||
- 开头概览用更戏谑的口吻，突出荒诞和讽刺
|
||||
- 正文话题标题可以改得更损
|
||||
- 引用原话时配上辛辣点评
|
||||
- @bot 答疑改为「毒舌值班版」（本批有 @bot 请求时才出现，见 SKILL.md Step 3.9，放结尾前；无则省略）：照样把干货答出来，但裹上调侃、嘴硬、吐槽提问者的口吻，与 roast 整体一致；来源同样只用群聊上下文 + 自有知识、不联网，查不到就嘴硬地承认查不到；同守下方红线。请求行措辞自由发挥，用调侃口吻点出提问者和请求即可，别套「又来了」这类固定句式。标题如 `🤖 bot 答疑（毒舌值班版）`，结构示意：
|
||||
- @bot 答疑改为「毒舌值班版」（本批有 @bot 请求时才出现，见 SKILL.md Step 3.9；位置与普通版相同——正文分类之后、统计区块之前；无则省略）：照样把干货答出来，但裹上调侃、嘴硬、吐槽提问者的口吻，与 roast 整体一致；来源同样只用群聊上下文 + 自有知识、不联网，查不到就嘴硬地承认查不到；同守下方红线。请求行措辞自由发挥，用调侃口吻点出提问者和请求即可，别套「又来了」这类固定句式。标题如 `🤖 bot 答疑（毒舌值班版）`，结构示意：
|
||||
|
||||
```
|
||||
🤖 bot 答疑（毒舌值班版）
|
||||
@@ -219,25 +222,8 @@ When you forget the structure mid-write, this is the skeleton:
|
||||
```
|
||||
{群名} 群聊精华 · {日期}
|
||||
|
||||
📊 消息统计: 共 N 条消息
|
||||
1. {昵称}: N 条
|
||||
2. {昵称}: N 条
|
||||
...
|
||||
10. {昵称}: N 条
|
||||
|
||||
{开篇 1-2 段，无标题，直入主题}
|
||||
|
||||
群友画像
|
||||
|
||||
{昵称}（{角色标签}）
|
||||
• {观察 1}
|
||||
• {观察 2}
|
||||
• {观察 3}
|
||||
|
||||
{昵称}（{角色标签}）
|
||||
• {观察 1}
|
||||
• {观察 2}
|
||||
|
||||
🛠 {分类标题 1}
|
||||
|
||||
{该分类下的整理过的讨论 / 段落 / 引用}
|
||||
@@ -259,6 +245,23 @@ When you forget the structure mid-write, this is the skeleton:
|
||||
• {提问者 + 请求，自然转述}
|
||||
🤖 {真诚有用的回答}
|
||||
|
||||
📊 消息统计: 共 N 条消息
|
||||
1. {昵称}: N 条
|
||||
2. {昵称}: N 条
|
||||
...
|
||||
10. {昵称}: N 条
|
||||
|
||||
群友画像
|
||||
|
||||
{昵称}（{角色标签}）
|
||||
• {观察 1}
|
||||
• {观察 2}
|
||||
• {观察 3}
|
||||
|
||||
{昵称}（{角色标签}）
|
||||
• {观察 1}
|
||||
• {观察 2}
|
||||
|
||||
本简报由 AI 自动生成
|
||||
```
|
||||
|
||||
@@ -267,19 +270,8 @@ When you forget the structure mid-write, this is the skeleton:
|
||||
```
|
||||
{群名} 群聊精华 · {日期} · 毒舌版
|
||||
|
||||
📊 消息统计: 共 N 条消息
|
||||
1. {昵称}: N 条 ({毒舌评语})
|
||||
2. {昵称}: N 条 ({毒舌评语})
|
||||
...
|
||||
|
||||
{毒舌开篇 1-2 段}
|
||||
|
||||
群友画像
|
||||
|
||||
{昵称}（{放大的角色标签}）
|
||||
• {毒舌观察 1}
|
||||
• {毒舌观察 2}
|
||||
|
||||
🛠 {更大声的分类标题}
|
||||
|
||||
{保留真实引用的毒舌叙述}
|
||||
@@ -289,6 +281,17 @@ When you forget the structure mid-write, this is the skeleton:
|
||||
• {提问者 + 请求，调侃口吻}
|
||||
🤖 {带刺但仍有实质的回答}
|
||||
|
||||
📊 消息统计: 共 N 条消息
|
||||
1. {昵称}: N 条 ({毒舌评语})
|
||||
2. {昵称}: N 条 ({毒舌评语})
|
||||
...
|
||||
|
||||
群友画像
|
||||
|
||||
{昵称}（{放大的角色标签}）
|
||||
• {毒舌观察 1}
|
||||
• {毒舌观察 2}
|
||||
|
||||
本简报由一个没有感情的 AI 自动生成,如有冒犯,概不负责
|
||||
```
|
||||
|
||||
@@ -298,14 +301,15 @@ When you forget the structure mid-write, this is the skeleton:
|
||||
|
||||
Before writing the digest file, mentally walk through:
|
||||
|
||||
1. Stats block accurate? Counts match the filtered message set?
|
||||
2. Top 10 names resolved (self_display substituted, ambiguous nicknames disambiguated)?
|
||||
3. Opening hooks at least one real category title?
|
||||
4. Every active user (3+ msgs) has a 画像 entry?
|
||||
5. Every category has a topic-named title (not "讨论")?
|
||||
6. Every quote uses 「」 and is traceable to a real message?
|
||||
7. Links inline and complete?
|
||||
8. No markdown bold/heading/link syntax leaked through?
|
||||
9. (Roast only) Every roast bullet would pass the §2 红线 audit?
|
||||
10. Footer line exact match?
|
||||
11. （本批有 @bot 请求时）两版各有对应 @bot 答疑小节？普通版真诚有用、毒舌版带刺仍有干货？无编造的实时信息？
|
||||
1. Section order correct? Opening summary → categorized body → (pain points) → (@bot) → stats block → portraits → footer?
|
||||
2. Stats block accurate? Counts match the filtered message set?
|
||||
3. Top 10 names resolved (self_display substituted, ambiguous nicknames disambiguated)?
|
||||
4. Opening hooks at least one real category title?
|
||||
5. Every active user (3+ msgs) has a 画像 entry?
|
||||
6. Every category has a topic-named title (not "讨论")?
|
||||
7. Every quote uses 「」 and is traceable to a real message?
|
||||
8. Links inline and complete?
|
||||
9. No markdown bold/heading/link syntax leaked through?
|
||||
10. (Roast only) Every roast bullet would pass the §2 红线 audit?
|
||||
11. Footer line exact match, and it is the last line (after 群友画像)?
|
||||
12. （本批有 @bot 请求时）两版各有对应 @bot 答疑小节？普通版真诚有用、毒舌版带刺仍有干货？无编造的实时信息？
|
||||
|
||||
Reference in New Issue
Block a user