> ## Documentation Index
> Fetch the complete documentation index at: https://docs.biomni.phylo.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Resources

> Point Biomni at scientific databases, software, HPC tools, and pipelines

Resources tell Biomni which scientific database, software package, command-line
tool, or managed compute tool you want it to consider.

The live Resources browser is the source of truth for the catalog available in
your workspace. It is updated more often than this guide and can vary by plan.

## Browse resources

Open **Resources** from the main navigation, or select **+ Add → Resources** in
a task. Type `@` in the composer to search the same resource catalog alongside
available files.

Resources are grouped into:

* **Databases** — scientific data sources such as PubMed, UniProt, PDB, Ensembl,
  ClinVar, GEO, Open Targets, and GWAS Catalog.
* **Tools** — managed scientific functions, HPC tools, and versioned pipelines.
* **Software** — Python, R, and command-line packages available for code-based
  analysis.

Select a resource to add it to the message, then describe how it should be used:

```text theme={null}
Search @PubMed for randomized studies published since 2022 on this intervention.
Build an evidence table with population, endpoint, effect size, and limitations.
```

```text theme={null}
Use @STAR for alignment and explain the reference build and parameters before
submitting the run.
```

## Attaching a resource does not run it

A resource is context for the request. Biomni still chooses and executes the
appropriate tool calls while working. If you require a specific method, say so
explicitly and explain any fixed parameters or validation criteria.

<Tip>
  You usually do not need to attach common software by name. Attach a resource when
  the source or method is part of the scientific requirement.
</Tip>

## Managed compute and pipelines

Compute-intensive tools and nf-core pipelines run outside the ordinary analysis
workspace. Biomni searches the current registry, reads the selected tool or
pipeline guide, submits the job, and reports completion back to the task.

Availability, versions, GPU types, and resource limits can change by plan and
workspace. Use the in-product catalog rather than a copied tool list when
planning a workflow.

## Resources versus Skills

A **Resource** identifies something Biomni can use. A **Skill** supplies a
reusable workflow for how to approach a class of task. You can use both in the
same request.

See [Skills & Capabilities](/features/skills-and-capabilities) for examples.