literature-review
Conduct comprehensive literature reviews using multi-perspective dialogue simulation. Generate diverse expert personas, conduct grounded Q&A conversations, and synthesize findings into structured knowledge. Use when starting a new research project or writing a survey section.
What this skill does
# Literature Review Conduct deep literature reviews through multi-perspective dialogue and systematic search. ## Input - `$0` — Research topic or question - `$1` — Optional: specific focus or angle ## References - Multi-perspective dialogue prompts (STORM): `~/.claude/skills/literature-review/references/dialogue-prompts.md` - Literature review workflow (AgentLaboratory): `~/.claude/skills/literature-review/references/review-workflow.md` ## Scripts (from literature-search skill) ```bash # Search Semantic Scholar python ~/.claude/skills/deep-research/scripts/search_semantic_scholar.py --query "topic" --max-results 20 # Search OpenAlex python ~/.claude/skills/literature-search/scripts/search_openalex.py --query "topic" --max-results 20 # Search arXiv python ~/.claude/skills/deep-research/scripts/search_arxiv.py --query "topic" --max-results 10 ``` ## Workflow ### Step 1: Generate Expert Personas (from STORM) Given the topic, create 3-5 diverse expert personas: - Each represents a different perspective, role, or research angle - Example: "ML systems researcher focused on efficiency", "Theoretical statistician concerned with guarantees" - Use the persona generation prompts from references ### Step 2: Multi-Perspective Dialogue For each persona, simulate a multi-turn Q&A conversation: 1. **Persona asks a question** from their unique angle 2. **Generate search queries** from the question 3. **Search literature** using the search scripts 4. **Synthesize an answer** grounded in retrieved papers with inline citations 5. **Record the dialogue turn** with search results 6. Repeat for 3-5 turns per persona 7. End when persona says "Thank you so much for your help!" ### Step 3: Synthesize Knowledge - Combine all persona conversations into a unified knowledge base - Remove redundancy across personas - Organize by theme/subtopic - Generate an outline based on the collected information ### Step 4: Generate Literature Review - Write a structured review organized by the generated outline - Every claim must be supported by a citation - Include a summary table of key papers (method, contribution, limitations) ## Output A structured literature review with: 1. **Outline** — Hierarchical topic structure 2. **Per-section summaries** — Each grounded in retrieved papers 3. **Paper database** — Structured entries for all reviewed papers 4. **Knowledge gaps** — Identified areas needing further investigation ## Rules - Every sentence in the review must be supported by gathered information - If information is not found, explicitly state the gap - Cite broadly — cover diverse approaches, not just the most popular - Include recent papers (last 2-3 years) alongside foundational work - Use inline citations: "Smith et al. [1] propose..." ## Related Skills - Upstream: [literature-search](../literature-search/), [deep-research](../deep-research/) - Downstream: [related-work-writing](../related-work-writing/), [research-planning](../research-planning/) - See also: [survey-generation](../survey-generation/)
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.