メニュー
Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | codexkit-document-summarizer |
| description | Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents. |
| version | 1.0.0 |
| category | review |
Classify the source: policy, proposal, memo, research, contract-like document, transcript, academic paper, operating document, or mixed packet.
Capture:
Keep source-backed summary separate from analysis or recommendation. Mark anything inferred.
Adapt format for executive, manager, student, legal/compliance reviewer, or team member.
State which sections deserve human review and why.
| Input | Required | Format |
|---|---|---|
| Document text or excerpt | Yes | Pasted text, extracted notes, OCR |
| Document type | Recommended | Proposal, policy, memo, research, etc. |
| Audience | Recommended | Executive, manager, student, team |
| Desired length | Optional | 5 bullets, one page, detailed brief |
| Focus area | Optional | Risks, obligations, actions, decisions |
## Document Summary - [Document Name]
### One-Line Takeaway
[Core point]
### Key Points
- [Point backed by source]
### Actions / Decisions
| Item | Owner | Deadline | Source Note |
|------|-------|----------|-------------|
### Risks / Caveats
- [Risk]
### Needs Human Review
- [Section or issue]
| Check | Question |
|---|---|
| Correctness | Are all summarized claims traceable to the document text? |
| Completeness | Are key points, actions, deadlines, risks, and review needs captured? |
| Context-fit | Does the summary match the audience and intended decision? |
| Consequence | What could be misread if the user relies only on the summary? |
Prompt: "Summarize this vendor proposal for an operations manager. Focus on deliverables, pricing assumptions, risks, and questions for the vendor."
Good pattern: "The proposal assumes customer data export is available by June 1. This is a dependency, not a confirmed commitment."
Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.
Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.
Turn business data, KPI movement, or experiment results into a clear narrative using the what-so what-now what structure, audience calibration, and action-oriented insight. Use when leaders need a data-backed brief, dashboard storyline, or metric interpretation. Do not use for raw statistical modeling with no communication deliverable.
Draft clear, professional business emails from rough notes, context, or instructions. Handles cold outreach, internal updates, client responses, and escalation drafts. Use when the work is routine email writing with known context and audience. Do not use for sensitive legal notices, formal regulatory correspondence, or board-level communication without review.
Summarize meeting notes or transcripts into decisions, action items, owners, risks, and follow-up messages. Use after meetings when raw notes need a clean recap.
Create practical role-specific onboarding checklists with owners, timing, access needs, and first-week milestones. Use for new hire, contractor, client, or team onboarding.