Skip to content
Research Agent Skillsby Kalaris Labs
Install
Lab Automationv2.1AdaptedMIT

latchbio-integration

Build, register, debug, and operate bioinformatics workflows on Latch using the Python SDK, CLI, Latch Data and Registry, Nextflow, Snakemake, programmatic execution, and Latch MCP. Use when authoring or deploying Latch workflows, configuring resources or interfaces, moving data, integrating Registry, or launching and monitoring runs.

Install this skill

Works with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode, and 70+ other harnesses.

skills.sh CLI (Recommended)
npx skills add KalarisLabs/research-agent-skills --skill latchbio-integration
uvx (Python tool runner)
uvx research-agent-skills install latchbio-integration

Documentation & Instructions

LatchBio Integration

Current Baseline

This skill targets Latch SDK 2.76.8, released July 10, 2026. The package metadata supports Python 3.9–3.12 and declares Python 3.9+.

Treat the installed package and its changelog as authoritative when a guide disagrees with the SDK. Some Latch guides retain older Python ranges or compatibility-specific pre-release pins, especially the Snakemake v2 tutorial. Never combine commands or imports from different tracks without checking their version requirements.

When to Use

Use this skill to:

  • Create or maintain Python SDK workflows and task graphs
  • Package and register Python, Nextflow, or Snakemake pipelines
  • Configure task CPU, memory, storage, GPU, caching, retries, and timeouts
  • Work with Latch Data through LPath, LatchFile, LatchDir, or the CLI
  • Read or update Latch Registry projects, tables, and records
  • Design workflow forms, launch plans, samplesheets, messages, and result links
  • Stage and debug workflow images with latch register --staging and latch develop
  • Launch and monitor workflows through Python or Latch MCP
  • Discover and use ready-to-run Latch workflows

Route to the Right Reference

Read only the references needed for the task:

Need Reference
Python workflows, tasks, maps, conditions, caching references/workflow-creation.md
LPath, legacy file types, Latch URLs, data CLI references/data-management.md
Registry reads, transactions, samplesheets references/registry.md
CPU, memory, storage, GPU, dynamic resources references/resource-configuration.md
Nextflow and Snakemake packaging references/nextflow-snakemake.md
Metadata, forms, launch plans, messages, automations references/ui-and-automation.md
Registration, development, execution, monitoring references/operations-and-debugging.md
Ready-to-use workflows and latch.verified references/verified-workflows.md
Remote MCP setup and tool workflow references/latch-mcp.md

Before relying on a symbol, run scripts/inspect_latch_sdk.py against the target SDK version. It performs local imports only and does not authenticate or make network requests.

Installation and Authentication

For a reproducible environment:

uv venv --python 3.12
source .venv/bin/activate
uv pip install "latch==2.76.8"

On Windows, use WSL for the documented Linux workflow tooling.

Authenticate through the supported OAuth flow; do not read, print, copy, or parse ~/.latch/token manually:

latch login
latch workspace

Select a workspace non-interactively when its numeric ID is already known:

latch workspace --id 12345

latch login credentials are for the SDK and CLI. Latch MCP uses a separate OAuth authorization and its credentials cannot be reused for general SDK access.

Fast Path

Create and remotely register the maintained subprocess template:

latch init covid-wf --template subprocess
latch register --yes --open covid-wf

Remote image building is the default. Use --no-remote only when a local Docker daemon is available and a local build is intentional.

Minimal Python Workflow

Keep workflow bodies declarative: invoke tasks and return their promises. Perform computation and side effects inside tasks.

from latch import small_task, workflow


@small_task
def reverse_complement(sequence: str) -> str:
    table = str.maketrans("ACGTacgt", "TGCAtgca")
    return sequence.translate(table)[::-1]


@workflow
def reverse_complement_workflow(sequence: str) -> str:
    """Return the reverse complement of a DNA sequence."""
    return reverse_complement(sequence=sequence)

Use @workflow(metadata) when the generated interface needs custom labels, sections, validation rules, samplesheets, or documentation links. Use LatchFile or LatchDir for automatic task input staging and output upload; use LPath for imperative remote path operations.

Recommended Development Lifecycle

  1. Inspect compatibility

    • Confirm the installed SDK and Python version.
    • Identify whether the project is Python, Nextflow, the legacy Snakemake flag path, or the separately pinned Snakemake v2 tutorial track.
  2. Define a typed interface

    • Annotate every workflow and task input and output.
    • Keep module import time free of network calls, data mutations, and secret retrieval. Isolate documented exceptions such as workflow_reference, which resolves the active workspace when its decorator is evaluated.
    • Use dataclasses and enums for structured parameters.
  3. Configure metadata and resources

    • Match metadata parameter keys to the workflow signature.
    • Start with named task decorators, then use custom_task only when measured requirements justify it.
  4. Validate in the execution image

    Fresh Nextflow and Snakemake projects must generate their version-compatible Python entrypoint before staging. In SDK 2.76.8, the staging branch does not generate one from --nf-script or --snakefile.

    latch register --staging .
    latch develop .
    

    Re-run staging registration after changing the Dockerfile or dependencies. Edits made inside the development container are not synced back.

  5. Register deliberately

    latch register --yes --open .
    

    Useful controls:

    latch register --workspace-id 12345 .
    latch register --mark-as-release .
    latch register --workflow-module wf.custom_entrypoint .
    

    Duplicate registration exits with status 2; it is not the same as a build failure.

  6. Launch only after reviewing cost and parameters

    • Prefer the Console or Latch MCP for interactive operation.
    • Prefer latch_cli.services.launch.launch_v2 for Python automation.
    • Do not use the deprecated latch launch CLI as a new integration pattern.
  7. Monitor and verify

    • Check terminal status, task logs, result links, and scientific outputs.
    • Treat successful orchestration as necessary but not sufficient scientific validation.

Operational Safety

  • Ask for confirmation before launching paid compute, especially GPU or large batch runs.
  • Ask for confirmation before LPath.rmr, latch rmr, Registry deletion, or overwriting shared destinations.
  • Never log secrets, SDK tokens, signed URLs, or secret values.
  • Call get_secret() only inside a task, use the returned value only for its intended service, and never return it as workflow output.
  • Do not pass untrusted strings through shell commands. Prefer argument lists with subprocess.run(..., check=True).
  • Pin the SDK and workflow dependencies for releases. Upgrade only after reviewing the changelog and re-running staging tests.
  • Treat generated files as generated: customize the documented extension file rather than editing output that the CLI will overwrite.

Inspect the Installed SDK

From this skill directory:

uv run --no-project --python 3.12 --with "latch==2.76.8" \
  python scripts/inspect_latch_sdk.py

Use JSON output for automated comparisons:

uv run --no-project --python 3.12 --with "latch==2.76.8" \
  python scripts/inspect_latch_sdk.py --json

Authoritative Sources

Related skills

  • dnanexus-integration: Build and operate reproducible genomics workloads on DNAnexus with the dx CLI, dxpy, apps/applets, native workflows, dxCompiler, and Nextfl…
  • nextflow: Build, run, and debug Nextflow data pipelines and nf-core workflows end to end.
  • benchling-integration: Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse…

Trigger Prompts & Evaluation Corpus

These evaluation prompts test that the agent correctly selects latchbio-integration for relevant tasks and leaves it out for near misses.

Should trigger (3)

  • should trigger

    “How do I give my Latch task more memory and a GPU?”

    expects Explains using the named task decorators (e.g. small/large GPU tasks) from the Latch SDK, or custom_task only when measured needs justify it, to set CPU, memory, storage and GPU. Notes that GPU runs cost money and should be confirmed before launching, and points to the resource configuration guidance.

  • should trigger

    “I have a Snakemake pipeline for ATAC-seq on mouse samples (Snakefile plus config.yaml, Dockerfile already written). I want to get it onto Latch so my collaborators can launch it from a form. `latch register --snakefile Snakefile --staging` ran but it fails to find a workflow entrypoint. What's going wrong and what should I do?”

    expects Identifies that in SDK 2.76.8 the staging path does not generate the Python entrypoint from --snakefile, so the version-compatible entrypoint must be generated first (e.g. via latch init/generate for Snakemake) before staging. Warns not to mix commands from the legacy flag path and the separately pinned Snakemake v2 tutorial track, and suggests checking the installed SDK version and then registering, with metadata for the launch form.

  • should trigger

    “We have a few hundred FASTQ files sitting in a cloud workspace and a sample table with metadata. I want to script a batch of alignment runs over them from Python, track each one until it finishes, and pull the results back into the sample table. Can you lay out the approach?”

    expects Recommends programmatic launching via latch_cli.services.launch.launch_v2 (not the deprecated `latch launch` CLI), reading samples from Latch Registry and writing results back via a Registry transaction, using LPath for data paths, and monitoring execution status. Asks for cost and parameter confirmation before launching a large batch, and advises verifying scientific outputs rather than trusting successful orchestration alone.

Near misses (2)

  • near miss

    “I want to run nf-core/rnaseq on my local cluster with Slurm for 24 human RNA-seq samples. How do I write the samplesheet.csv and configure the executor in nextflow.config?”

    expects Should be handled by the nextflow skill: gives the nf-core/rnaseq samplesheet format (sample, fastq_1, fastq_2, strandedness) and a Slurm executor profile in nextflow.config, with no Latch-specific registration or platform steps.

  • near miss

    “How do I upload files to a DNAnexus project and launch an applet from the dx CLI?”

    expects Should be handled by the dnanexus-integration skill: uses dx upload and dx run with the applet and inputs, with no Latch SDK or CLI content.