scienceclaw-summarization
Summarize scientific papers, datasets, experimental results, and literature reviews. Use when: (1) condensing research papers, (2) creating literature reviews, (3) summarizing experimental findings, (4) meta-analysis synthesis, (5) creating executive summaries of research. NOT for: information extraction (use scienceclaw-ie), full paper retrieval (use scienceclaw-retrieval), or writing new content (use scienceclaw-generation).
Best use case
scienceclaw-summarization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Summarize scientific papers, datasets, experimental results, and literature reviews. Use when: (1) condensing research papers, (2) creating literature reviews, (3) summarizing experimental findings, (4) meta-analysis synthesis, (5) creating executive summaries of research. NOT for: information extraction (use scienceclaw-ie), full paper retrieval (use scienceclaw-retrieval), or writing new content (use scienceclaw-generation).
Teams using scienceclaw-summarization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scienceclaw-summarization/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scienceclaw-summarization Compares
| Feature / Agent | scienceclaw-summarization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Summarize scientific papers, datasets, experimental results, and literature reviews. Use when: (1) condensing research papers, (2) creating literature reviews, (3) summarizing experimental findings, (4) meta-analysis synthesis, (5) creating executive summaries of research. NOT for: information extraction (use scienceclaw-ie), full paper retrieval (use scienceclaw-retrieval), or writing new content (use scienceclaw-generation).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
SKILL.md Source
# scienceclaw-summarization Summarize scientific papers, datasets, experimental results, and literature reviews with discipline-aware precision and faithful representation of source material. ## When to Use - Condensing a full research paper into a structured abstract or brief summary - Creating literature review summaries across multiple papers on a topic - Summarizing experimental findings, including methods, results, and conclusions - Synthesizing results from multiple studies for meta-analysis overviews - Producing executive summaries of research for non-specialist audiences - Distilling key takeaways from conference proceedings or preprint batches - Generating comparative summaries across related studies ## When NOT to Use - Extracting structured data points, entities, or relations from papers -- use `scienceclaw-ie` - Retrieving or finding papers from databases -- use `scienceclaw-retrieval` - Writing original research content, drafts, or manuscripts -- use `scienceclaw-generation` - Answering specific factual questions about science -- use `scienceclaw-qa` - Verifying claims or checking statistical validity -- use `scienceclaw-verification` ## Summary Types ### Abstract-Style Summary A concise summary (150-300 words) that mirrors the structure of a scientific abstract: 1. **Background** -- one to two sentences of context and motivation 2. **Objective** -- the research question or hypothesis 3. **Methods** -- brief description of approach, dataset, or experimental design 4. **Results** -- key quantitative findings with effect sizes and confidence intervals where available 5. **Conclusion** -- main takeaway and implications ### Executive Summary A high-level overview (300-500 words) aimed at decision-makers or non-specialists: 1. **Problem Statement** -- why this research matters 2. **Approach** -- what was done, in plain language 3. **Key Findings** -- the most impactful results, translated for a general audience 4. **Implications** -- practical significance and next steps 5. **Limitations** -- major caveats or open questions ### Detailed Summary A thorough walkthrough (500-1500 words) preserving methodological detail: 1. **Introduction and Motivation** -- full context and prior work referenced 2. **Methods and Materials** -- detailed experimental or analytical design 3. **Results** -- comprehensive reporting of all major findings, tables, and figures described 4. **Discussion** -- interpretation, comparison with related work, alternative explanations 5. **Limitations and Future Work** -- weaknesses acknowledged by authors and beyond ### Systematic Review Summary A structured synthesis across multiple papers: 1. **Search Strategy** -- how papers were identified and selected 2. **Inclusion/Exclusion Criteria** -- what qualified for the review 3. **Study Characteristics** -- table of included studies with key attributes 4. **Synthesized Findings** -- aggregated results, agreement and disagreement across studies 5. **Quality Assessment** -- risk of bias and evidence strength per study 6. **Gaps and Recommendations** -- what remains unanswered ## Discipline-Aware Terminology Summaries must respect the vocabulary conventions of the source discipline: - **Biomedical Sciences** -- use MESH terms, standard gene/protein nomenclature, clinical trial phase terminology, CONSORT-aligned reporting - **Physics and Astronomy** -- preserve unit conventions (SI, CGS), uncertainty notation, standard model terminology - **Computer Science** -- retain benchmark names, model architecture terms, dataset identifiers, metric abbreviations (F1, BLEU, ROUGE) - **Chemistry** -- use IUPAC nomenclature, preserve reaction notation, maintain spectroscopic data references - **Social Sciences** -- respect statistical reporting norms (APA style), effect size conventions, survey methodology terms - **Earth and Environmental Sciences** -- preserve geospatial references, climate model identifiers, temporal scale descriptors When summarizing across disciplines (interdisciplinary work), define domain-specific terms on first use and favor the terminology conventions of the primary discipline. ## Citation Handling ### In-Summary Citations - Preserve author-year citations from the source when referencing specific claims: "(Smith et al., 2024)" - When summarizing multiple papers, maintain consistent citation format throughout - Use numbered references [1], [2] when summarizing more than ten sources for readability - Always attribute quantitative claims to their source study ### Citation Integrity Rules - Never fabricate citations -- if a referenced work cannot be confirmed, note it as "cited by authors, not independently verified" - Preserve DOI links when available in the source material - Flag retracted or corrected papers when encountered during summarization - Distinguish between primary sources (original research) and secondary sources (reviews, textbooks) ### Reference List - Append a reference list at the end of systematic review summaries and literature review summaries - Use a consistent format (preferably matching the source discipline convention) - Include DOIs where available ## Output Templates ### Single Paper Summary Template ``` Title: [Paper Title] Authors: [Author List] Source: [Journal/Preprint Server, Year] DOI: [DOI if available] Summary Type: [Abstract-Style | Executive | Detailed] [Summary content organized by the selected type structure above] Key Metrics: [Primary quantitative results] Limitations Noted: [Major caveats] ``` ### Multi-Paper Synthesis Template ``` Topic: [Research Topic] Papers Reviewed: [Count] Date Range: [Earliest -- Latest publication] Synthesis Type: [Literature Review | Systematic Review | Meta-Analysis Overview] [Synthesis content organized by the selected type structure above] Agreement: [Points of consensus across studies] Disagreement: [Points of conflict or contradiction] Gaps: [Unanswered questions identified] References: [Numbered reference list] ``` ## Quality Criteria A good scientific summary must satisfy the following: 1. **Faithfulness** -- no claims that are not present in or directly supported by the source material 2. **Completeness** -- all major findings and caveats are represented, not just positive results 3. **Precision** -- quantitative results include exact values, units, confidence intervals, and p-values as reported 4. **Neutrality** -- avoids editorializing; reports what the authors found and claimed 5. **Clarity** -- readable by the target audience without losing scientific rigor 6. **Traceability** -- every claim can be traced back to its source document or section ## Zero-Hallucination Rule ALL factual claims, citations, database results, and scientific data presented to the user MUST come from actual tool results (API calls, code execution, web search) in this conversation. NEVER fabricate or "fill in" details from training data. If a tool returns no results or partial data, report exactly what happened.
Related Skills
scientific-summarization
Summarize and simplify scientific literature, educational content, and research papers
scienceclaw-verification
Verify scientific claims, check calculations, validate experimental designs, and fact-check citations. Use when: (1) checking a claim against evidence, (2) validating statistical analyses, (3) verifying experimental reproducibility claims, (4) fact-checking references, (5) adversarial review of research. NOT for: generating new content (use scienceclaw-generation), simple QA (use scienceclaw-qa).
scienceclaw-retrieval
Retrieve scientific information from databases, literature, and knowledge bases. Use when: (1) finding relevant papers, (2) querying scientific databases, (3) cross-referencing findings, (4) building bibliographies, (5) systematic literature search. NOT for: answering questions (use scienceclaw-qa), summarizing (use scienceclaw-summarization), or data analysis (use code-execution skill).
scienceclaw-reasoning
Perform multi-step scientific reasoning, proof construction, causal inference, and logical argumentation. Use when: (1) deriving conclusions from premises, (2) causal analysis, (3) mathematical proofs, (4) hypothesis evaluation, (5) counterfactual reasoning. NOT for: simple factual questions (use scienceclaw-qa), data analysis (use code-execution), or literature search (use scienceclaw-retrieval).
scienceclaw-qa
Answer scientific questions across all disciplines with evidence-based responses and citations. Use when: (1) user asks factual science questions, (2) needs explanation of concepts/theories/methods, (3) multi-step scientific reasoning needed. Covers natural sciences (physics, chemistry, biology, medicine, materials, astronomy, earth science, math, CS) and social sciences (economics, sociology, psychology, political science, linguistics, history, law, philosophy, education). NOT for: opinion-based questions, non-scientific queries, or when code execution is needed (use code-execution skill).
scienceclaw-prediction
Predict scientific properties, trends, and outcomes. Use when: user asks for property prediction, trend forecasting, or model-based estimation. NOT for: historical data lookup or real-time monitoring.
scienceclaw-ie
Extract structured information from scientific texts: entities, relations, data tables, methods, results. Use when: (1) parsing papers for key data, (2) extracting experimental parameters, (3) building knowledge graphs from literature, (4) NER on scientific documents, (5) extracting methods/results sections. NOT for: summarization (use scienceclaw-summarization), full text retrieval (use scienceclaw-retrieval).
scienceclaw-generation
Generate scientific hypotheses, experimental designs, and paper drafts. Use when: user asks to propose hypotheses, design experiments, or write scientific content. NOT for: data analysis or literature search.
scienceclaw-discovery
Identify research gaps, synthesize cross-disciplinary insights, and generate novel hypotheses. Use when: user asks about unexplored areas, cross-field connections, or new research directions. NOT for: routine literature review or data analysis.
scienceclaw-classification
Classify scientific content by discipline, methodology, topic, and quality. Use when: user asks to categorize papers, methods, or research outputs. NOT for: simple keyword tagging or non-scientific content.
xurl
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.