Summarization
Reduce reading time while preserving the source's meaning, evidence, decisions,
uncertainty, and useful detail.
Runtime Compatibility
- Resolve bundled files relative to this skill directory.
- Use tools available in the active runtime to read the actual source material.
- Do not claim full coverage of inaccessible, truncated, or unsupported input.
- Verify extraction quality when the source is a scan, recording, or complex file.
Intake
Infer these settings from the request and source:
- audience;
- purpose;
- output length;
- required format;
- facts that must survive compression;
- whether attribution to speakers or documents matters.
When the request is underspecified, choose a practical format and state the
compression level in one short line.
Workflow
Establish source boundaries
- Identify every file, message range, URL, transcript, or diff included.
- Note missing pages, failed extraction, inaudible segments, or truncation.
Build a source map
- Record the central claim or purpose.
- Capture decisions, evidence, dates, quantities, people, risks, and open items.
- Separate facts, opinions, proposals, and unresolved statements.
Rank information
- Keep what the target reader needs to decide, act, understand, or verify.
- Remove repetition, scene-setting, and low-impact detail unless requested.
Write the summary
- Put the bottom line first.
- Group related points rather than following source order mechanically.
- Preserve qualifications that change the meaning of a claim.
Audit against the source
- Check names, figures, dates, units, ownership, and negation.
- Confirm that no new conclusion was introduced.
- Flag contradictions instead of silently resolving them.
Format Selection
Executive Brief
Use for reports, proposals, and decision material:
- bottom line;
- strongest evidence;
- risks or uncertainty;
- required decision;
- next actions.
Technical Summary
Use for specifications, architecture, incidents, and code:
- purpose and scope;
- behavior or design;
- interfaces and dependencies;
- important decisions;
- trade-offs and limitations;
- breaking changes or follow-up work.
Meeting Or Conversation
Use for notes, chats, and email threads:
- decisions;
- action items with owner and due date when stated;
- key reasoning;
- disagreements;
- unresolved questions.
Do not assign an owner or deadline that was not explicitly agreed.
Research Digest
Use for papers and analytical material:
- research question;
- method and sample;
- main findings;
- limitations;
- implications.
Keep correlation, causation, statistical confidence, and author interpretation
distinct.
Multi-Source Synthesis
- Read all available sources before drafting.
- Organize by theme or question.
- Attribute disputed or source-specific claims.
- Surface conflicts in dates, measurements, definitions, or conclusions.
- Avoid presenting repeated claims as independent confirmation.
Compression Levels
- Snapshot: one paragraph or a few bullets.
- Brief: bottom line plus essential evidence and actions.
- Detailed: structured coverage of all major sections and caveats.
Scale by information density and user need, not page count alone.
Output Rules
- Do not invent context, intent, consensus, or causality.
- Preserve exact numbers and dates when they affect meaning.
- Use direct quotes only when wording itself matters and the source is available.
- Mark uncertainty with precise language.
- Distinguish source omissions from your own inability to access material.
- Keep recommendations separate from the summary unless the user requests them.
Optional Templates
Load summary-templates.md when a reusable output skeleton will save time. Adapt
the template to the source instead of filling empty sections mechanically.
Final Check
- The opening states the most important conclusion or purpose.
- All critical figures, decisions, and caveats match the source.
- The summary is useful without pretending to replace unavailable evidence.
- The length and terminology fit the intended reader.
1---2name: summarization3description: Create accurate summaries of documents, articles, meetings, research, code changes, or multiple sources as briefs, key points, actions, or catch-up notes.4---56# Summarization78Reduce reading time while preserving the source's meaning, evidence, decisions,9uncertainty, and useful detail.1011## Runtime Compatibility1213- Resolve bundled files relative to this skill directory.14- Use tools available in the active runtime to read the actual source material.15- Do not claim full coverage of inaccessible, truncated, or unsupported input.16- Verify extraction quality when the source is a scan, recording, or complex file.1718## Intake1920Infer these settings from the request and source:2122- audience;23- purpose;24- output length;25- required format;26- facts that must survive compression;27- whether attribution to speakers or documents matters.2829When the request is underspecified, choose a practical format and state the30compression level in one short line.3132## Workflow33341. **Establish source boundaries**35 - Identify every file, message range, URL, transcript, or diff included.36 - Note missing pages, failed extraction, inaudible segments, or truncation.37382. **Build a source map**39 - Record the central claim or purpose.40 - Capture decisions, evidence, dates, quantities, people, risks, and open items.41 - Separate facts, opinions, proposals, and unresolved statements.42433. **Rank information**44 - Keep what the target reader needs to decide, act, understand, or verify.45 - Remove repetition, scene-setting, and low-impact detail unless requested.46474. **Write the summary**48 - Put the bottom line first.49 - Group related points rather than following source order mechanically.50 - Preserve qualifications that change the meaning of a claim.51525. **Audit against the source**53 - Check names, figures, dates, units, ownership, and negation.54 - Confirm that no new conclusion was introduced.55 - Flag contradictions instead of silently resolving them.5657## Format Selection5859### Executive Brief6061Use for reports, proposals, and decision material:6263- bottom line;64- strongest evidence;65- risks or uncertainty;66- required decision;67- next actions.6869### Technical Summary7071Use for specifications, architecture, incidents, and code:7273- purpose and scope;74- behavior or design;75- interfaces and dependencies;76- important decisions;77- trade-offs and limitations;78- breaking changes or follow-up work.7980### Meeting Or Conversation8182Use for notes, chats, and email threads:8384- decisions;85- action items with owner and due date when stated;86- key reasoning;87- disagreements;88- unresolved questions.8990Do not assign an owner or deadline that was not explicitly agreed.9192### Research Digest9394Use for papers and analytical material:9596- research question;97- method and sample;98- main findings;99- limitations;100- implications.101102Keep correlation, causation, statistical confidence, and author interpretation103distinct.104105### Multi-Source Synthesis106107- Read all available sources before drafting.108- Organize by theme or question.109- Attribute disputed or source-specific claims.110- Surface conflicts in dates, measurements, definitions, or conclusions.111- Avoid presenting repeated claims as independent confirmation.112113## Compression Levels114115- **Snapshot:** one paragraph or a few bullets.116- **Brief:** bottom line plus essential evidence and actions.117- **Detailed:** structured coverage of all major sections and caveats.118119Scale by information density and user need, not page count alone.120121## Output Rules122123- Do not invent context, intent, consensus, or causality.124- Preserve exact numbers and dates when they affect meaning.125- Use direct quotes only when wording itself matters and the source is available.126- Mark uncertainty with precise language.127- Distinguish source omissions from your own inability to access material.128- Keep recommendations separate from the summary unless the user requests them.129130## Optional Templates131132Load `summary-templates.md` when a reusable output skeleton will save time. Adapt133the template to the source instead of filling empty sections mechanically.134135## Final Check136137- The opening states the most important conclusion or purpose.138- All critical figures, decisions, and caveats match the source.139- The summary is useful without pretending to replace unavailable evidence.140- The length and terminology fit the intended reader.