AGENT SKILL

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.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 132
Forks
16

01 前言 Front Matter

name
latchbio-integration
license
MIT
metadata
{ "tags": "bioinformatics workflows, cloud computing, Nextflow, Snakemake, Latch", "version": "2.1", "category": "lab-automation", "maintainer": "Kalaris Labs" }
description
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.
allowed-tools
Read Write Edit Bash
compatibility
Requires network access and a Latch account. The current stable SDK requires Python 3.9+; Python 3.12 is recommended. Uses uv for installation. Docker is needed for local image builds, while remote registration is the CLI default.

02 资源文件 10

03 SKILL.md 正文

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…

04 同仓库更多 Skills

KalarisLabs
KalarisLabs/research-agent-skills

plos

Prepare manuscripts for PLOS journals (PLOS ONE, PLOS Biology, PLOS Computational Biology, PLOS Genetics, PLOS Medicine, PLOS Pathogens, PLOS Neglected Tropical Diseases, PLOS Global Public Health and others), covering structure, abstract and author summary, Vancouver-style references, the mandatory data availability policy, ethics and financial disclosure statements, figure requirements (PACE), the PLOS LaTeX template, reporting guidelines and PLOS ONE's publication criteria. Use when targeting any PLOS journal or checking compliance with PLOS policies.

★ 132
KalarisLabs
KalarisLabs/research-agent-skills

pkpd-modeling

Pharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK/PD and exposure-response, TMDD, PBPK orientation, bioequivalence, allometric scaling and first-in-human dose, drug interaction prediction, and Bayesian therapeutic drug monitoring. Use when analysing concentration-time data, deriving exposure metrics, fitting PK or PD models, or evaluating dosing regimens. Triggers include "pharmacokinetics", "pharmacodynamics", "PK/PD", "NCA", "non-compartmental", "AUC", "Cmax", "lambda z", "half-life", "clearance", "volume of distribution", "compartmental model", "population PK", "popPK", "NONMEM", "nlmixr2", "Pharmpy", "Monolix", "exposure-response", "Emax", "EC50", "indirect response", "effect compartment", "TMDD", "PBPK", "bioequivalence", "RSABE", "ABEL", "allometric scaling", "first-in-human", "MABEL", "drug-drug interaction", "DDI", "ICH M12", "concentration-QTc", "therapeutic drug monitoring", "MIPD", and "dosing regimen".

★ 132
KalarisLabs
KalarisLabs/research-agent-skills

pinecone

Guides use of Pinecone, a managed serverless vector database, through its Python client and the LangChain and LlamaIndex integrations. Covers creating indexes, upserting and querying vectors, metadata filtering, namespaces, hybrid dense and sparse search, index management, and deleting vectors. Use when building a production RAG system on a hosted vector store, adding semantic search or recommendations without running infrastructure, isolating per-user or per-tenant data with namespaces, combining dense and sparse vectors in one query, or filtering results by metadata. Do not use for self-hosted or local stores (Chroma, Weaviate) or offline similarity search (FAISS).

★ 132
KalarisLabs
KalarisLabs/research-agent-skills

pi-agent

Build with and use Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers/models/settings/environment variables, creating Pi skills/extensions/packages/themes/prompt templates, embedding Pi through the SDK, integrating over RPC or JSON event streams, parsing sessions, running local models through the llama.cpp router, developing custom Pi providers and TUI components, or using ecosystem packages such as pi-subagents (delegation/orchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).

★ 132
KalarisLabs
KalarisLabs/research-agent-skills

phoenix-observability

Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.

★ 132
KalarisLabs
KalarisLabs/research-agent-skills

peft-fine-tuning

Fine-tunes LLMs with Hugging Face PEFT, using LoRA, QLoRA, IA3, AdaLoRA, prefix tuning, and prompt tuning so that under 1% of parameters are trained. Covers rank, alpha, and target module selection, loading and merging adapters, multi-adapter serving, and integration with TRL SFTTrainer, Axolotl, and vLLM. Use when fine-tuning 7B-70B models on limited GPU memory, when running QLoRA on a single 24GB GPU, when choosing LoRA rank and alpha, when merging or swapping adapters on one base model, or when debugging CUDA OOM or an adapter that does not apply. Not for full fine-tuning of small models under 1B parameters or cases needing all weights updated.

★ 132