analyzing-research-papers
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
Best use case
analyzing-research-papers is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
Teams using analyzing-research-papers 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/analyzing-research-papers/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyzing-research-papers Compares
| Feature / Agent | analyzing-research-papers | 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?
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
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.
SKILL.md Source
# Analyzing Research Papers
This skill provides expertise in systematically analyzing research papers to extract key insights, evaluate methodological rigour, and contextualize findings for researchers.
## Paper Access Methods
### Input Formats Accepted
**Local files:**
- Absolute paths: `/path/to/paper.pdf`
- Relative paths: `./papers/smith2024.pdf`
- Markdown files: `paper.md`
**DOIs:**
- Standard format: `10.1234/journal.2024.12345`
- With prefix: `doi:10.1234/journal.2024.12345`
- Resolve using: `https://doi.org/{doi}`
**URLs:**
- ArXiv: `https://arxiv.org/pdf/2301.12345.pdf`
- Journal websites: Direct PDF or HTML links
- Preprint servers: bioRxiv, medRxiv, etc.
### Handling Access Issues
**Paywalled content:**
- Work with available abstract and metadata
- Extract what's publicly accessible
- Note limitations in summary
- Suggest open access alternatives
**PDF reading failures:**
- Request text version if available
- Try alternative formats (HTML, arXiv)
- Extract from DOI metadata
## Analysis Framework
### Initial Scan
**Identify paper structure:**
- Abstract and key claims
- Section organization (IMRaD vs custom)
- Figures and tables overview
- Reference density and key citations
**Classify paper type:**
- Theory: Proofs, mathematical foundations, formal results
- Methods: New algorithms, techniques, computational approaches
- Application: Domain-specific use cases, case studies
- Review: Surveys, systematic reviews, meta-analyses
- Empirical: Experimental results, observations, measurements
### Content Extraction Priorities
**Must extract:**
1. Main contribution(s) and claims
2. Methodological approach and assumptions
3. Key results with statistical evidence
4. Limitations acknowledged
5. Related work positioning
**Important to capture:**
- Experimental setup and validation
- Implementation details
- Performance metrics and comparisons
- Dataset characteristics
- Reproducibility information
**Nice to have:**
- Future work suggestions
- Broader implications
- Alternative approaches considered
- Failure modes discussed
## Quality Assessment Criteria
### Methodological Rigour
**Strong indicators:**
- Clear research questions
- Appropriate methodology for questions
- Controlled comparisons
- Statistical significance properly assessed
- Limitations openly discussed
- Assumptions explicitly stated
**Weak indicators:**
- Vague objectives
- Methodology not justified
- Cherry-picked results
- Over-claiming based on limited evidence
- Ignoring contrary evidence
- Unacknowledged assumptions
### Reproducibility Assessment
**High reproducibility:**
- Code publicly available
- Data accessible or well-described
- Implementation details complete
- Hyperparameters specified
- Random seeds provided
- Environment documented
**Low reproducibility:**
- "Implementation details omitted for brevity"
- No code or data shared
- Vague parameter descriptions
- Critical details missing
- Non-standard methods without explanation
### Impact Potential
**High impact indicators:**
- Addresses important problem
- Novel approach or insight
- Strong empirical results
- Generalizable beyond specific case
- Clear practical applications
- Challenges existing assumptions
**Limited impact indicators:**
- Incremental improvement
- Narrow applicability
- Limited novelty
- Weak empirical support
- Unclear practical value
## Analysis Structure
### Overview Section
**Synthesize (2-3 paragraphs):**
- What problem does this address?
- What's the main contribution?
- What's the key finding or result?
- Why does this matter?
### Highlights (Bullet Points)
**Extract:**
- Most important findings
- Key methodological innovations
- Surprising or counter-intuitive results
- Practical implications
- Limitations to be aware of
### Strengths Assessment
**Methodological strengths:**
- Rigorous experimental design
- Appropriate statistical analysis
- Comprehensive evaluation
- Clear presentation
**Impact strengths:**
- Novel contributions
- Practical applicability
- Theoretical insights
- Reproducibility support
### Weaknesses Assessment
**Be specific and fair:**
- Methodological limitations
- Scope constraints
- Unclear explanations
- Missing comparisons
- Reproducibility concerns
- Over-claims not supported by evidence
**Distinguish:**
- Fundamental flaws (invalidate conclusions)
- Important limitations (affect interpretation)
- Minor issues (don't affect main findings)
## Section-by-Section Analysis
### Introduction
**Extract:**
- Problem motivation and importance
- Research gap being addressed
- Main research questions
- Contributions claimed
- Paper organization
**Assess:**
- Is motivation convincing?
- Is gap clearly identified?
- Are claims appropriately scoped?
### Methods/Approach
**Extract:**
- Core methodology or algorithm
- Key design decisions and rationale
- Assumptions made (explicit and implicit)
- Implementation details
- Parameters and configurations
**Assess:**
- Is approach well-justified?
- Are assumptions reasonable?
- Is description complete enough to reproduce?
- Are limitations acknowledged?
### Results/Experiments
**Extract:**
- Experimental setup
- Datasets or scenarios used
- Metrics and evaluation criteria
- Main findings with numbers
- Statistical significance
- Comparison with baselines
**Assess:**
- Are experiments well-designed?
- Are comparisons fair?
- Are results presented clearly?
- Is statistical analysis appropriate?
- Are claims supported by evidence?
### Discussion/Conclusion
**Extract:**
- Interpretation of results
- Broader implications
- Limitations discussed
- Future work suggested
- Take-home messages
**Assess:**
- Are interpretations justified?
- Are limitations honestly addressed?
- Are broader claims supported?
## Technical Detail Extraction
### For Methods Papers
**Capture:**
- Algorithm pseudocode or description
- Computational complexity
- Key equations and formulations
- Implementation strategies
- Performance characteristics
### For Theory Papers
**Capture:**
- Main theorems and proofs structure
- Assumptions and their necessity
- Formal definitions
- Theoretical guarantees
- Connections to prior work
### For Application Papers
**Capture:**
- Domain context and requirements
- Data characteristics
- Specific challenges addressed
- Real-world constraints
- Practical validation
### For Review Papers
**Capture:**
- Taxonomy or classification used
- Coverage scope
- Trends identified
- Gaps in literature
- Research directions suggested
## Related Work Contextualization
### Positioning
**Identify:**
- Key related papers cited
- How this work differs
- What gaps it fills
- Which results it extends
- Where it fits in research trajectory
**Assess:**
- Is related work coverage adequate?
- Are comparisons fair?
- Are important works cited?
- Is novelty clearly established?
## Output Format Template
```markdown
# Paper Summary: [Title]
**Authors**: [All authors]
**Year**: [Year]
**Venue**: [Journal/Conference]
**DOI/URL**: [Link]
## Overview
[2-3 paragraph synthesis]
## Highlights
- [Finding 1]
- [Finding 2]
- [Finding 3]
## Strengths
- [Strength 1]
- [Strength 2]
## Weaknesses
- [Limitation 1]
- [Concern 2]
## Detailed Summary
### Introduction
[Problem, gap, contributions]
### Methods
[Approach, algorithms, assumptions]
### Results
[Findings, metrics, comparisons]
### Discussion
[Interpretation, implications]
## Technical Details
[Implementation specifics, equations, parameters]
## Related Work Context
[How this fits in the literature]
## Potential Applications
[Practical uses]
## Reproducibility Notes
[Code, data, reproducibility assessment]
```
## Special Considerations by Field
### Machine Learning/AI
- Architecture details and hyperparameters
- Training procedures and convergence
- Dataset characteristics and splits
- Ablation studies
- Computational requirements
- Generalization evidence
### Statistics/Biostatistics
- Model specification and assumptions
- Prior choices and justification
- Identifiability and inference
- Sensitivity analyses
- Missing data handling
- Validation approach
### Epidemiology/Public Health
- Study design and population
- Exposure and outcome definitions
- Confounding adjustment
- Causal interpretation
- Generalizability
- Public health implications
### Computational Biology
- Biological context and motivation
- Data sources and preprocessing
- Validation with known biology
- Biological interpretation
- Reproducibility with data/code
## When to Use This Skill
Apply this analysis approach when:
- Reading papers for literature review
- Evaluating methods for adoption
- Assessing novelty for research direction
- Extracting technical details for implementation
- Preparing paper summaries for team
- Reviewing papers for journal/conference
- Building bibliography with annotations
Extract insights efficiently whilst maintaining critical assessment.
Provide researchers with actionable understanding of papers' contributions and relevance.Related Skills
api-researcher
Expert API research including discovery, evaluation, integration analysis, and documentation review
analyzing-user-feedback
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
analyzing-unknown-codebases
Analyze unfamiliar codebases systematically to produce subsystem catalog entries - emphasizes strict contract compliance and confidence marking
analyzing-text-patterns
Extract and analyze recurring patterns from log messages, span names, and event names using punctuation-based template discovery. Use when you need to understand log diversity, identify common message structures, detect unusual formats, or prepare for log parser development. Works by removing variable content and preserving structural markers.
analyzing-taint-flow
Tracks untrusted input propagation from sources to sinks in binary code to identify injection vulnerabilities. Use when analyzing data flow, tracing user input to dangerous functions, or detecting command/SQL injection.
Analyzing Spreadsheets
Analyzes Excel spreadsheets, summarizes trends, and recommends charts when users mention spreadsheets, Excel workbooks, or .xlsx files.
analyzing-projects
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"
analyzing-patterns
Automatically activated when user asks to "find patterns in...", "identify repeated code...", "analyze the architecture...", "what design patterns are used...", or needs to understand code organization, recurring structures, or architectural decisions
analyzing-logs
Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".
analyzing-implementations
Documents HOW code works with surgical precision - traces data flow, explains implementation details, provides file:line references. Purely documentarian, no critiques or suggestions for improvement.
analyzing-funding-landscape
Analyzes venture capital, investment trends, funding rounds, investor strategies, M&A activity, and funding patterns in specific markets or industries. Use when the user requests funding analysis, VC landscape research, investment trend analysis, or wants to understand investor activity and funding dynamics.
analyzing-frontend-layer
Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)