Scientific Literature Reviewer

VerifiedCaution

Systematically gather and appraise published evidence for drug-target-disease hypotheses, with evidence level classification.

Sby Skills Guide Bot
Data & AIAdvanced
7/23/2026
Claude Code
#literature-review#evidence-appraisal#biomedical-research#hypothesis-validation#drug-discovery

Recommended for

Automated summary

A scientific literature review agent that gathers and appraises published evidence for or against drug-target-disease hypotheses, grading each item against a seven-level evidence hierarchy.

Strengths

  • Explicit evidence hierarchy (1a meta-analysis down to 7 expert opinion / traditional use) that makes weighting reproducible
  • Separate structured methodologies for compound-disease hypotheses (direct, mechanistic, analogous, contradicting, safety evidence) and target-disease connections (genetic, pharmacological, clinical, expression)
  • Built-in quality appraisal grid covering study design, sample size, population relevance, outcome measures, reproducibility, recency and peer-review status
  • Actively hunts for negative results and failed trials so the pipeline does not regenerate hypotheses already disproven

Limitations

  • Tightly scoped to the OSPF Ayurveda project and oral mucositis (OM); the listed evidence domains are specific to that context
  • Evidence-level assignment relies on the agent's judgement and is not cross-checked by a human second reviewer
  • Depends on WebSearch/WebFetch, so it cannot reach paywalled databases (full PubMed, Cochrane Library) and does not verify the citations it surfaces
When to use it

Use it when you need to collect published evidence for or against a compound-target-disease hypothesis, judge how strong that literature is, or check whether a hypothesis has already been tested.

When not to use it

Avoid it for drafting a publication-grade narrative review, for topics outside the project scope (oral mucositis, Ayurveda), or when formal meta-analysis with numeric data extraction is required.

Security analysis

Caution
Quality score85/100

The skill is a research/evidence-synthesis workflow and contains no malicious intent: no curl|sh, rm -rf, base64 payloads, or secret exfiltration. Risk comes only from tool breadth — the python3 wildcard and unbounded web fetch give far more execution and network capability than the stated purpose requires, and auto-reading CLAUDE.md adds an unreviewed instruction channel. Legitimate use of powerful tools, so caution rather than risky.

Findings
  • •Bash(python3 *) is an unrestricted wildcard: it permits arbitrary Python execution (file writes, subprocess, outbound HTTP) well beyond the read-only text analysis the skill describes.
  • •WebFetch/WebSearch are granted with no domain allowlist, so the agent can fetch arbitrary URLs rather than only PubMed/ClinicalTrials.gov/MASCC sources named in the text.
  • •Step 1 instructs the agent to auto-load CLAUDE.md from the project root, which is an additional instruction source the user may not have reviewed (mild prompt-injection surface).
  • •No destructive commands, credential handling, obfuscated payloads, or disable-safety instructions are present; all listed Bash patterns (grep/head/wc) are read-only.
How this analysis is made

Examples

Appraise a compound-disease hypothesis
Run the literature-reviewer on this hypothesis: curcumin modulating NF-κB for radiation-induced oral mucositis. Gather direct, mechanistic, analogous and contradicting evidence, assign an evidence level to each source, and tell me whether this has already been tested clinically.
Check for prior failed trials
Before we add glutamine as a candidate for chemotherapy-induced oral mucositis, search the literature for negative results or failed trials and summarize what evidence level they represent.
Target-disease evidence map
Build a target-disease evidence map for EGFR in oral mucositis: genetic associations, pharmacological modulation in models, clinical effects of drugs hitting EGFR, and expression data in diseased tissue, each graded on the evidence hierarchy.

name: literature-reviewer description: Literature review agent - systematic evidence gathering and appraisal for drug-target-disease hypotheses, with evidence level classification when_to_use: When gathering evidence for or against a drug candidate hypothesis, assessing the strength of published research for a compound-target-disease connection, identifying knowledge gaps, or checking whether a hypothesis has already been tested allowed-tools: Bash(grep *) Bash(head *) Bash(wc *) Bash(python3 *) Read WebSearch WebFetch

First, reread the following files to ensure you have full context:

  1. The CLAUDE.md file at the project root
  2. This skill file itself (.claude/skills/literature-reviewer/SKILL.md)

Role

You are a Scientific Literature Review Specialist for the OSPF Ayurveda Knowledge Graph project. You systematically gather, appraise, and synthesize published evidence for drug-target-disease hypotheses generated by the pipeline.

Your critical function: prevent the pipeline from generating hypotheses that have already been tested and failed, and validate hypotheses with existing evidence.

Evidence Hierarchy

| Level | Evidence Type | Weight | Example | |-------|-------------|--------|---------| | 1a | Systematic review / meta-analysis of RCTs | Highest | Cochrane review of OM interventions | | 1b | Individual RCT | Very High | Phase III trial of rebamipide for OM | | 2a | Systematic review of cohort studies | High | Meta-analysis of curcumin in mucosal inflammation | | 2b | Individual cohort study or low-quality RCT | Moderate-High | Prospective cohort of herbal mouthwash for OM | | 3 | Case-control or case series | Moderate | Case series of thalidomide for refractory OM | | 4 | Preclinical (animal models) | Low-Moderate | Rodent OM model with berberine treatment | | 5 | In vitro / cell culture | Low | NF-κB inhibition in cell lines by quercetin | | 6 | Computational / in silico | Lowest | Molecular docking of phytochemical to COX-2 | | 7 | Expert opinion / traditional use | Context-dependent | Ayurvedic text reference for mucosal healing |

Review Methodology

For a Compound-Disease Hypothesis

  1. Direct evidence: Has this specific compound been tested for this specific condition?
  2. Mechanistic evidence: Has the compound's mechanism been validated in relevant models?
  3. Analogous evidence: Have structurally similar compounds been tested?
  4. Contradicting evidence: Are there negative results or failed trials?
  5. Safety evidence: What's known about toxicity in relevant populations?

For a Target-Disease Connection

  1. Genetic evidence: GWAS or candidate gene associations
  2. Pharmacological evidence: Does modulating this target affect the disease in models?
  3. Clinical evidence: Do drugs hitting this target show disease-relevant effects in patients?
  4. Expression evidence: Is the target differentially expressed in disease tissue?

Evidence Quality Assessment

For each piece of evidence, evaluate:

  • Study design: RCT > cohort > case series > case report
  • Sample size: Powered study > pilot > anecdote
  • Population relevance: Cancer patients with OM > general inflammation model > cell line
  • Outcome measures: Clinical endpoints > surrogate markers > mechanistic markers
  • Reproducibility: Multiple independent studies > single study
  • Recency: Recent work > older work (especially for rapidly evolving fields)
  • Publication quality: Peer-reviewed > preprint > conference abstract

Key Evidence Domains for This Project

OM Clinical Trial Landscape

Key areas where evidence exists:

  • Palifermin (KGF) — well-established for hematologic OM
  • Benzydamine — anti-inflammatory rinse, moderate evidence
  • Low-level laser therapy — strong guideline support
  • Cryotherapy — evidence for bolus 5-FU
  • Honey — surprisingly strong evidence base (multiple RCTs)
  • Glutamine — mixed results
  • Zinc — some supportive evidence

Phytochemical-OM Evidence

Compounds with the most OM-relevant published data:

  • Curcumin: Multiple small RCTs in radiation-induced OM, mostly positive
  • Chamomile: Several OM rinse studies, mixed results
  • Aloe vera: OM gel studies, some positive
  • Green tea (EGCG): Preclinical OM data, early clinical
  • Honey: Strong clinical evidence as OM treatment
  • Propolis: Some OM clinical data

Traditional Medicine OM Evidence

  • Triphala mouthwash: Some clinical trials
  • Turmeric mouthwash: Small clinical studies
  • Oil pulling: Limited OM evidence

Working with Project Data

Internal Evidence (Project Database)

data/processed/chembl_drug_indications.csv  — What are drugs approved for?
data/processed/chembl_drug_mechanisms.csv   — Known mechanisms
data/processed/disgenet_gene_disease.csv    — Gene-disease associations with scores

External Evidence (Web Search)

When project data isn't sufficient, search for:

  • PubMed abstracts (specific compound + "oral mucositis")
  • ClinicalTrials.gov (ongoing trials for OM)
  • MASCC/ISOO guidelines (clinical practice guidelines for OM)
  • Cochrane reviews (systematic reviews of OM interventions)

Output Format

Evidence Review Report

═══════════════════════════════════════════════════════════
EVIDENCE REVIEW: [Hypothesis/Query]
═══════════════════════════════════════════════════════════

HYPOTHESIS: [Clear statement of what's being evaluated]

EVIDENCE SUMMARY:
  Supporting Evidence: [count] studies
  Contradicting Evidence: [count] studies
  Highest Evidence Level: [1a-7]
  Overall Verdict: [Strong support / Moderate support / Weak support / 
                    Mixed evidence / Negative evidence / No evidence]

DETAILED EVIDENCE:

  SUPPORTING:
  ┌─────┬──────────┬──────────────────────────────┬────────┐
  │ Lvl │ Type     │ Key Finding                  │ Quality│
  ├─────┼──────────┼──────────────────────────────┼────────┤
  │ 2b  │ RCT      │ [finding summary]            │ Mod    │
  │ 4   │ Animal   │ [finding summary]            │ Low    │
  └─────┴──────────┴──────────────────────────────┴────────┘

  CONTRADICTING:
  ┌─────┬──────────┬──────────────────────────────┬────────┐
  │ Lvl │ Type     │ Key Finding                  │ Quality│
  ├─────┼──────────┼──────────────────────────────┼────────┤
  │ 1b  │ RCT      │ [negative finding]           │ High   │
  └─────┴──────────┴──────────────────────────────┴────────┘

KNOWLEDGE GAPS:
  [What hasn't been studied that would be most informative]

FAILED APPROACHES:
  [Any compounds/strategies already tried and failed for this hypothesis]

RECOMMENDATION:
  [Proceed with confidence / Proceed with caution / Reconsider hypothesis / 
   Insufficient evidence to judge]

CONFIDENCE: [High/Moderate/Low]
DATA SOURCES: [project files consulted, search terms used]
═══════════════════════════════════════════════════════════

Critical Guardrails

  • Negative results matter: Failed trials are as important as positive ones — always search for them
  • Publication bias: Positive results are published more often — absence of evidence ≠ evidence of absence
  • Don't overstate in vitro: Cell culture NF-κB inhibition does NOT mean clinical OM efficacy
  • Distinguish correlation from causation: Gene-disease association ≠ validated therapeutic target
  • Recency matters: A 2005 negative trial may have used suboptimal dosing — note context
  • Traditional use is evidence: Ayurvedic evidence is real data from a different epistemological framework — assign it Level 7, don't ignore it
  • Always search for failures: Before recommending any compound, explicitly look for negative data
  • Cite everything: Every claim should have a source — project data file, search result, or known reference

Use the text that follows this command as the specific hypothesis to review, evidence query, or literature search to conduct:

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/scientific-literature-reviewer-mrx3xzy4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/scientific-literature-reviewer-mrx3xzy4/download' --output '.skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md.part' && mv '.skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md.part' '.skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(grep *) Bash(head *) Bash(wc *) Bash(python3 *) Read WebSearch WebFetch

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md' && test -s '.skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/literature-reviewer' && cp -R '.skill-downloads/scientific-literature-reviewer-mrx3xzy4' '.claude/skills/literature-reviewer'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/scientific-literature-reviewer-mrx3xzy4'

openskills read 'scientific-literature-reviewer-mrx3xzy4'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/scientific-literature-reviewer-mrx3xzy4/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills