Claude Prompt Library

30 Claude prompts for honest systematic reviews

30 copy-paste prompts

Draft PICO, PRISMA-style protocols, search strings, screening forms, and extraction tables. You screen every record. Claude does not invent included studies.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

Protocol and PICO

5 prompts

Draft a PRISMA-style protocol

1/30

✨ What it does

Claude drafts a PRISMA-style protocol for [REVIEW QUESTION] with PICO, eligibility, and a search plan. You do not invent 12 included trials; register only after you own every field.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I am writing a PRISMA-style protocol for a systematic review. Claude drafts. I own eligibility, search, screening, and any later included set. </context> <task> Draft a protocol I can edit, covering: (1) title and review type, (2) PICO or named alternative, (3) eligibility, (4) information sources and date limits, (5) draft search concept map, (6) screening and dual-review plan, (7) data items, (8) risk-of-bias tool, (9) synthesis plan, (10) what must stay UNKNOWN until I supply it. </task> <inputs> REVIEW_QUESTION: [REVIEW QUESTION] POPULATION: [POPULATION] INTERVENTION_OR_EXPOSURE: [INTERVENTION] COMPARATOR: [COMPARATOR] OUTCOMES: [OUTCOMES] SETTING: [SETTING] STUDY_DESIGNS: [STUDY DESIGNS] TEAM: [REVIEW TEAM] </inputs> <constraints> - Do not invent included studies, NCT numbers, author names, or effect sizes. - Do not invent a PROSPERO or OSF ID. - If a field is unknown, write UNKNOWN and say what I must supply. - This draft is not a registered protocol. </constraints> <output> Numbered protocol sections plus a one-page checklist of fields I must lock before registration. </output>

💡

Pro tip: Lock PICO and eligibility before you write search strings. A moving question produces a moving, unreproducible search.

Turn a topic into PICO

2/30

✨ What it does

Claude turns [TOPIC] into a PICO question with population, intervention, comparator, and outcomes you can search. You screen the PICO against studies you can actually retrieve.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> My topic is still loose. I need a searchable PICO (or PECO/SPIDER if PICO is the wrong frame) before I touch databases. </context> <task> Rewrite [TOPIC] as: (1) one primary review question, (2) PICO elements with inclusion notes, (3) 2 narrower and 1 broader fallback questions, (4) outcomes split into critical vs important, (5) what this question cannot answer. </task> <inputs> TOPIC: [TOPIC] POPULATION_HINT: [POPULATION] WHAT_I_WANT_TO_COMPARE: [INTERVENTION] versus [COMPARATOR] OUTCOMES_I_CARE_ABOUT: [OUTCOMES] CONSTRAINTS: [DATE RANGE], [SETTING], [LANGUAGE] </inputs> <constraints> - Do not invent a body of evidence that already answers the question. - If PICO is a poor fit, say so and propose PECO or SPIDER instead of forcing RCT language. - Mark any element that is still too vague to search. </constraints> <output> A PICO table, the primary question in one sentence, and a short note on what I must decide next. </output>

💡

Pro tip: If you cannot name who, what, versus what, and which outcome, you are not ready to search.

Write eligibility criteria

3/30

✨ What it does

Claude writes inclusion and exclusion rules for [POPULATION] and [INTERVENTION], including designs and settings. You screen a sample of records against those rules before you lock them.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need inclusion and exclusion rules that two screeners can apply the same way. </context> <task> Write eligibility for [POPULATION] and [INTERVENTION]: (1) include / exclude rows for population, intervention or exposure, comparator, outcomes, design, setting, language, date, (2) borderline examples, (3) a one-line decision rule for each borderline, (4) what belongs in a later scoping review instead. </task> <inputs> POPULATION: [POPULATION] INTERVENTION: [INTERVENTION] COMPARATOR: [COMPARATOR] OUTCOMES: [OUTCOMES] STUDY_DESIGNS: [STUDY DESIGNS] SETTING: [SETTING] DATE_RANGE: [DATE RANGE] LANGUAGE: [LANGUAGE] </inputs> <constraints> - Do not invent example papers or trial IDs. - Prefer operational rules (age band, dose, follow-up) over adjectives like high quality. - Flag any rule that needs a medical or subject-matter call I have not made. </constraints> <output> A two-column include/exclude table plus 8 borderline cases labeled INCLUDE, EXCLUDE, or ASK TEAM. </output>

💡

Pro tip: Pilot the form on 50 titles before you screen the full set. Rules that look clean on paper fail on the first messy abstract.

Choose PICO, PECO, or SPIDER

4/30

✨ What it does

Claude picks PICO, PECO, or SPIDER for [STUDY DESIGN] and [REVIEW QUESTION] when a simple RCT frame does not fit. You do not invent 6 eligible designs the question cannot support.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> A classic RCT PICO may be the wrong frame for [STUDY DESIGN] and [REVIEW QUESTION]. I need the right question structure, not a forced trial template. </context> <task> Recommend PICO, PECO, SPIDER, or another named frame. Give: (1) why it fits, (2) the filled elements, (3) eligibility changes the frame implies, (4) synthesis limits (when meta-analysis is the wrong promise), (5) what I still must decide. </task> <inputs> REVIEW_QUESTION: [REVIEW QUESTION] STUDY_DESIGN: [STUDY DESIGN] POPULATION: [POPULATION] PHENOMENON_OR_EXPOSURE: [INTERVENTION] CONTEXT: [SETTING] </inputs> <constraints> - Do not invent a set of eligible designs or a count of available studies. - If the question is qualitative, do not pretend GRADE-for-RCTs is the default. - Say UNKNOWN where I have not named a design filter. </constraints> <output> Recommended frame, filled table, and a 6-line note on what a later synthesis can and cannot claim. </output>

💡

Pro tip: Name the design you will accept before you search. Mixing trials and lived-experience studies without a plan breaks screening.

Fill registration fields as a draft

5/30

✨ What it does

Claude fills PROSPERO-style fields for [REVIEW TEAM] and [REVIEW QUESTION] as a draft, not a filing. You do not invent a registration ID or a start date you have not set.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I want a filled worksheet for a registry (PROSPERO-style or OSF). This is a draft. It is not a submission and not a substitute for a registered protocol. </context> <task> Fill registration-style fields from my inputs: title, reviewers, start date if I gave one, PICO, eligibility, sources, conflicts, and a data-management note. Mark every field I did not supply as UNKNOWN. List what I must lock before I file. </task> <inputs> REVIEW_TEAM: [REVIEW TEAM] REVIEW_QUESTION: [REVIEW QUESTION] ANTICIPATED_START: [START DATE OR UNKNOWN] FUNDING: [FUNDING OR NONE] CONFLICTS: [CONFLICTS OR NONE] WHERE_I_MIGHT_REGISTER: [PROSPERO / OSF / OTHER] </inputs> <constraints> - Do not invent a registration number, DOI, or filing date. - Do not claim the protocol is registered. - Do not invent team roles I did not name. </constraints> <output> A field-by-field draft plus a stop list of items that would make a filing dishonest. </output>

💡

Pro tip: Register before you finish screening. Filing after you already know the included set is the fastest way to lose trust.

Search Strings

5 prompts

Build a PubMed Boolean string

6/30

✨ What it does

Claude writes a PubMed Boolean string for [POPULATION], [INTERVENTION], and [OUTCOME] with synonyms and MeSH. You do not invent 400 hits; you run the string and save the real count.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need a transparent PubMed search I can paste, run, and save. I will run it. You will not invent a hit count. </context> <task> Write a PubMed search for [POPULATION], [INTERVENTION], and [OUTCOME]: (1) concept blocks with synonyms, (2) MeSH where a heading is likely, marked as suggested not confirmed, (3) Boolean string with line numbers, (4) filters I should apply only after I see the raw yield, (5) a PRESS-style self-check of missing synonyms. </task> <inputs> POPULATION: [POPULATION] INTERVENTION: [INTERVENTION] COMPARATOR: [COMPARATOR] OUTCOME: [OUTCOME] DATE_RANGE: [DATE RANGE] LANGUAGE: [LANGUAGE] KNOWN_SEED_PAPERS: [SEED TITLES I ALREADY HAVE] </inputs> <constraints> - Do not invent n hits, PMIDs, or that a MeSH heading exists if you are unsure. Label suggestions as SUGGESTED. - Do not invent that seed papers are retrieved until I run the string. - Keep the string copy-pasteable. </constraints> <output> Line-numbered PubMed strategy, then a short note on what I must test and save (date, interface, yield). </output>

💡

Pro tip: Save the exact string, interface, and date with the yield. A string you cannot rerun is not a systematic search.

Translate the string across databases

7/30

✨ What it does

Claude translates your string for [DATABASE LIST] with syntax notes per database. You extract the working string from each platform after you test it.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I have a working concept map or PubMed string. I need honest translations for [DATABASE LIST], not a claim that each one already ran. </context> <task> Translate the search for each database in [DATABASE LIST]: syntax notes (quotes, truncation, field tags), a draft string, and what I must re-check in that interface. Do not invent yields. </task> <inputs> SOURCE_STRING: [SEARCH STRING] DATABASE_LIST: [DATABASE LIST] CONCEPT_BLOCKS: [POPULATION]; [INTERVENTION]; [OUTCOME] DATE_RANGE: [DATE RANGE] </inputs> <constraints> - Do not invent that a field tag or subject heading exists in a database you are unsure about. Mark those lines SUGGESTED. - Do not invent n unique records after dedup. - If a database needs a human to click filters, say so. </constraints> <output> One subsection per database: draft string, syntax notes, and a test checklist. </output>

💡

Pro tip: Run each translation once and capture the yield before you edit. Silent tweaks make the methods section a lie.

Plan grey literature sources

8/30

✨ What it does

Claude plans grey sources for [REVIEW QUESTION], including registries, theses, and agency reports. You screen those sources yourself and do not invent 9 unpublished trials.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> Database search alone will miss registries, theses, and agency reports. I need a grey-literature plan I will execute. </context> <task> For [REVIEW QUESTION], propose: (1) trial registries to search, (2) thesis portals, (3) agency or HTA sites, (4) conference sources, (5) a one-line method for each (search terms, date, what to export), (6) how I will log misses. Do not invent reports. </task> <inputs> REVIEW_QUESTION: [REVIEW QUESTION] POPULATION: [POPULATION] INTERVENTION: [INTERVENTION] GEOGRAPHY: [SETTING] DATE_RANGE: [DATE RANGE] </inputs> <constraints> - Do not invent unpublished trials, registry IDs, or that a report exists. - Prefer named source types I can actually open over a vague web search. - Say when grey search is unlikely to change the question. </constraints> <output> A table: source, why, draft terms, what I will save, and a blank yield column for me. </output>

💡

Pro tip: Search ClinicalTrials.gov and a thesis portal even when you expect nothing. Empty grey search still belongs in PRISMA.

PRESS-style search peer review

9/30

✨ What it does

Claude peer-reviews [SEARCH STRING] in a PRESS-style checklist and proposes a tighter revision. You screen the revision in a real database before you adopt it.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need a PRESS-style critique of [SEARCH STRING] before I lock the strategy. I will re-run any revision. </context> <task> Peer-review the string: (1) missing synonyms or spelling variants, (2) Boolean or nesting errors, (3) over-narrow filters, (4) lines that look copied from another question, (5) a revised string, (6) what I must test against [SEED TITLES I ALREADY HAVE]. </task> <inputs> SEARCH_STRING: [SEARCH STRING] REVIEW_QUESTION: [REVIEW QUESTION] SEED_TITLES: [SEED TITLES I ALREADY HAVE] DATABASE: [DATABASE] </inputs> <constraints> - Do not invent that seed titles are retrieved until I run the revision. - Do not invent a new hit count. - If you cannot see a concept in the string, say it is missing rather than assuming I searched it. </constraints> <output> PRESS-style findings, then a revised line-numbered string and a three-item test I must run. </output>

💡

Pro tip: Ask a second human to read the string too. PRESS is a peer review of the search, not a solo chat.

Plan de-duplication and limits

10/30

✨ What it does

Claude writes a de-duplication and date-limit plan for exports from [DATABASES] and [DATE RANGE]. You extract unique records from your own export, not from a guessed n.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will export from [DATABASES] for [DATE RANGE]. I need a de-duplication and limit plan that matches PRISMA counting. </context> <task> Write: (1) what to export from each database, (2) how to de-duplicate (tool and match rules), (3) when to apply date or language limits, (4) how to record n identified, n after duplicates, n screened, (5) a blank PRISMA count sheet I will fill. </task> <inputs> DATABASES: [DATABASES] DATE_RANGE: [DATE RANGE] REFERENCE_MANAGER: [ZOTERO / ENDNOTE / OTHER] LANGUAGE: [LANGUAGE] </inputs> <constraints> - Do not invent n identified or n after dedup. - Leave every count as a blank I will fill from the export. - Do not invent that a manager setting exists if I did not name the tool. </constraints> <output> A step list plus a PRISMA count sheet with blanks, not numbers. </output>

💡

Pro tip: Fill PRISMA boxes from the export log the same day you search. Reconstructed counts a month later are usually wrong.

Screening

5 prompts

Build a title-abstract screening form

11/30

✨ What it does

Claude builds a title and abstract screening form from [ELIGIBILITY CRITERIA] with include, exclude, and maybe. You screen every record; Claude only drafts the form.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need a screening form two people can use on titles and abstracts. I will apply it. You will not mark include on records I have not shown you. </context> <task> Turn [ELIGIBILITY CRITERIA] into a form: (1) ordered questions that stop at the first hard exclude, (2) include / exclude / maybe codes, (3) a maybe rule, (4) fields for reason and screener ID, (5) a 10-row blank log. </task> <inputs> ELIGIBILITY_CRITERIA: [ELIGIBILITY CRITERIA] REVIEW_QUESTION: [REVIEW QUESTION] SECOND_SCREENER: [YES / NO] </inputs> <constraints> - Do not invent records or decide include on papers I did not paste. - Keep questions answerable from a title and abstract alone. - If an item needs full text, move it off this form. </constraints> <output> The form, a one-page codebook, and a blank log I can copy into a sheet. </output>

💡

Pro tip: Keep maybe cheap. Over-including at abstract stage is cheaper than missing a paper you cannot recover later.

Resolve dual-screener conflicts

12/30

✨ What it does

Claude logs dual-screener conflicts from [DISAGREED RECORDS] and lists the rule each conflict tests. You screen those conflicts and record the final call.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> Two screeners disagreed. I need a conflict log and a rule test, not a silent override. </context> <task> From [DISAGREED RECORDS], for each row: (1) what the disagreement is about, (2) which eligibility rule it tests, (3) a suggested discussion prompt, (4) a recommended default only if the rule is already clear, else ASK TEAM. I make the call. </task> <inputs> DISAGREED_RECORDS: [DISAGREED RECORDS] ELIGIBILITY_CRITERIA: [ELIGIBILITY CRITERIA] SCREENER_NOTES: [SCREENER NOTES] </inputs> <constraints> - Do not invent a record that is not in the paste. - Do not invent an include set. - Do not break ties by guessing study quality. </constraints> <output> A conflict table: record, rule, discussion prompt, suggested default or ASK TEAM. </output>

💡

Pro tip: If the same rule causes three conflicts, rewrite the rule. Do not keep adjudicating the same ambiguity.

Code full-text exclusion reasons

13/30

✨ What it does

Claude maps full-text exclusion reasons from [PASTE FULL TEXT NOTES] onto PRISMA categories. You extract each reason from the PDF you opened, not from a guessed paper.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I have notes from full texts I opened. I need PRISMA-style exclusion reasons, one primary reason each. </context> <task> Map [PASTE FULL TEXT NOTES] to a single primary reason per record (wrong population, intervention, comparator, outcome, design, or other named reason). Quote the phrase in my notes that supports the reason. If notes are too thin, write NEED PDF. </task> <inputs> FULL_TEXT_NOTES: [PASTE FULL TEXT NOTES] ELIGIBILITY_CRITERIA: [ELIGIBILITY CRITERIA] </inputs> <constraints> - Do not invent a paper I did not paste notes for. - Do not stack three reasons when PRISMA wants one primary reason. - Do not promote a record to included. </constraints> <output> A table: record, primary reason, supporting quote from my notes, or NEED PDF. </output>

💡

Pro tip: Pick one primary reason. Stacked reasons make the flow diagram impossible to audit.

Fill a PRISMA 2020 flow from your counts

14/30

✨ What it does

Claude draws a PRISMA 2020 flow from [YOUR COUNTS] only, with a blank where a count is missing. You do not invent n identified or n included.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will give counts I recorded. You will place them in a PRISMA 2020 flow. You will not invent a box. </context> <task> Build a PRISMA 2020 flow from [YOUR COUNTS] only. If a box is missing, write UNKNOWN and say which export or log I must open. Show the arithmetic so I can see if the boxes add up. </task> <inputs> YOUR_COUNTS: [YOUR COUNTS] DATABASES_SEARCHED: [DATABASES] OTHER_SOURCES: [OTHER SOURCES OR NONE] </inputs> <constraints> - Do not invent n identified, n screened, n excluded, or n included. - Do not invent a study to make the boxes add up. - If the arithmetic fails, say so and stop. </constraints> <output> A text PRISMA 2020 flow with my numbers only, plus a list of UNKNOWN boxes. </output>

💡

Pro tip: If the boxes do not add up, fix the log. Do not ask Claude to plug a number that makes the figure look finished.

Calibrate on a 50-record pilot

15/30

✨ What it does

Claude calibrates the screening form on [PASTE 50 TITLES] and flags where the rules disagree. You screen the pilot set and lock the form before the rest.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I am piloting the screening form on a first batch before the full set. I need calibration notes, not a finished include list. </context> <task> Using [PASTE 50 TITLES] and [ELIGIBILITY CRITERIA], flag: (1) titles that test a fuzzy rule, (2) where two screeners are likely to split, (3) form edits, (4) items that cannot be judged without full text. Do not mark a final include set. </task> <inputs> PILOT_TITLES: [PASTE 50 TITLES] ELIGIBILITY_CRITERIA: [ELIGIBILITY CRITERIA] FORM_DRAFT: [SCREENING FORM] </inputs> <constraints> - Do not invent titles I did not paste. - Do not invent abstracts or outcomes for those titles. - Do not promote the pilot into n included studies. </constraints> <output> A calibration memo: fuzzy rules, suggested form edits, and which pilot rows I must screen first. </output>

💡

Pro tip: Lock the form after the pilot. Changing include rules halfway through the set is how reviews become unreproducible.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Data Extraction

5 prompts

Design the extraction form

16/30

✨ What it does

Claude designs a data extraction form for [OUTCOMES] and [STUDY DESIGNS] with fields and coding notes. You extract into that form from papers you hold.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need an extraction form that matches [OUTCOMES] and [STUDY DESIGNS]. I will fill it from papers I have. </context> <task> Design the form: (1) study ID and citation fields, (2) design and setting, (3) participants, (4) intervention or exposure, (5) outcomes with time points and metrics, (6) funding and conflicts, (7) coding notes, (8) a dual-extraction check. Leave result cells blank. </task> <inputs> OUTCOMES: [OUTCOMES] STUDY_DESIGNS: [STUDY DESIGNS] REVIEW_QUESTION: [REVIEW QUESTION] CITATION_STYLE: [CITATION STYLE] </inputs> <constraints> - Do not invent rows for studies I have not included. - Do not invent effect sizes or n randomized. - If an outcome needs a definition I did not give, mark DEFINE. </constraints> <output> A column list I can paste into a sheet, plus a one-page codebook. </output>

💡

Pro tip: Extract in duplicate on the first few papers. The codebook is wrong until two people hit the same cell.

Extract one paper you pasted

17/30

✨ What it does

Claude extracts study details from [PASTE METHODS AND RESULTS] into your form and marks UNKNOWN gaps. You extract only what that paste supports.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste methods and results from one paper I opened. Extract only what that paste supports. </context> <task> Fill my form from [PASTE METHODS AND RESULTS]. Use UNKNOWN for missing cells. Quote the phrase that supports each filled cell. Do not complete the row from training memory. </task> <inputs> PASTE: [PASTE METHODS AND RESULTS] FORM_FIELDS: [OUTCOMES] and any extra fields I list: [EXTRA FIELDS] STUDY_LABEL: [STUDY LABEL I ASSIGNED] </inputs> <constraints> - Do not invent author names, years, NCT numbers, or numbers that are not in the paste. - Do not pull a different paper with a similar title. - If the paste is only an abstract, extract an abstract-level row and say so. </constraints> <output> One extraction row, supporting quotes, and a list of UNKNOWN cells I must reopen in the PDF. </output>

💡

Pro tip: Paste the methods and results, not the title alone. A title is not enough to fill n, dose, or follow-up.

Build a study-characteristics table

18/30

✨ What it does

Claude builds a characteristics-of-included-studies table from [PASTE STUDY NOTES] and leaves empty rows blank. You do not invent 8 included studies to fill the table.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste notes for studies I have already decided to include. You will table those notes only. </context> <task> Build a characteristics-of-included-studies table from [PASTE STUDY NOTES]: citation as I labeled it, design, n, population, intervention, comparator, follow-up. Leave a cell blank or UNKNOWN rather than guess. Do not add a study I did not paste. </task> <inputs> STUDY_NOTES: [PASTE STUDY NOTES] CITATION_STYLE: [CITATION STYLE] COLUMNS_I_NEED: [COLUMNS] </inputs> <constraints> - Do not invent n included studies to make the table look complete. - Do not invent a row from a famous trial that is not in the notes. - If notes conflict, quote both and mark CONFLICT. </constraints> <output> A markdown table of only the studies in the notes, plus a gap list. </output>

💡

Pro tip: Every row needs a paper you can hand a reviewer. Empty is better than a tidy invented trial.

Build an outcomes table from your numbers

19/30

✨ What it does

Claude builds an outcomes table from [PASTE NUMBERS] with effect, n, and time point. You extract those numbers from the paper, not from a remembered figure.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste numbers I copied from papers. You will arrange them. You will not compute a pooled effect unless I pasted every input it needs. </context> <task> From [PASTE NUMBERS], build an outcomes table: study label, outcome, time point, n, effect, interval if present, scale. Flag unit mismatches. Do not invent a missing interval or a meta-analytic diamond. </task> <inputs> PASTE_NUMBERS: [PASTE NUMBERS] PRIMARY_OUTCOME: [OUTCOME] METRIC_I_WANT: [MEAN DIFFERENCE / RISK RATIO / OTHER] </inputs> <constraints> - Do not invent effect sizes, n, or confidence intervals. - Do not invent that studies are comparable enough to pool. - If a number is missing, write UNKNOWN, not a rounded guess. </constraints> <output> An outcomes table plus a list of cells that block any later meta-analysis. </output>

💡

Pro tip: Copy n and the interval from the PDF in the same sitting. Memory is how 184 becomes 148 in a results table.

Log missing data and author questions

20/30

✨ What it does

Claude lists missing fields in [MISSING FIELDS] and drafts author-contact questions. You extract what is present and log what the paper never reported.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> Some cells are empty after extraction. I need a missing-data log and polite author questions, not filled-in numbers. </context> <task> From [MISSING FIELDS], list: (1) what is missing per study label, (2) whether it is unreported or I failed to extract it, (3) a short author email, (4) what I will do if there is no reply (exclude from synthesis, impute only if my protocol already said so, or narrative only). </task> <inputs> MISSING_FIELDS: [MISSING FIELDS] STUDY_LABELS: [STUDY LABELS] PROTOCOL_RULE_FOR_MISSING: [PROTOCOL RULE] </inputs> <constraints> - Do not invent the missing number. - Do not invent that an author already replied. - Do not invent an email address. Leave a blank for me. </constraints> <output> A missing-data table and one email draft per study label, with a blank To: line. </output>

💡

Pro tip: Contact corresponding authors once, with a deadline. Then follow the missing-data rule you wrote in the protocol.

Bias and Certainty

5 prompts

Draft RoB 2 notes from pasted methods

21/30

✨ What it does

Claude drafts RoB 2 domain notes from [PASTE METHODS] and withholds a judgment when text is thin. You extract each domain call only from that methods text.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste methods (and results if needed) from a randomized trial I opened. I need RoB 2 domain notes, not a score from memory. </context> <task> Using [PASTE METHODS], draft RoB 2-style notes for randomization, deviations, missing outcome data, measurement, and selection of the reported result. For each domain: supporting quote, suggested judgment or NO JUDGMENT, and what I must reopen in the PDF. </task> <inputs> PASTE_METHODS: [PASTE METHODS] OUTCOME_FOR_RoB: [OUTCOME] TRIAL_LABEL: [STUDY LABEL] </inputs> <constraints> - Do not invent allocation concealment, blinding, or an NCT record I did not paste. - If the paste is silent, write NO JUDGMENT, not low risk. - Do not assign an overall score that hides empty domains. </constraints> <output> A domain table with quotes, suggested judgment or NO JUDGMENT, and PDF checks. </output>

💡

Pro tip: Some is not low risk. If concealment is not described, leave the domain open until the PDF or protocol says it.

Draft observational bias domains

22/30

✨ What it does

Claude applies observational bias domains to [STUDY DESIGN] using [PASTE METHODS]. You screen those domain notes against the paper you opened.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> [STUDY DESIGN] is not an RCT. I need ROBINS-I-style or design-appropriate domain notes from text I pasted. </context> <task> Using [PASTE METHODS], draft domain notes for confounding, selection, classification of the exposure, deviations, missing data, measurement, and reporting. Recommend a tool only if I did not name one. Do not invent confounders the paper never mentioned unless you label them HYPOTHESIZED. </task> <inputs> STUDY_DESIGN: [STUDY DESIGN] PASTE_METHODS: [PASTE METHODS] EXPOSURE: [INTERVENTION] OUTCOME: [OUTCOME] TOOL_IF_CHOSEN: [ROBINS-I / OTHER / UNDECIDED] </inputs> <constraints> - Do not invent a cohort size or an adjusted effect. - Do not treat observational evidence as an RCT with a weaker score. - Mark HYPOTHESIZED confounders separately from confounders the paper named. </constraints> <output> A domain table plus a note on whether this design can answer [REVIEW QUESTION] at all. </output>

💡

Pro tip: Write the confounders you care about in the protocol. Do not discover them after you like a study's result.

Draft a GRADE profile from your evidence

23/30

✨ What it does

Claude drafts a GRADE profile for [OUTCOME] from [PASTE EVIDENCE] and names each certainty move. You do not invent 11 studies in the evidence profile.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste the evidence I have for one outcome. I need a GRADE-style certainty discussion, not extra studies. </context> <task> From [PASTE EVIDENCE] for [OUTCOME], draft a GRADE profile: starting certainty, reasons to rate down or up, and a suggested certainty. Name risk of bias, inconsistency, indirectness, imprecision, and publication bias only from what I pasted. </task> <inputs> OUTCOME: [OUTCOME] PASTE_EVIDENCE: [PASTE EVIDENCE] DESIGN_MIX: [STUDY DESIGNS] INCLUDED_N_IF_KNOWN: [INCLUDED N OR UNKNOWN] </inputs> <constraints> - Do not invent 11 studies or a pooled effect I did not paste. - Do not start at high certainty for designs I said were observational. - If I did not give a count, write UNKNOWN instead of guessing n. </constraints> <output> A GRADE row for this outcome, with each rating move tied to a phrase in my paste. </output>

💡

Pro tip: GRADE one outcome at a time. A single certainty for the whole review is not GRADE.

Discuss publication bias without a fake plot

24/30

✨ What it does

Claude discusses publication-bias risk from [SEARCH DATES] and [INCLUDED N] without drawing a fake plot. You do not invent a funnel of 20 trials.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need an honest publication-bias discussion from the search I ran and the n I included, not a generated funnel plot. </context> <task> Using [SEARCH DATES] and [INCLUDED N], write: (1) whether a funnel plot is even justified, (2) registry and grey-search implications, (3) small-study risk in plain language, (4) what I must not claim. Do not draw or invent a plot of trials I did not list. </task> <inputs> SEARCH_DATES: [SEARCH DATES] INCLUDED_N: [INCLUDED N] GREY_SEARCH_DONE: [YES / NO] REGISTRY_SEARCH_DONE: [YES / NO] EFFECTS_I_HAVE: [PASTE EFFECT SIZES OR NONE] </inputs> <constraints> - Do not invent a funnel plot of 20 trials. - Do not run a statistical test on invented coordinates. - If n is small, say a plot would mislead. </constraints> <output> A short discussion paragraph plus a yes/no on whether I should attempt a plot at all. </output>

💡

Pro tip: Most reviews have too few studies for a funnel plot. Write that sentence. Do not paste a generated figure.

Plan sensitivity analyses

25/30

✨ What it does

Claude plans sensitivity analyses from [RISK DECISIONS] and names which included studies to drop. You extract which estimates move when those studies leave.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I have risk-of-bias decisions and a synthesis plan. I need sensitivity analyses that use the studies I actually included. </context> <task> From [RISK DECISIONS], propose analyses: drop high-risk studies, drop high-missing-data studies, fixed vs random if I already chose a primary model, and any pre-specified subgroup. Name study labels only if they appear in my paste. Do not invent a new included set. </task> <inputs> RISK_DECISIONS: [RISK DECISIONS] PRIMARY_SYNTHESIS: [NARRATIVE / META-ANALYSIS] INCLUDED_LABELS: [STUDY LABELS] PROTOCOL_SUBGROUPS: [SUBGROUPS OR NONE] </inputs> <constraints> - Do not invent a study label that is not in INCLUDED_LABELS. - Do not invent that an estimate will move by a given amount. - If n is too small for a subgroup, say so. </constraints> <output> A numbered sensitivity plan with the exact include/exclude rule for each run. </output>

💡

Pro tip: Write the sensitivity rule in the protocol. Choosing who to drop after you see the forest plot is a results-driven edit.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Write the Review

5 prompts

Write methods from the protocol you ran

26/30

✨ What it does

Claude writes a methods section from [PROTOCOL] that matches what you said you would do. You screen every sentence against the search and screening you actually ran.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste the protocol and what I actually did. The methods section must match the work, including deviations. </context> <task> Write a methods section from [PROTOCOL] and [WHAT I ACTUALLY DID]: eligibility, sources, search (no invented yields), screening, extraction, risk of bias, and synthesis. List deviations in a separate subsection. Leave counts as UNKNOWN unless I pasted them. </task> <inputs> PROTOCOL: [PROTOCOL] WHAT_I_ACTUALLY_DID: [WHAT I ACTUALLY DID] CITATION_STYLE: [CITATION STYLE] WORD_LIMIT: [WORD LIMIT] </inputs> <constraints> - Do not invent databases, dates, or n identified. - Do not invent a second reviewer if I said I screened alone. - If I screened alone, say that and name it as a limitation, not as dual independent review. </constraints> <output> A methods draft under [WORD LIMIT] plus a deviations list. </output>

💡

Pro tip: If you screened alone, write that. Dual independent review is a method, not a style you can claim after the fact.

Write results only from your table

27/30

✨ What it does

Claude writes a results narrative from [PASTE EXTRACTION TABLE] and cites only rows in that table. You do not invent 7 included trials in the prose.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste an extraction table. The results narrative may cite only rows in that table. </context> <task> Write a results narrative from [PASTE EXTRACTION TABLE]: study set, designs, participants as totaled only if I provided addable n, outcomes, and where studies disagree. Do not add a study. Do not invent a pooled effect. </task> <inputs> EXTRACTION_TABLE: [PASTE EXTRACTION TABLE] PRIMARY_OUTCOME: [OUTCOME] CITATION_STYLE: [CITATION STYLE] WORD_LIMIT: [WORD LIMIT] </inputs> <constraints> - Do not invent 7 included trials or extra citations. - Do not total n unless every row has an n I pasted. - If the table is empty, refuse to write results. </constraints> <output> A results draft under [WORD LIMIT] that points back to table rows, plus a list of claims I blocked. </output>

💡

Pro tip: If a sentence needs a paper that is not in the table, cut the sentence. That is how invented trials get into print.

Interpret effects you actually have

28/30

✨ What it does

Claude interprets pooled effects from [PASTE EFFECT SIZES] and states uncertainty in plain language. You extract the interpretation only from those numbers.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I will paste effect sizes I extracted. I need interpretation, not a new meta-analysis from memory. </context> <task> Interpret [PASTE EFFECT SIZES]: direction, precision, inconsistency you can see in the paste, and what a reader should not conclude. If I did not paste a pooled estimate, do not invent one. If I pasted a forest-plot readout, interpret those numbers only. </task> <inputs> EFFECT_SIZES: [PASTE EFFECT SIZES] OUTCOME: [OUTCOME] MINIMAL_IMPORTANT_DIFFERENCE: [MID OR UNKNOWN] </inputs> <constraints> - Do not invent a diamond, I-squared, or prediction interval. - Do not upgrade a narrative spread into a pooled effect. - Distinguish statistical and practical significance only from numbers I pasted. </constraints> <output> A plain-language interpretation plus a do-not-claim list. </output>

💡

Pro tip: Paste the numbers from your software or table. Do not ask Claude to remember a forest plot you saw last week.

Write discussion and limitations

29/30

✨ What it does

Claude drafts discussion and limitations from [KEY FINDINGS] and [ROB SUMMARY]. You screen every claim so none outruns the included set.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need a discussion that stays inside [KEY FINDINGS] and [ROB SUMMARY]. No new trials in the close. </context> <task> Draft discussion: what the included evidence can support, what it cannot, limitations (search, screening, bias, missing data), and implications for practice and research that do not require invented studies. </task> <inputs> KEY_FINDINGS: [KEY FINDINGS] ROB_SUMMARY: [ROB SUMMARY] KNOWN_GAPS: [GAPS I ALREADY LOGGED] WORD_LIMIT: [WORD LIMIT] </inputs> <constraints> - Do not invent a landmark trial to explain a gap. - Do not recommend a practice the included set cannot support. - If findings are thin, say the review is empty or uncertain rather than padding. </constraints> <output> Discussion and limitations under [WORD LIMIT], with each practice claim tagged SUPPORTED or NOT SUPPORTED. </output>

💡

Pro tip: An empty or uncertain review is a result. Padding the discussion with famous trials you never screened is misconduct.

Write the abstract and plain-language summary

30/30

✨ What it does

Claude writes a structured abstract and plain-language summary from [YOUR RESULTS] within [WORD LIMIT]. You do not invent n participants or n trials.

<role> You are a systematic-review methodologist. You draft protocol text and tables. You never invent studies, trial IDs, effect sizes, or PRISMA counts. </role> <context> I need a structured abstract and a plain-language summary that use only [YOUR RESULTS]. </context> <task> Write: (1) a structured abstract (background, methods, results, conclusions) within [WORD LIMIT], (2) a plain-language summary a non-specialist can read. Use only counts and effects I pasted. If a count is UNKNOWN, keep it out of the abstract. </task> <inputs> YOUR_RESULTS: [YOUR RESULTS] WORD_LIMIT: [WORD LIMIT] AUDIENCE: [CLINICIANS / POLICY / PUBLIC] CITATION_STYLE: [CITATION STYLE] </inputs> <constraints> - Do not invent n participants or n trials. - Do not invent a certainty rating I did not paste. - Do not write a positive conclusion the results section cannot carry. </constraints> <output> Structured abstract, then a plain-language summary, then a list of numbers I still must fill. </output>

💡

Pro tip: Write the abstract last, from the finished tables. An abstract with a nicer n than the PRISMA flow will be caught.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

No. Claude can draft PICO, eligibility, and PROSPERO-style fields. That draft is not a registered protocol on PROSPERO, OSF, or a journal registry. You lock the fields, file them yourself, and keep the registration ID. Filing after you already know the included set is not a protocol.
It will try if you let it. These prompts forbid invented trials, NCT numbers, effect sizes, and PRISMA counts. You paste records you retrieved, papers you opened, and numbers you copied. If a row is not in your table, it does not go in the review.
It can draft the form, flag fuzzy rules, and log conflicts you paste. You still screen. Dual independent human screening is the method. Letting a chat mark include on titles it has not been shown is how invented studies enter a PRISMA flow.
It can draft domain notes and GRADE moves from methods and evidence you paste, and it should refuse a judgment when the paste is silent. You own the call. Do not accept a low-risk or high-certainty label that is not tied to text you opened.
Only if you ran the review that way. PRISMA is a reporting checklist for work you did: named sources, saved strings, counted records, human screening, and tables that match the PDFs. Claude can format the flow and the methods. It cannot supply a search you never ran.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.