Back to Details

reader-recap

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
You are summarizing the user's recent reading activity from Readwise Reader. Follow this process carefully.
你需要从Readwise Reader中汇总用户近期的阅读活动，请严格遵循以下流程。

Readwise Access

Readwise 访问

Check if Readwise MCP tools are available (e.g. 
mcp__readwise__reader_list_documents
). If they are, use them throughout. If not, use the equivalent 
readwise
CLI commands instead (e.g. 
readwise list
, 
readwise read <id>
, 
readwise highlights <id>
). The instructions below reference MCP tool names — translate to CLI equivalents as needed.
检查是否有可用的Readwise MCP工具（例如 
mcp__readwise__reader_list_documents
）。如果有，请全程使用这些工具；如果没有，请改用等效的
readwise
CLI命令（例如 
readwise list
、
readwise read <id>
、
readwise highlights <id>
）。以下说明中引用的是MCP工具名称——必要时请替换为对应的CLI命令。

Setup

准备步骤

  1. Check for persona file. Read 
    reader_persona.md
    in the current working directory if it exists. Use it to personalize the briefing tone and to contextualize the user's annotations (e.g. connecting highlights to their known interests). If no persona file exists, proceed without it — the recap works fine standalone.
  2. Determine time window. Parse the argument as a number of days. Default to 1 (last 24 hours) if no argument is given.
/reader-recap           # last 24 hours
/reader-recap 7         # last 7 days
/reader-recap 30        # last 30 days
  1. 检查角色文件：如果当前工作目录下存在
    reader_persona.md
    文件，请读取该文件。使用它来调整简报的语气，并结合用户的标注内容（例如，将标注内容与用户已知的兴趣点关联）。如果没有角色文件，直接继续即可——复盘功能可以独立运行。
  2. 确定时间范围：将参数解析为天数。如果未提供参数，默认时间范围为1（过去24小时）。
/reader-recap           # 过去24小时
/reader-recap 7         # 过去7天
/reader-recap 30        # 过去30天

Step 1: Fetch Recent Documents

步骤1：获取近期文档

Query Reader for documents the user archived or moved to "later" within the time window. Run both calls in parallel:
mcp__readwise__reader_list_documents(location="archive", updated_after=<cutoff>, limit=100, response_fields=["title", "author", "category", "notes", "source_url"])
mcp__readwise__reader_list_documents(location="later", updated_after=<cutoff>, limit=100, response_fields=["title", "author", "category", "notes", "source_url"])
Combine and deduplicate results by document ID.
If no documents are found, report "No archived or moved documents in the last [N] days" and stop.
向Reader查询用户在指定时间范围内归档或移至“稍后阅读”的文档。并行执行以下两个调用：
mcp__readwise__reader_list_documents(location="archive", updated_after=<cutoff>, limit=100, response_fields=["title", "author", "category", "notes", "source_url"])
mcp__readwise__reader_list_documents(location="later", updated_after=<cutoff>, limit=100, response_fields=["title", "author", "category", "notes", "source_url"])
合并结果并按文档ID去重。
如果未找到任何文档，请提示“过去[N]天内没有归档或移至稍后阅读的文档”并停止流程。

Step 2: Get Highlights

步骤2：获取标注内容

For each document returned, fetch highlights:
mcp__readwise__reader_get_document_highlights(document_id=<id>)
After fetching, split documents into three groups:
  • Annotated — has highlights where the user left notes (the 
    note
    field is non-empty), OR has a non-empty document-level 
    notes
    field
  • Highlighted only — has highlights but none with user notes
  • No engagement — zero highlights and no document-level notes (archived without reading)
对每个返回的文档，获取其标注内容：
mcp__readwise__reader_get_document_highlights(document_id=<id>)
获取完成后，将文档分为三组：
  • 带注释的文档：存在用户添加了笔记的标注（
    note
    字段非空），或文档级别的
    notes
    字段非空
  • 仅标注的文档：存在标注但没有用户添加的笔记
  • 无互动的文档：没有标注且文档级别无笔记（未阅读就归档）

Step 3: Classify Annotations

步骤3：分类注释内容

For each annotated document, scan the user's notes on highlights and the document-level notes field. Flag anything actionable:
FlagPattern
QuestionContains "?" or asks something
TODOSays to look up, verify, follow up, try, or do something
IdeaConnects multiple concepts or proposes something new
DisagreementPushes back on the source's claim
Cross-referenceMentions another book, article, or author by name
Annotations that don't match any pattern are just context — the user thinking out loud. Still include them in the briefing.
对每个带注释的文档，扫描用户在标注上的笔记以及文档级别的笔记字段。标记所有可执行的内容：
标记特征
问题包含“?”或提出某个问题
待办事项提到需要查阅、验证、跟进、尝试或执行某件事
想法关联多个概念或提出新观点
异议反驳原文的主张
交叉引用提及另一本书、文章或作者的名称
不符合任何特征的注释仅作为上下文——即用户的随意思考。仍需将其包含在简报中。

Step 4: Write the Briefing

步骤4：撰写简报

Write a conversational recap — like a well-read assistant catching someone up over coffee. Warm, concise, and useful. Not a data dump.
Structure:
  1. Opening line — a one-sentence overview of the time period.
    "You had a busy week — 12 articles and a book, mostly history and AI stuff."
    "Quiet day — just two articles, but you had a lot to say about one of them."
  2. Per-document paragraphs — one short paragraph per annotated document, ordered by engagement (most annotated first). Each paragraph should naturally weave together:
    • What the piece was about (1 sentence)
    • How much the user highlighted (folded into the flow, not as a stat line)
    • The most interesting annotations, especially actionable ones — paraphrase the user's notes conversationally: "You had a question about whether this applies to mammals too." "You noted you want to try this workflow yourself." "You pushed back on the author's claim about pricing."
    • If the user left a document-level note, lead with it — it's usually the overall reaction
  3. Light reads — a single sentence listing documents the user highlighted but didn't annotate. "You also highlighted a few things in [Title] and [Title] but didn't leave notes."
  4. Action items — if any annotations were flagged as TODOs, questions, or ideas, collect them at the end as a short bulleted list under "Things you might want to follow up on:". Skip this section entirely if nothing is actionable.
Example output:
Busy couple of days — you finished 8 articles and a chunk of that Ottoman
history book. Most of your attention went to the logistics stuff.

You were really into Sarah Chen's piece on supply chain resilience. 14
highlights, and you left a note saying the comparison to Roman grain
logistics was "exactly what I've been looking for." You also flagged a
question — whether the same bottleneck pattern shows up in digital
infrastructure.

The Ottoman book got 9 new highlights across three chapters. Your note on
the harem education system connected it to that article about elite
training programs you read last month. You also marked a claim about
succession rates that you want to verify.

You also highlighted a few things in "Why Bridges Fail" and a Substack
post about medieval farming, but didn't leave notes on either.

**Things you might want to follow up on:**
- Does the supply chain bottleneck pattern apply to digital infrastructure?
- Verify the Ottoman succession rate claim (Chapter 7)
- You wanted to connect harem education to the elite training piece
Tone rules:
  • Second person ("you read", "you noted"), not third person
  • Contractions are fine
  • No bullet-point lists for the main body — prose paragraphs only
  • Keep it skimmable — short paragraphs, one idea each
  • Don't editorialize on the content itself — just report what the user did and said
  • The action items list at the end IS bulleted — that's the one exception
  • If the persona file exists, use it to add context (e.g. "this connects to your interest in X")
撰写对话式的复盘简报——就像一位博学的助理在咖啡时间和你同步信息一样。语气亲切、简洁且实用，不要堆砌数据。
结构：
  1. 开场白——用一句话概述指定时间范围内的阅读情况。
    "你这周阅读量很大——12篇文章和一本书，主要是历史和AI相关内容。"
    "今天阅读不多——只有两篇文章，但你其中一篇有很多见解。"
  2. 按文档分段——每个带注释的文档对应一个短段落，按互动程度排序（注释最多的排在最前面）。每个段落应自然融入以下内容：
    • 文章的主题（一句话）
    • 用户的标注量（自然融入叙述，不要生硬地作为统计数据）
    • 最有趣的注释，尤其是可执行的内容——用对话式的语言转述用户的笔记： "你提出了一个问题，想知道这是否也适用于哺乳动物。" "你提到想亲自尝试这个工作流。" "你反驳了作者关于定价的主张。"
    • 如果用户留下了文档级别的笔记，将其放在段落开头——这通常是整体的反馈
  3. 轻阅读内容——用一句话列出用户标注过但未添加注释的文档。“你还在《[标题]》和《[标题]》中标注了一些内容，但没有留下笔记。”
  4. 行动项——如果有注释被标记为待办事项、问题或想法，将它们收集在末尾，以“你可能需要跟进的事项：”为标题，用短列表呈现。如果没有可执行内容，则跳过此部分。
示例输出：
过去两天你阅读不少——完成了8篇文章和奥斯曼帝国史的部分章节。你主要关注的是物流相关内容。

你对Sarah Chen关于供应链韧性的文章很感兴趣。你标注了14处，还留下笔记说，文中将其与罗马谷物物流的对比“正是我一直在找的内容”。你还提出了一个问题——这种瓶颈模式是否也适用于数字基础设施。

奥斯曼帝国史的书中，你在三个章节里新增了9处标注。你关于后宫教育体系的笔记，将其与你上个月读的那篇关于精英培训项目的文章联系了起来。你还标记了一个关于继承率的主张，需要验证。

你还在《桥梁为何倒塌》和一篇关于中世纪农业的Substack文章中标注了一些内容，但都没有留下笔记。

**你可能需要跟进的事项：**
- 供应链瓶颈模式是否适用于数字基础设施？
- 验证奥斯曼帝国继承率的主张（第7章）
- 你想将后宫教育体系与精英培训文章关联起来
语气规则：
  • 使用第二人称（“你读了”、“你提到”），而非第三人称
  • 可以使用缩写（比如“don't”）
  • 主体部分不要使用项目符号列表——仅使用散文段落
  • 内容要易于浏览——段落简短，每段一个核心观点
  • 不要对原文内容发表评论——仅报告用户的行为和见解
  • 末尾的行动项列表可以使用项目符号——这是唯一的例外
  • 如果存在角色文件，用它来添加上下文（例如，“这与你对X的兴趣相关”）

Notes

注意事项

  • This skill is read-only. It doesn't move, tag, or modify any documents.
  • The "archive" and "later" locations catch most finished reading. Documents still in "feed" or "new" are works in progress and aren't included.
  • Annotations (the user's own notes on highlights) are the interesting part. Raw highlights without notes are counted but not shown individually.
  • For large time windows (30 days), there may be many documents. Prioritize the most-annotated ones and summarize the rest in aggregate rather than writing a paragraph for every single one.
  • 此skill为只读。不会移动、标记或修改任何文档。
  • “归档”和“稍后阅读”文件夹涵盖了大多数已完成的阅读内容。仍在“订阅源”或“新内容”中的文档属于未完成的阅读，不会被包含在内。
  • 注释（用户在标注上添加的个人笔记）是重点内容。没有笔记的原始标注会被统计，但不会单独展示。
  • 对于较大的时间范围（如30天），可能会有很多文档。优先处理注释最多的文档，其余的则汇总概述，而非为每个文档单独撰写段落。