Agent Skillssgharlow/claude-code-recipes › summarize-document

summarize-document

GitHub

将长文档(如PDF、报告)提炼为决策就绪的摘要,包括执行摘要、关键要点及角色特定影响。需确认读者背景,确保内容忠实原文并标注出处,同时指出文档未覆盖的盲区,避免无根据推断。

skills/summarize-document/SKILL.md sgharlow/claude-code-recipes

触发场景

用户要求总结文档或提取关键点 用户上传长文档询问核心内容 用户询问是否需要阅读完整文件

安装

npx skills add sgharlow/claude-code-recipes --skill summarize-document -g -y
更多选项

不安装直接使用

npx skills use sgharlow/claude-code-recipes@summarize-document

指定 Agent (Claude Code)

npx skills add sgharlow/claude-code-recipes --skill summarize-document -a claude-code -g -y

安装 repo 全部 skill

npx skills add sgharlow/claude-code-recipes --all -g -y

预览 repo 内 skill

npx skills add sgharlow/claude-code-recipes --list

SKILL.md

Frontmatter
{
    "name": "summarize-document",
    "description": "Summarize a long document into an executive summary, key points, and role-specific implications. Use when the user says \"summarize this document\", \"give me the key points\", \"do I need to read this?\", or drops a long PDF, report, or contract and asks what matters in it."
}

Document Summarization and Key Point Extraction

Read a long document and return a decision-ready digest tuned to the reader's role. The summary must be faithful: every claim in it traces to the document, with section or page references where the format allows.

Steps

  1. Confirm the target file and the reader's context — role, why they are reading it, and what they will do with it (present, decide, share). If context is missing, ask these three questions first; a summary without them is generic and half as useful.
  2. Read the full document. For very long documents, read in passes: structure first (headings, tables, executive sections), then the sections that bear on the reader's stated purpose.
  3. Produce, in order:
    • Executive summary — 3–5 sentences: what the document is, its central claim, why it matters to this reader.
    • Key points — 5–10 bullets, each with a section/page reference.
    • Implications for your role — 2–4 bullets connecting findings to the reader's stated purpose.
    • Numbers that matter — any figures, dates, or thresholds a decision would turn on.
    • What the document does NOT cover — gaps the reader might wrongly assume are addressed.
  4. Verify: re-scan the document for any section not represented in the key points; either add it or state why it was omitted. Never present an inference as the document's claim — label reader-specific interpretation as "Implication", not "Finding".

Constraints

  • Do not summarize a document you could not fully read (unsupported format, truncated file) — say exactly what was unreadable instead of summarizing the fragment silently.
  • Quote sparingly; a digest that is 40% quotation is not a digest.

Full walkthrough, examples, and variations: recipes/Recipe-004-Document-Summarization.md.

版本历史

  • 9157c9a 当前 2026-07-19 10:48

同 Skill 集合

skills/data-cleanup/SKILL.md
skills/meeting-notes-to-actions/SKILL.md
skills/qc-checklist/SKILL.md
skills/research-synthesis/SKILL.md
skills/weekly-status-report/SKILL.md

元信息

文件数
0
版本
9157c9a
Hash
e9f4fbb9
收录时间
2026-07-19 10:48

首页 - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 14:47
浙ICP备14020137号-1 $访客地图$