Use when working with LaminDB, the open-source lineage-native lakehouse for biological datasets and models. Covers setup, artifact registration, query/search, lineage tracking, validation, ontology-backed annotation with Bionty, collections, branches, storage, and workflow integrations.
SKILL.md
LaminDB
Overview
LaminDB is an open-source, lineage-native lakehouse for biology. It makes datasets and models queryable, traceable, validated, reproducible, and FAIR (Findable, Accessible, Interoperable, Reusable) while storing data in open formats across local filesystems, S3, GCS, Hugging Face, SQLite, and Postgres.
Core Value Proposition:
Queryability: Search and filter artifacts, records, runs, features, schemas, and collections
Traceability: Track inputs, outputs, parameters, source code, and environments for notebooks, scripts, functions, and pipelines
Validation: Curate DataFrame, AnnData, SpatialData, TileDB-SOMA, Parquet, Zarr, and other biological formats with schemas
FAIR Compliance: Standardize annotations with Bionty-backed ontologies and custom registries
Change management: Organize work with projects, branches, spaces, collections, and saved notes or plans
When to Use This Skill
Use this skill when:
Managing biological datasets: scRNA-seq, bulk RNA-seq, spatial transcriptomics, flow cytometry, multi-modal data, EHR data
Create and version artifacts from files or Python objects
Track notebook/script execution with ln.track() and ln.finish()
Track function workflows with @ln.flow() and @ln.step()
Annotate artifacts with records, ulabels, projects, and typed features
Visualize data lineage graphs with artifact.view_lineage()
Query by provenance (find all outputs from specific code/inputs)
Reference:references/core-concepts.md - Read this for detailed information on artifacts, records, runs, transforms, features, versioning, and lineage tracking.
2. Data Management and Querying
Query capabilities:
Registry exploration and lookup with auto-complete
Single record retrieval with get(), one(), one_or_none()
Filtering with comparison operators (__gt, __lte, __contains, __startswith)
Feature-based queries, including expression-style queries with Feature objects
Cross-registry traversal with double-underscore syntax
Full-text search across registries
Advanced logical queries with ln.Q objects (AND, OR, NOT)
Streaming large datasets without loading into memory
Key workflows:
Browse artifacts with filters and ordering
Query by features, creation date, creator, size, etc.
Stream large files in chunks or with array slicing
Organize data with hierarchical keys
Group artifacts into collections
Reference:references/data-management.md - Read this for comprehensive query patterns, filtering examples, streaming strategies, and data organization best practices.
3. Annotation and Validation
Curation process:
Validation: Confirm datasets match desired schemas
Standardization: Fix typos, map synonyms to canonical terms
Annotation: Link datasets to metadata entities for queryability
Schema types:
Flexible schemas: Validate only known columns, allow additional metadata
Strict schemas: Complete control over structure and values
Supported data types:
DataFrames (Parquet, CSV)
AnnData (single-cell genomics)
MuData (multi-modal)
SpatialData (spatial transcriptomics)
TileDB-SOMA (scalable arrays)
Key workflows:
Define features and schemas for data validation
Use DataFrameCurator, AnnDataCurator, SpatialDataCurator, or TiledbsomaExperimentCurator for validation
Standardize values with .cat.standardize()
Map to ontologies with .cat.add_ontology()
Save curated artifacts with schema linkage
Query validated datasets by features
Reference:references/annotation-validation.md - Read this for detailed curation workflows, schema design patterns, handling validation errors, and best practices.
4. Biological Ontologies
Available ontologies (via Bionty):
Genes (Ensembl), Proteins (UniProt)
Cell types (CL), Cell lines (CLO)
Tissues (Uberon), Diseases (Mondo, DOID)
Phenotypes (HPO), Pathways (GO)
Experimental factors (EFO), Developmental stages
Organisms (NCBItaxon), Drugs (DrugBank)
Key workflows:
Import public ontologies with bt.CellType.import_source()
Reference:references/ontologies.md - Read this for comprehensive ontology operations, standardization strategies, hierarchy navigation, and annotation workflows.
5. Integrations
Workflow managers:
Nextflow: Track pipeline processes and outputs
Snakemake: Integrate into Snakemake rules
Redun: Combine with Redun task tracking
Lightning: Persist checkpoints and training metadata
MLOps platforms:
Weights & Biases: Link experiments with data artifacts
MLflow: Track models and experiments
Hugging Face: Track model fine-tuning
scVI-tools: Single-cell analysis workflows
Storage systems:
Local filesystem, AWS S3, Google Cloud Storage
S3-compatible (MinIO, Cloudflare R2)
HTTP/HTTPS endpoints (read-only)
HuggingFace datasets
Array stores:
TileDB-SOMA (with cellxgene support)
DuckDB for SQL queries on Parquet files
Visualization:
Vitessce for interactive spatial/single-cell visualization
Version control:
Git integration for source code tracking
Reference:references/integrations.md - Read this for integration patterns, code examples, and troubleshooting for third-party systems.
6. Setup and Deployment
Installation:
Current stable baseline: lamindb==2.5.1 (released 2026-06-01; Python >=3.10, <=3.14)
Basic: uv pip install 'lamindb==2.5.1'
With extras: uv pip install 'lamindb[gcp,zarr-v2,fcs]==2.5.1'
Bionty module: included in the LaminDB docs and available as uv pip install 'bionty==2.4.0'
Optional modules: pin reviewed releases for wetlab or clinical schema modules rather than installing floating latest versions
Instance types:
Local SQLite (development)
Cloud storage + SQLite (small teams)
Cloud storage + PostgreSQL (production)
Storage options:
Local filesystem
AWS S3 with configurable regions and permissions
Google Cloud Storage
S3-compatible endpoints (MinIO, Cloudflare R2)
Configuration:
Cache management for cloud files
Multi-user system configurations
Git repository sync
Named environment variables for credentials and connection URLs
Deployment patterns:
Local dev → Cloud production migration
Multi-region deployments
Shared storage with personal instances
Reference:references/setup-deployment.md - Read this for detailed installation, configuration, storage setup, database management, security best practices, and troubleshooting.
Safety and Security Defaults
When helping with LaminDB setup or integrations:
Never display, log, or transmit actual API keys, cloud credentials, database passwords, or full connection strings that include secrets.
Prefer IAM roles, workload identity, secret managers, or named environment variables such as LAMIN_DB_URL, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and GOOGLE_APPLICATION_CREDENTIALS; only check whether a named variable is present, not its value.
Before saving content from REST APIs, external databases, or user-provided files, validate and sanitize it with an explicit schema or curator.
For reproducible installs, pin package versions or use a lock file. Floating installs are acceptable only when the user explicitly wants the latest upstream release.
Common Use Case Workflows
Use Case 1: Single-Cell RNA-seq Analysis with Ontology Validation
import lamindb as ln
import bionty as bt
import anndata as ad
# Start tracking a notebook/script run
ln.track(params={"analysis": "scRNA-seq QC and annotation"})
# Import cell type ontology
bt.CellType.import_source()
# Load data
adata = ad.read_h5ad("raw_counts.h5ad")
# Validate and standardize cell types
adata.obs["cell_type"] = bt.CellType.standardize(adata.obs["cell_type"])
# Curate with schema
curator = ln.curators.AnnDataCurator(adata, schema)
curator.validate()
artifact = curator.save_artifact(key="scrna/validated.h5ad")
# Link ontology-backed annotations for queryability
cell_types = bt.CellType.from_values(adata.obs["cell_type"])
artifact.cell_types.add(*cell_types)
ln.finish()
Use Case 2: Building a Queryable Data Lakehouse
import lamindb as ln
# Register multiple experiments
for i, file in enumerate(data_files):
artifact = ln.Artifact.from_anndata(
ad.read_h5ad(file),
key=f"scrna/batch_{i}.h5ad",
description=f"scRNA-seq batch {i}"
).save()
# Annotate with features
artifact.features.set_values({
"batch": i,
"tissue": tissues[i],
"condition": conditions[i]
})
# Query across all experiments by annotated features
immune_datasets = ln.Artifact.filter(
key__startswith="scrna/",
tissue="PBMC",
condition="treated"
).to_dataframe()
# Load specific datasets
for artifact in immune_datasets:
adata = artifact.load()
# Analyze
Use Case 3: ML Pipeline with W&B Integration
import lamindb as ln
import wandb
# Initialize both systems
wandb.init(project="drug-response", name="exp-42")
ln.track(params={"model": "random_forest", "n_estimators": 100})
# Load training data from LaminDB
train_artifact = ln.Artifact.get(key="datasets/train.parquet")
train_data = train_artifact.load()
# Train model
model = train_model(train_data)
# Log to W&B
wandb.log({"accuracy": 0.95})
# Save model in LaminDB with W&B linkage
import joblib
joblib.dump(model, "model.pkl")
model_artifact = ln.Artifact("model.pkl", key="models/exp-42.pkl").save()
model_artifact.features.set_values({"wandb_run_id": wandb.run.id})
ln.finish()
wandb.finish()
Use Case 4: Nextflow Pipeline Integration
# In Nextflow process script
import lamindb as ln
ln.track()
# Load input artifact
input_artifact = ln.Artifact.get(key="raw/batch_${batch_id}.fastq.gz")
input_path = input_artifact.cache()
# Process (alignment, quantification, etc.)
# ... Nextflow process logic ...
# Save output
output_artifact = ln.Artifact(
"counts.csv",
key="processed/batch_${batch_id}_counts.csv"
).save()
ln.finish()
For native Nextflow projects, prefer the nf-lamin plugin and current nextflow.config patterns when available; use inline Python tracking for small or custom pipeline steps.