summarization
Create effective summaries by matching summarization type to purpose, audience, and context. Use when asked to summarize, create TLDR, condense content, or create executive summaries. Keywords: summary, TLDR, condense, executive summary, abstract.
What this skill does
# Summarization ## Purpose Create effective summaries by matching summarization type to purpose, audience, and context. "Summarize" can mean many different things—this skill helps identify and execute the right approach. ## Core Principle **Summarization is translation, not just reduction.** Different purposes require different summary types. Clarify the need before condensing. --- ## Clarifying Questions Before summarizing, consider: 1. **Purpose:** What will this summary be used for? - Decision-making - Background information - Further research - Quick understanding - Reference/recall 2. **Audience:** Who will read it? - Technical experts - General audience - Decision makers - Familiar/unfamiliar with topic 3. **Scope:** How comprehensive? - Ultra-brief (single sentence) - Brief (paragraph) - Moderate (page) - Extended (multiple pages) 4. **Emphasis:** What aspects are most important? - Methodology - Findings/results - Arguments/claims - Context/background - Implications/applications 5. **Format:** What structure? - Narrative text - Bullet points - Hierarchical outline - Visual representation --- ## Summary Type Taxonomy ### Information Reduction Approaches | Type | What It Is | When to Use | |------|-----------|-------------| | **Key Point Extraction** | Isolating the most important claims | Original has discrete important points | | **Abstraction** | Higher-level statements covering multiple details | Patterns matter more than specifics | | **Gisting** | Capturing essential meaning, discarding details | Only core message matters | | **Compression** | Shortening while preserving information | Comprehensive coverage needed in less space | ### Structural Approaches | Type | What It Is | When to Use | |------|-----------|-------------| | **Executive Summary** | Business-focused: decisions, recommendations, outcomes | Documents requiring action | | **Abstract/Précis** | Academic: methodology and findings | Research papers, technical documents | | **TLDR** | Ultra-brief main takeaway | Casual communication, extreme brevity | | **Outline** | Hierarchical structure of main/supporting points | Logical structure matters | ### Purpose-Oriented Approaches | Type | What It Is | When to Use | |------|-----------|-------------| | **Synthesis** | Combining multiple sources coherently | Summarizing across documents | | **Critical Summary** | Evaluating claims while condensing | Assessment of quality needed | | **Contextual Summary** | Framing within broader knowledge | Understanding bigger picture matters | | **Actionable Summary** | Focusing on implications and next steps | Summary will drive action | --- ## Execution by Type ### Key Point Extraction 1. Scan for topic sentences and conclusions 2. Identify explicitly stated main ideas 3. List each distinct point 4. Preserve original phrasing where powerful **Example:** "The author makes three main arguments: (1)..., (2)..., (3)..." ### Abstraction 1. Group related details 2. Find common themes or patterns 3. Create higher-level statements 4. Reduce specifics to principles **Example:** "Multiple studies consistently show..." instead of listing 12 studies ### Gisting 1. Ask: "What is the one thing to remember?" 2. Distill to core insight 3. Remove all supporting detail 4. Verify essence is preserved **Example:** "Remote work increases productivity for most knowledge workers." ### Executive Summary 1. State the problem/opportunity 2. Present the solution/recommendation 3. Highlight key benefits 4. Note costs/risks 5. Specify required actions ### Synthesis 1. Read all sources 2. Identify common themes 3. Note contradictions 4. Find complementary information 5. Create unified narrative **Example:** "Across the five reports, three key trends emerge..." ### Critical Summary 1. Summarize the claims 2. Evaluate the evidence 3. Assess methodology 4. Note limitations 5. Conclude with assessment **Example:** "While the author claims X, the evidence is limited by..." --- ## Format Variations ### Quotation-Based - Use key phrases verbatim - When precise wording is important - Select and organize most important quotes ### Bullet Points - Break continuous text into discrete units - When quick scanning is valued - Make each point standalone ### Progressive Summary - Start ultra-brief - Add layers of detail - Let reader choose depth ### Comparative Summary - Side-by-side analysis - Highlight similarities and differences - When contrasting sources --- ## Quality Checklist - [ ] Purpose is clear - [ ] Audience is considered - [ ] Scope is appropriate - [ ] Emphasis matches needs - [ ] Format serves purpose - [ ] Core message is preserved - [ ] Reduction is proportional - [ ] No invented information - [ ] Attribution where needed --- ## Anti-Patterns ### The Information Dump **Problem:** Reduces length but not complexity **Fix:** Focus on what matters, not just what's short ### The Distortion **Problem:** Changes meaning through compression **Fix:** Verify summary against original claims ### The One-Size-Fits-All **Problem:** Same approach for all requests **Fix:** Match type to purpose and audience ### The Over-Abstraction **Problem:** Loses all useful specifics **Fix:** Preserve concrete details that support understanding --- ## Integration Points **Inbound:** - When asked to summarize any content - When processing long documents - When creating documentation **Outbound:** - To decision-making processes - To knowledge management systems - To communication outputs **Complementary:** - `speech-adaptation`: For spoken summaries - `voice-analysis`: For maintaining voice in summaries
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.