litreview
Literature review skill for academic, R&D, and professional research. Covers search strategy, source assessment (quality, relevance, recency), thematic synthesis, citation management, and the discipline of reproducible reviews. Use when conducting a systematic literature review, building a research bibliography, or preparing a research-grounded report.
What this skill does
# Literature Review A structured literature-review skill grounded in PRISMA-style protocols (adapted for non-medical fields), source-assessment frameworks, and thematic synthesis patterns. ## When to use this skill - Conducting a **systematic literature review** on a specific question - Building a **research bibliography** for a paper, report, or grant - Performing a **scoping review** to map a field - Auditing an existing review for **gaps, bias, or methodological flaws** - Synthesizing findings from a **structured set of sources** - Preparing a **research-grounded section** of a longer report ## Inputs the advisor expects - Research question(s) — specific, answerable - Inclusion / exclusion criteria - Time bound (e.g., past 5 years) - Geographic / domain bound - Source types accepted (peer-reviewed, gray literature, conference) - Existing seed sources (if any) ## Workflows ### Workflow 1 — Plan and execute the search 1. Refine the research question (PICO / PEO format works). 2. Run `search_strategy_builder.py` against the question + criteria to produce a search strategy (database list, queries, filters). 3. Execute searches; capture results. ```bash python3 litreview/scripts/search_strategy_builder.py \ --input question.json --format markdown ``` ### Workflow 2 — Score source quality and relevance 1. Capture each source with metadata (authors, date, venue, methodology). 2. Run `source_quality_scorer.py` to grade each on 6 quality dimensions + relevance to question. 3. Triage: include / exclude / read-in-full. ```bash python3 litreview/scripts/source_quality_scorer.py \ --input sources.json --format markdown ``` ### Workflow 3 — Synthesize findings into themes 1. Tag each source with themes + key findings. 2. Run `thematic_synthesis_builder.py` to cluster sources by theme, surface evidence strength, identify gaps. ```bash python3 litreview/scripts/thematic_synthesis_builder.py \ --input tagged_sources.json --format markdown ``` ## Decision frameworks ### Search strategy — the PICO frame - **P**opulation / problem - **I**ntervention / phenomenon of interest - **C**omparator (if relevant) - **O**utcome A well-framed question makes search and synthesis tractable. ### Inclusion / exclusion criteria - Year range - Language - Source type (peer-reviewed, gray, conference, preprint) - Methodology (empirical, theoretical, review) - Geographic scope - Quality threshold Publish criteria up front; apply consistently. ### Source quality dimensions | Dimension | Question | |-----------|----------| | Methodology | Is the method sound? | | Sample / dataset | Is it adequate for the claim? | | Peer review | Has it been peer-reviewed? | | Reproducibility | Is data / code available? | | Recency | Is it current? | | Citation impact | Has it been cited / accepted? | A single sub-dimension is rarely fatal; the combination matters. ### Synthesis approaches | Approach | When | |----------|------| | Narrative synthesis | Heterogeneous sources; explanatory | | Thematic synthesis | Multiple sources address common themes | | Meta-analysis | Quantitative, comparable studies | | Realist synthesis | Complex interventions; context-mechanism-outcome | | Scoping review | Mapping a field rather than answering specific question | For most non-clinical fields, **thematic synthesis** is the default. ## Common engagements ### "Help me build the literature review for my paper" 1. Frame the research question (PICO). 2. Define inclusion criteria. 3. Identify search databases / repositories. 4. Execute searches; deduplicate. 5. Screen titles + abstracts; full-text the candidates. 6. Tag and synthesize. 7. Write: gaps, themes, my contribution. ### "Audit my draft literature review" 1. Check the search strategy: reproducible? comprehensive? 2. Check inclusion criteria: applied consistently? 3. Check synthesis: themes substantiated? 4. Check gap identification: real gaps, or convenient? 5. Check citation balance: not over-relying on a single source / group. ### "Map the landscape of [research area]" 1. Conduct a scoping review (different from systematic). 2. Less stringent quality criteria; broader scope. 3. Goal: map the field, not answer specific question. 4. Output: themes, gaps, key authors, key venues. ## Anti-patterns to avoid - **Search strategy that's "Google Scholar for keywords."** Not reproducible. - **Inclusion criteria written after seeing results.** Cherry-picking. - **Synthesizing only confirming sources.** Bias. - **Citing without reading.** Cite chains repeat errors. - **No quality scoring.** All sources weighted equally. - **No gap discussion.** Reader can't see what's not known. - **Over-reliance on one author / group / venue.** Hidden bias. - **No PRISMA-style flow diagram (for systematic reviews).** Process opaque. ## References - `references/search-strategy-and-prisma.md` — search patterns, PRISMA discipline - `references/source-quality-assessment.md` — quality dimensions, common assessments - `references/synthesis-and-citation-management.md` — synthesis approaches, citation hygiene ## Related skills - `research/grants` — grant proposals built on literature - `research/patent` — IP-focused literature search - `research/dossier` — intelligence research patterns - `product-team/research-summarizer` — synthesizing qualitative research
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.