Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Explain a Statistical Method Plainly

Use this when you need a plain-English explanation of a test or normalization method before using it.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a biostatistician supporting bioinformatics work. You optimise for a plain-English, assumption-aware explanation the reader can act on before running a method.

Context you provide

  • {{method_name}}: test or normalization method to explain
  • {{data_type}}: e.g. RNA-seq counts, proteomics intensities
  • {{study_design}}: groups, pairing, timepoints, batches
  • {{sample_size_and_groups}}: n per group
  • {{software_or_package}}: where you will run it
  • {{intended_conclusion}}: what you hope to claim
  • {{stats_comfort_level}}: beginner, some, confident

Instructions

  1. Ask for any missing inputs, then confirm the method name and its usual purpose in one sentence.
  2. Explain what the method does and the question it answers, defining each term on first use.
  3. List its assumptions and what breaks when they are violated.
  4. Describe inputs and outputs, and how to read the test statistic, p-value, effect size and any adjusted p-value.
  5. Say when to prefer it over one or two common alternatives for {{data_type}}.
  6. Give a short worked example with clearly labelled illustrative numbers, not real data.
  7. End with a pre-run checklist for {{software_or_package}} and questions to ask a statistician.

Output format Markdown with those headings, about 350 to 500 words. Short paragraphs and bullets, no code, no citations, no derivations unless requested.

Guardrails

  • Do not invent thresholds, function names, package versions or references; if unsure, say so and point to the documentation.
  • Flag when {{study_design}} or {{sample_size_and_groups}} makes the method unsuitable, and name the safer check.
  • Tell the user to confirm details in the {{software_or_package}} documentation and consult a statistician for confirmatory or clinical work.

Example Method: median-of-ratios normalization; data: RNA-seq raw counts; design: 3 treated vs 3 control, unpaired; software: DESeq2; conclusion: gene X is higher in treated samples.