lamindb
LaminDB is an open-source lineage-native lakehouse that manages biological datasets and models by making them queryable, traceable, validated, and reproducible. Use this skill when managing biological data such as scRNA-seq or spatial transcriptomics, tracking computational workflows, curating data with schema validation, working with biological ontologies through Bionty, building unified data lakehouses, ensuring reproducibility through versioning and lineage tracking, integrating ML pipelines, or establishing local or cloud-based data infrastructure for collaborative research.
git clone --depth 1 https://github.com/K-Dense-AI/scientific-agent-skills /tmp/lamindb && cp -r /tmp/lamindb/skills/lamindb ~/.claude/skills/lamindbSKILL.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 - **Tracking computational workflows**: Notebooks, scripts, functions, shell scripts, and pipeline execution (Nextflow, Snakemake, Redun) - **Curating and validating data**: Schema validation, standardization, ontology-based annotation - **Working with biological ontologies**: Genes, proteins, cell types, tissues, diseases, pathways (via Bionty) - **Building data lakehouses**: Unified query interface across multiple datasets - **Ensuring reproducibility**: Automatic versioning, lineage tracking, environment capture - **Integrating ML pipelines**: Connecting with Weights & Biases, MLflow, Hugging Face, Lightning, scVI-tools - **Deploying data infrastructure**: Setting up local or cloud-based data management systems - **Collaborating on datasets**: Sharing curated, annotated data with standardized metadata ## Core Capabilities LaminDB provides six interconnected capability areas, each documented in detail in the references folder. ### 1. Core Concepts and Data Lineage **Core entities:** - **Artifacts**: Versioned datasets (DataFrame, AnnData, Parquet, Zarr, etc.) - **Records & ULabels**: Experimental entities, typed records, and simple labels - **Collections**: Versioned, immutable sets of artifacts - **Runs & Transforms**: Computational lineage tracking (what code produced what data) - **Features**: Typed metadata fields for annotation and querying - **Projects, Branches & Spaces**: Project grouping, change management, and access boundaries **Key workflows:** - 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:** 1. **Validation**: Confirm datasets match desired schemas 2. **Standardization**: Fix typos, map synonyms to canonical terms 3. **Annotation**: Link datasets to metadata entities for queryability **Schema types:** - **Flexible schemas**: Validate only known columns, allow additional metadata - **Minimal required schemas**: Specify essential columns, permit extras - **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()` - Search ontologies with keyword or exact matching - Standardize terms using synonym mapping - Explore hierarchical relationships (parents, children, ancestors) - Validate data against ontology terms - Annotate datasets with ontology records - Create custom t
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Infer gene regulatory networks (GRNs) from gene expression data using scalable algorithms (GRNBoost2, GENIE3). Use when analyzing transcriptomics data (bulk RNA-seq, single-cell RNA-seq) to identify transcription factor-target gene relationships and regulatory interactions. Supports distributed computation for large-scale datasets.
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server. Returns 25+ fields per paper including methods, results, sample sizes, quality scores, and conclusions. Use for literature reviews, evidence synthesis, and finding experimental details not available in abstracts alone.