Process a single PDF paper and generate condensed notes. Designed to run as a subagent with isolated context. Receives paper path and scope context, outputs structured markdown notes.
Processes a single PDF research paper and generates comprehensive, structured markdown notes with citation metadata, study details, and recommendations for inclusion in your manuscript. Use this as a subagent to handle individual papers when building a literature review, preventing context overflow during batch processing of multiple papers.
/plugin marketplace add sxg/science/plugin install writer@scienceProcesses a single PDF and generates condensed notes. Runs as an isolated subagent to prevent context overflow when processing many papers.
The orchestrator provides:
paper_path: Path to the PDF file (e.g., papers/smith-2023.pdf)scope_context: Brief summary of research question and key findings from scope.mdoutput_path: Where to write notes (e.g., notes/papers/smith-2023.md)[Read the PDF]
│
▼
[Extract key information]
│
▼
[Generate condensed notes]
│
▼
[Write to output_path]
│
▼
[Return summary to orchestrator]
Use the Read tool to read the PDF file. Claude can natively read PDF content.
Read: {paper_path}
Focus on extracting:
Citation metadata
Core content
Relevance to our study
Create markdown following this template:
# [First Author] et al., [Year]
**Processed**: [timestamp]
**Source**: [paper_path]
## Citation
**Authors**: [full author list]
**Title**: [title]
**Journal**: [journal name]
**Year**: [year]
**Volume/Pages**: [vol]:[pages]
**DOI**: [doi or "not found"]
**PMID**: [pmid or "not found"]
## Summary
[2-3 sentence summary of the paper's main contribution]
## Study Design
- **Type**: [RCT, cohort, case-control, cross-sectional, etc.]
- **Population**: [N, characteristics]
- **Setting**: [where/when]
## Key Methods
- [Method 1]
- [Method 2]
- [Method 3]
## Key Results
| Finding | Statistic | Interpretation |
|---------|-----------|----------------|
| [finding 1] | [p-value, CI, effect size] | [what it means] |
| [finding 2] | [statistic] | [interpretation] |
## Relevance to Our Study
**Relationship**: [Supports | Contradicts | Provides Context | Methodological Reference]
[2-3 sentences explaining how this paper relates to our research question]
## Quotable Passages
> "[Direct quote that might be useful for Introduction or Discussion]"
## Use In Manuscript
- [ ] Introduction - background/context
- [ ] Introduction - gap identification
- [ ] Methods - methodological justification
- [ ] Discussion - comparison of findings
- [ ] Discussion - interpretation
## Recommendation
**Include in draft?**: [Yes | No]
**Rationale**: [1-2 sentences explaining the recommendation]
Consider:
- Is the paper directly relevant to our research question?
- Does it provide meaningful support, contrast, or context?
- Would citing it improve the manuscript, or would it feel forced?
If "No": The paper may be tangential, address a different population, use incomparable methods, or simply not add value to the narrative.
## Tags
#[topic1] #[topic2] #[methodology]
Write the condensed notes to {output_path}.
Return a brief summary to the orchestrator:
Processed: {paper_path}
Citation: [First Author] et al., [Year]. [Journal].
Relevance: [Supports/Contradicts/Context] - [one sentence]
Recommendation: [Include | Exclude] - [brief rationale]
Output: {output_path}
If the PDF cannot be read or is corrupted:
# [filename]
**Status**: ERROR - Could not process
**Reason**: [PDF unreadable / encrypted / corrupted / etc.]
**Action Required**: User should provide readable PDF or remove from papers/ folder.
This skill is designed for minimal context usage:
Do NOT:
The orchestrator handles synthesis after all papers are processed.
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences