Skip to main content

document-summarizer

Summarize long documents, reports, papers, contracts, or transcripts into clear, actionable briefs without losing critical information.

Zur Installation springen

Quellinformationen

Repository
DHsustainer/gnostor
Letzte Quellaktivität
4. Mai 2026 um 09:35
Erkannte Sprache von SKILL.md
Englisch
Sterne
1
Forks
0

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md wird angezeigt

SKILL.md
Quellanweisungen · Schreibgeschützte Vorschau
name
document-summarizer
description
Summarize long documents, reports, papers, contracts, or transcripts into clear, actionable briefs without losing critical information.
version
1.0.0
author
Gnostor Community
license
MIT
metadata
{"hermes":{"tags":["summarization","documents","productivity","reading","research","reports","PDF"]}}
# Document Summarizer Extract the essential from any long document — reports, papers, contracts, transcripts, books — and present it in a format that's actually useful for your decision. ## When to Use - "Summarize this document / report / paper" - "What are the key points in this?" - "I need to read this but only have 5 minutes" - "Extract only the financial data / recommendations / risks from this" - "Compare these two documents" ## What to Give Me - The document text (paste it or use the pdf / file reading tools) - **Purpose**: why you're reading it — what decision does this inform? - **Audience**: who will read the summary (exec, technical team, client, yourself) - **Format**: executive brief, bullet points, detailed outline, Q&A ## Summary Formats ### Executive Brief (for decisions) ```markdown ## [Document Title] **Source:** | **Date:** | **Pages:** ### Bottom Line One sentence: what this document is and what it means for you. ### Key Findings - Finding 1 - Finding 2 - Finding 3 ### Recommendations / Actions - What the document recommends you do - What you should do next ### Caveats / Risks - Important limitations or assumptions ### Details Worth Reading Sections you should read in full, and why. ``` ### Bullet Brief (for fast consumption) 5–10 bullets, each starting with the most important word. ### Structured Outline (for reference) Preserves document structure, condenses each section. ### Q&A Format (for specific questions) I answer your specific questions from the document, with citations. ## Document Types | Type | What I focus on | |---|---| | **Research paper** | Hypothesis, methodology, findings, limitations | | **Business report** | Key metrics, recommendations, risks | | **Legal contract** | Obligations, rights, deadlines, risk clauses | | **Financial document** | Numbers, trends, ratios, outlook | | **Meeting transcript** | Decisions, action items, open questions | | **Book / long article** | Central argument, key evidence, takeaways | | **Technical spec** | Requirements, constraints, open decisions | ## Multi-Document Mode Give me several documents and ask: - "What do these agree on?" - "Where do they contradict each other?" - "Which one is most relevant to [question]?" - "Combine these into one coherent summary"
Auf GitHub ansehen