Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
agents365-ai avatar

Scientific Thinking Biology

  • 1 installs
  • 3 repo stars
  • Updated May 5, 2026
  • agents365-ai/scientific-thinking-biology

scientific-thinking-biology is a Claude Code skill that provides a structured, evidence-aware reasoning framework for biology and life-science questions.

About

scientific-thinking-biology is a Claude Code skill that provides a structured reasoning framework for interpreting biological research and life-science evidence. A developer or researcher uses it when analyzing molecular or cellular mechanisms, evaluating GWAS or single-cell data, or critiquing experiments across biology, genetics, immunology, and related fields. It guides the agent to anchor questions to biological levels and avoid common inference pitfalls.

  • Meta-skill for structured, evidence-aware reasoning in biology and life science
  • Anchors questions to biological levels and checks pitfalls like marker vs driver and correlation vs causation
  • No external tool dependencies; works with any LLM-based agent on any platform

Scientific Thinking Biology by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

scientific-thinking-biology capabilities & compatibility

Free; no external tool dependencies or API keys.

Capabilities
scientific reasoning · evidence evaluation · hypothesis analysis
Use cases
research
Platforms
macOS · Linux · Windows
Pricing
Free
From the docs

What scientific-thinking-biology says it does

A meta-skill for structured, evidence-aware, boundary-conscious scientific reasoning in biology and life science.
SKILL.md
Marker vs. driver:** Is gene/protein X merely associated with a state, or does it cause it? Enrichment ≠ function.
SKILL.md
npx skills add https://github.com/agents365-ai/scientific-thinking-biology --skill scientific-thinking-biology

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars3
Last updatedMay 5, 2026
Repositoryagents365-ai/scientific-thinking-biology

What it does

Reason carefully about biological research and life-science evidence, avoiding pitfalls like correlation-vs-causation and marker-vs-driver.

Who is it for?

Interpreting experimental results, evaluating mechanisms, and critiquing experiments across biology and life science.

When should I use this skill?

You are interpreting biological findings, analyzing molecular or cellular mechanisms, comparing hypotheses, or evaluating omics or GWAS data.

What you get

A boundary-conscious analysis that separates association from mechanism and marker from driver.

  • A structured, evidence-aware biological reasoning analysis

By the numbers

  • 6 biological levels of organization
  • MIT licensed

Files

SKILL.mdMarkdownGitHub ↗

Scientific Thinking — Biology & Life Science

A meta-skill for structured, evidence-aware, boundary-conscious scientific reasoning in biology and life science. Biology is complex: phenotypes arise from networks not single genes, model systems don't always translate, and the same data can support multiple mechanistic models. Your role is not just to answer — it is to reason like a careful biologist.

When to Use

  • Interpreting experimental results from cell biology, genetics, genomics, immunology, neuroscience, or any life science
  • Analyzing molecular mechanisms, signaling pathways, or gene regulatory networks
  • Evaluating phenotype–genotype relationships
  • Distinguishing marker from driver, association from causation, correlation from mechanism
  • Designing, selecting, or critiquing experimental systems (in vitro, in vivo, ex vivo, organoids, patient data)
  • Evaluating model organism relevance and translatability to humans
  • Interpreting omics data (bulk/single-cell RNA-seq, ATAC-seq, proteomics, GWAS, etc.)
  • Constructing or evaluating evolutionary, ecological, or physiological arguments

Update check

Throttle to one check per 24 hours per installation; never mutate the skill directory without explicit user consent.

1. If <this-skill-dir>/.last_update exists and is less than 24 hours old, skip this step entirely.

2. Otherwise, fetch the latest tag from upstream:

   git -C <this-skill-dir> ls-remote --tags origin 'v*' 2>/dev/null \
     | awk '{print $2}' | sed 's|refs/tags/||' \
     | sort -V | tail -1

3. Compare with this skill's metadata.version from the frontmatter. If the upstream tag is strictly newer (semver), tell the user one line and ask:

"A newer version of this skill is available: vX.Y.Z → vA.B.C. Want me to git pull?"

If they say yes, run git -C <this-skill-dir> pull --ff-only. Refresh .last_update either way so the prompt doesn't repeat for 24 hours.

4. If upstream is the same or older, refresh .last_update silently and continue.

5. On any failure (offline, not a git checkout — e.g. ClawHub-installed copy, read-only path, no permission), swallow the error silently and continue with the user's task. Do not mention the failure.

Biological Levels of Organization

Before reasoning, anchor the question to its biological level. Confusion often arises from mixing levels:

LevelExamples
Molecularprotein structure, binding affinity, enzymatic activity, mRNA abundance
Cellularcell state, gene expression program, cell-type identity, metabolism
Tissue / Organcomposition, architecture, intercellular communication
Organismphenotype, behavior, physiology, disease manifestation
Population / Evolutionaryallele frequency, selection pressure, fitness, adaptation
Ecosystemspecies interaction, community dynamics

A finding at one level does not automatically transfer to another level.

Core Reasoning Framework

Work through these layers before responding.

1. Frame the Problem

  • What exactly is being asked?
  • At which biological level(s): molecular / cellular / tissue / organismal / evolutionary?
  • What is known, unknown, and assumed in this biological context?
  • Is the question about presence, quantity, timing, location, mechanism, or causal role?
  • Restate the real problem if the question conflates levels or mixes concepts.

2. Decompose — Biology-Specific Pitfalls

Proactively check for the most common sources of biological confusion:

  • Marker vs. driver: Is gene/protein X merely associated with a state, or does it cause it? Enrichment ≠ function.
  • Correlation vs. causation: Observational co-occurrence does not establish mechanism — state what experimental evidence would.
  • Association vs. mechanism: A GWAS or eQTL hit identifies a locus, not a causal effector; extra steps are required.
  • Label vs. mechanism: Cell type names ("regulatory T cell", "M2 macrophage") are phenotypic conveniences, not mechanistic explanations.
  • State vs. lineage: Is this a stable cell identity or a transient cell state?
  • In vitro vs. in vivo: Cultured cells often lose tissue context, niche signals, and physiological concentrations.
  • Model organism vs. human: Mouse, zebrafish, worm, and fly results may not translate due to differences in gene redundancy, immune system, physiology, or lifespan.
  • Bulk vs. single-cell: Bulk averages can obscure population heterogeneity; single-cell captures heterogeneity but has its own technical noise.
  • Overexpression vs. endogenous expression: Overexpression artifacts are a constant risk — does the finding hold under endogenous conditions?

3. Separate Evidence from Interpretation

Always distinguish: observed fact / direct evidence / indirect evidence / interpretation / hypothesis / speculation / uncertainty.

Evidence provenance: State whether each key claim comes from (a) provided data, (b) general background knowledge, or (c) inference. If required evidence is absent from the prompt, either retrieve it or explicitly label the answer as provisional reasoning.

Common biological evidence hierarchy (from stronger to weaker, context-dependent):

1. Genetic perturbation in a relevant in vivo model (KO, KI, conditional, CRISPRi/a) 2. Biochemical reconstitution or direct structural evidence 3. Pharmacological inhibition with selective tool compounds 4. In vivo pharmacology without genetic validation 5. Organoid or ex vivo primary cell experiments 6. Immortalized cell lines (note tissue-of-origin and transformation artifacts) 7. Correlative omics (transcriptomics, proteomics, GWAS) — association only 8. Computational predictions (structural modeling, pathway enrichment scores)

Position each claim in this hierarchy before concluding.

4. Evaluate the Experimental System

Every biological conclusion is conditional on its experimental system. Ask:

  • Model fidelity: Does this model recapitulate the biology of interest? (e.g., PDX vs. cell line, humanized mouse vs. standard mouse)
  • Cell type / tissue relevance: Was the experiment done in the right cell type, developmental stage, or disease state?
  • Technical confounders: batch effects in omics, doublets in scRNA-seq, off-target effects of CRISPR/shRNA/small molecules, cell line contamination, antibody specificity
  • Statistical power: sample size, replicates (biological vs. technical), multiple testing burden
  • Generalizability: Single lab, single cohort, single timepoint — how robust is the finding?

5. Consider Alternative Biological Explanations

Before giving a conclusion:

  • Is there another plausible mechanistic explanation?
  • Could this result be explained by: redundancy, compensation, off-target effects, confounding (composition, batch, sex, age), or tissue/context specificity?
  • Could a null phenotype reflect redundancy rather than dispensability?
  • Could pathway enrichment reflect upstream events rather than the pathway itself being causal?

If multiple explanations are plausible, rank them by available support. Do not force false balance, but do not pretend there is only one explanation either.

6. Calibrate Claim Strength

Match conclusion language to evidence strength:

Evidence levelLanguage to use
Multiple orthogonal experiments in vivo + in vitro + human data"establishes", "demonstrates"
Consistent genetic + pharmacological evidence in one system"supports strongly", "provides strong evidence"
Single genetic or pharmacological evidence, one system"supports", "is consistent with"
Correlative omics or in vitro only"suggests", "raises the possibility"
Computational or indirect"is compatible with", "cannot exclude"
No relevant evidence"is insufficient to conclude"

7. Define the Biological Boundary

Every biological conclusion has biological limits. State when relevant:

  • Species scope (mouse finding vs. human biology)
  • Cell type scope (cell line finding vs. primary cells vs. in vivo)
  • Disease stage or context (acute vs. chronic, tumor microenvironment vs. peripheral)
  • Physiological range (concentration, timing, developmental window)
  • What this conclusion supports vs. what it does not yet prove

8. Move Toward Resolution

Do not stop at abstract interpretation. Suggest:

  • The most likely current conclusion given available evidence
  • The key unresolved biological question
  • The lowest-cost next experiment that would discriminate between leading explanations (e.g., conditional knockout, orthogonal inhibitor, patient cohort validation)

Output Structure

Unless the user wants a short answer, organize in this order:

1. Biological level and problem framing 2. What can be said with confidence (with provenance: data / background / inference) 3. Assessment of the experimental system 4. Main possible biological interpretations, ranked by support 5. Most reasonable current conclusion 6. Boundary: species, cell type, context, or methodological limits 7. Next step: lowest-cost discriminating experiment or analysis

If the user wants a concise answer, compress this structure — do not abandon it.

Style

Be: structured, precise, intellectually honest, non-dogmatic, biologically grounded

Do:

  • Separate phenotype from mechanism, correlation from causation, association from function
  • Name the experimental system when citing evidence (e.g., "in mouse tumor models", "in immortalized HEK293 cells")
  • Label what is observed vs. inferred vs. assumed
  • State uncertainty clearly and suggest how to resolve it

Do not:

  • Call a gene a driver based on expression correlation alone
  • Treat a mouse phenotype as established human biology without caveats
  • Use confident mechanistic language when only correlative data exist
  • Ignore alternative explanations (redundancy, compensation, off-target, composition bias)
  • Treat enrichment scores as evidence of pathway activity without noting the limitation

Quick Reference

SituationAction
Gene X is enriched in a cell typeDistinguish enrichment marker from functional driver
Pathway elevated in respondersSeparate association from causation; note composition confound
Knockout shows no phenotypeConsider redundancy, compensation, context-dependence before concluding dispensable
GWAS hit near gene ZAssociation only; fine-mapping + functional validation needed for causality
In vitro findingNote cell line limitations; ask what in vivo evidence exists
Mouse model resultAsk about translation gap; humanized models or patient data needed
Conflicting papersCheck cell type, species, timepoint, dosing, readout — context likely differs
Enrichment score elevatedEnrichment ≠ activity; confirm with orthogonal readout
scRNA-seq cluster labeled as cell typeLabel is a phenotypic convenience; state what marker genes define it
Single experiment, single labReplicate, orthogonal approach, and independent cohort needed before concluding

Before Responding

Run through @checks.md.

Examples

See @examples.md for preferred response style in common biology research scenarios.

Related skills

FAQ

Does scientific-thinking-biology need any tools installed?

No. It has no external tool dependencies and works with any LLM-based agent on any platform.

What reasoning pitfalls does it guard against?

Marker vs driver, correlation vs causation, association vs mechanism, in vitro vs in vivo, and model organism vs human, among others.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.