/summarize-doc
Create an executive summary of any document at the appropriate level of detail. Triggers on \"summarize this\", \"main points\", \"give me the gist\". See also: `file-document` if you also want to save it; `capture-meeting` if it's meeting notes.
Claude Code
$ npx -y skills add kbanc85/claudia --skill summarize-doc --agent claude-code
Codex
$ npx skills add kbanc85/claudia --skill summarize-doc -a codex -y
Cursor
$ npx skills add kbanc85/claudia --skill summarize-doc -a cursor -y
Gemini CLI
$ npx skills add kbanc85/claudia --skill summarize-doc -a gemini-cli -y
GitHub Copilot
$ npx skills add kbanc85/claudia --skill summarize-doc -a github-copilot -y
OpenCode
$ npx skills add kbanc85/claudia --skill summarize-doc -a opencode -y
Windsurf
$ npx skills add kbanc85/claudia --skill summarize-doc -a windsurf -y
SKILL.md
summarize-doc.SKILL.mdname: summarize-doc
description: "Create an executive summary of any document at the appropriate level of detail. Triggers on \"summarize this\", \"main points\", \"give me the gist\". See also: `file-document` if you also want to save it; `capture-meeting` if it's meeting notes."
effort-level: medium
Summarize Doc
Create an executive summary of any document.
Usage
`/summarize-doc`
Then provide the document content (paste, upload, or describe location).
Input Types
- Pasted text
- PDF content
- Meeting transcript
- Email thread
- Report or article
- Contract or legal document
- Any long-form content
Summary Levels
Quick Summary (Default)
- 3-5 bullet points
- Key takeaways only
- 30-second read
Standard Summary
- Executive summary paragraph
- Key points with context
- Important details
- 2-3 minute read
Detailed Summary
- Section-by-section breakdown
- All significant points
- Relevant quotes
- 5-10 minute read
Ask: "Quick summary, standard, or detailed?"
Output Format
Quick Summary
## Summary: [Document Title]
**Key Points:**
- [Point 1]
- [Point 2]
- [Point 3]
**Bottom Line:** [One sentence takeaway]
Standard Summary
## Summary: [Document Title]
### Executive Summary
[2-3 paragraph overview]
### Key Points
1. [Point with context]
2. [Point with context]
3. [Point with context]
### Important Details
- [Detail 1]
- [Detail 2]
### Action Items (if any)
- [Action required]
### Bottom Line
[What this means for the reader]
Detailed Summary
## Detailed Summary: [Document Title]
### Overview
[Comprehensive executive summary]
### Section Breakdown
#### [Section 1 Name]
[Summary of section]
- Key points
- Relevant quotes
#### [Section 2 Name]
[Continue for each section]
### Key Themes
- [Theme 1]
- [Theme 2]
### Notable Quotes
> "[Important quote]"
### Action Items
- [Action 1]
- [Action 2]
### Questions/Concerns Raised
- [Question]
### Recommendations
[If applicable]
Document Types
Meeting Transcript
Focus on:
- Decisions made
- Action items
- Key discussion points
- Next steps
Contract/Legal
Focus on:
- Key terms
- Obligations
- Important dates
- Risks or concerns
Report/Article
Focus on:
- Main argument/finding
- Supporting evidence
- Implications
- Recommendations
Email Thread
Focus on:
- What's being discussed
- What's being asked
- Where things stand
- What needs to happen
Special Handling
Confidential Documents
- Note confidentiality
- Ask about sharing/storage
Technical Documents
- Explain jargon if needed
- Focus on implications over details
Long Documents
- Offer section-by-section approach
- Prioritize most relevant sections
Quality Checklist
- [ ] Captures main message accurately
- [ ] Key points are genuinely key (not everything)
- [ ] Actionable items clearly identified
- [ ] Length appropriate for summary level
- [ ] Reader can understand without original
Follow-Up Options
After summarizing: "Would you like me to:
- Extract action items to track?
- Draft a response?
- Highlight specific sections?
- Save summary to a file?"
Read more
name: summarize-doc description: "Create an executive summary of any document at the appropriate level of detail. Triggers on \"summarize this\", \"main points\", \"give me the gist\". See also: `file-document` if you also want to save it; `capture-meeting` if it's meeting notes." effort-level: medium
Summarize Doc
Create an executive summary of any document.
Usage
`/summarize-doc`
Then provide the document content (paste, upload, or describe location).
Input Types
- Pasted text
- PDF content
- Meeting transcript
- Email thread
- Report or article
- Contract or legal document
- Any long-form content
Summary Levels
Quick Summary (Default)
- 3-5 bullet points
- Key takeaways only
- 30-second read
Standard Summary
- Executive summary paragraph
- Key points with context
- Important details
- 2-3 minute read
Detailed Summary
- Section-by-section breakdown
- All significant points
- Relevant quotes
- 5-10 minute read
Ask: "Quick summary, standard, or detailed?"
Output Format
Quick Summary
## Summary: [Document Title] **Key Points:** - [Point 1] - [Point 2] - [Point 3] **Bottom Line:** [One sentence takeaway]
Standard Summary
## Summary: [Document Title] ### Executive Summary [2-3 paragraph overview] ### Key Points 1. [Point with context] 2. [Point with context] 3. [Point with context] ### Important Details - [Detail 1] - [Detail 2] ### Action Items (if any) - [Action required] ### Bottom Line [What this means for the reader]
Detailed Summary
## Detailed Summary: [Document Title] ### Overview [Comprehensive executive summary] ### Section Breakdown #### [Section 1 Name] [Summary of section] - Key points - Relevant quotes #### [Section 2 Name] [Continue for each section] ### Key Themes - [Theme 1] - [Theme 2] ### Notable Quotes > "[Important quote]" ### Action Items - [Action 1] - [Action 2] ### Questions/Concerns Raised - [Question] ### Recommendations [If applicable]
Document Types
Meeting Transcript
Focus on:
- Decisions made
- Action items
- Key discussion points
- Next steps
Contract/Legal
Focus on:
- Key terms
- Obligations
- Important dates
- Risks or concerns
Report/Article
Focus on:
- Main argument/finding
- Supporting evidence
- Implications
- Recommendations
Email Thread
Focus on:
- What's being discussed
- What's being asked
- Where things stand
- What needs to happen
Special Handling
Confidential Documents
- Note confidentiality
- Ask about sharing/storage
Technical Documents
- Explain jargon if needed
- Focus on implications over details
Long Documents
- Offer section-by-section approach
- Prioritize most relevant sections
Quality Checklist
- [ ] Captures main message accurately
- [ ] Key points are genuinely key (not everything)
- [ ] Actionable items clearly identified
- [ ] Length appropriate for summary level
- [ ] Reader can understand without original
Follow-Up Options
After summarizing: "Would you like me to:
- Extract action items to track?
- Draft a response?
- Highlight specific sections?
- Save summary to a file?"
Terminal-based AI chief of staff. Remembers relationships, tracks commitments, helps you think strategically. Runs on Claude Code.
Other skills on claudia.
More skills from other plugins.
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress…
distilly
Set up the owner profile so a personal agent knows who it works for (first-run setup, \"get to know me\"), or distill colleague,…
Questions about summarize-doc.
- Which coding agents can use summarize-doc?
- summarize-doc installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

