literature-review
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
npx skills add BioTender-max/awesome-bio-agent-skills --skill literature-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Literature Review ## Overview Conduct systematic, comprehensive literature reviews following rigorous academic methodology. Search multiple literature databases, synthesize findings thematically, verify all citations for accuracy, and generate professional output documents in markdown and PDF formats. This skill uses the **parallel-web skill** (`parallel-cli search`) as the primary web search tool for broad academic literature discovery, supplemented by specialized database access skills (gget, bioservices, datacommons-client). It provides specialized tools for citation verification, result aggregation, and document generation. ## When to Use This Skill Use this skill when: - Conducting a systematic literature review for research or publication - Synthesizing current knowledge on a specific topic across multiple sources - Performing meta-analysis or scoping reviews - Writing the literature review section of a research paper or thesis - Investigating the state of the art in a research domain - Identifying research gaps and future directions - Requiring verified citations and professional formatting ## Visual Enhancement with Scientific Schematics **⚠️ MANDATORY: Every literature r
- Overview
- When to Use This Skill
- Visual Enhancement with Scientific Schematics
- Core Workflow
- Phase 1: Planning and Scoping
- Phase 2: Systematic Literature Search
- Phase 3: Screening and Selection
- Phase 4: Data Extraction and Quality Assessment
- Phase 5: Synthesis and Analysis
- Phase 6: Citation Verification
- Phase 7: Document Generation
- Database-Specific Search Guidance
- PubMed / PubMed Central
- bioRxiv / medRxiv
python scripts/generate_schematic.py "your diagram description" -o figures/output.png parallel-cli search "your research topic" -q "keyword1" -q "keyword2" \ parallel-cli extract "https://arxiv.org/abs/XXXX.XXXXX" --json python search_databases.py combined_results.json \ python search_databases.py results.json --deduplicate --output unique_results.json cp assets/review_template.md my_literature_review.md python scripts/verify_citations.py my_literature_review.md python scripts/generate_pdf.py my_literature_review.md \ Search PubMed gget search pubmed "CRISPR gene editing" -l 100
What does the literature-review skill do?
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill literature-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.