[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74YWVYZS6004BDFBJJDASWP":3,"skill-same:01M74YWVYZS6004BDFBJJDASWP":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M74YWVYZS6004BDFBJJDASWP","latchbio-integration",null,"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.","KalarisLabs\u002Fresearch-agent-skills","KalarisLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300878568?v=4","01M74Y7MT23GXXC56VM6TVSXZY","Kalarislabs","01M74Y7MTQM9REXZX4SNXWX95C",132,"MIT","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: latchbio-integration\ndescription: 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.\nlicense: MIT\ncompatibility: 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.\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: '2.1'\n  category: lab-automation\n  maintainer: Kalaris Labs\n  tags: bioinformatics workflows, cloud computing, Nextflow, Snakemake, Latch\n---\n\n# LatchBio Integration\n\n## Current Baseline\n\nThis skill targets **Latch SDK 2.76.8**, released July 10, 2026. The package\nmetadata supports Python 3.9–3.12 and declares Python 3.9+.\n\nTreat the installed package and its changelog as authoritative when a guide\ndisagrees with the SDK. Some Latch guides retain older Python ranges or\ncompatibility-specific pre-release pins, especially the Snakemake v2 tutorial.\nNever combine commands or imports from different tracks without checking their\nversion requirements.\n\n## When to Use\n\nUse this skill to:\n\n- Create or maintain Python SDK workflows and task graphs\n- Package and register Python, Nextflow, or Snakemake pipelines\n- Configure task CPU, memory, storage, GPU, caching, retries, and timeouts\n- Work with Latch Data through `LPath`, `LatchFile`, `LatchDir`, or the CLI\n- Read or update Latch Registry projects, tables, and records\n- Design workflow forms, launch plans, samplesheets, messages, and result links\n- Stage and debug workflow images with `latch register --staging` and `latch develop`\n- Launch and monitor workflows through Python or Latch MCP\n- Discover and use ready-to-run Latch workflows\n\n## Route to the Right Reference\n\nRead only the references needed for the task:\n\n| Need | Reference |\n|---|---|\n| Python workflows, tasks, maps, conditions, caching | `references\u002Fworkflow-creation.md` |\n| `LPath`, legacy file types, Latch URLs, data CLI | `references\u002Fdata-management.md` |\n| Registry reads, transactions, samplesheets | `references\u002Fregistry.md` |\n| CPU, memory, storage, GPU, dynamic resources | `references\u002Fresource-configuration.md` |\n| Nextflow and Snakemake packaging | `references\u002Fnextflow-snakemake.md` |\n| Metadata, forms, launch plans, messages, automations | `references\u002Fui-and-automation.md` |\n| Registration, development, execution, monitoring | `references\u002Foperations-and-debugging.md` |\n| Ready-to-use workflows and `latch.verified` | `references\u002Fverified-workflows.md` |\n| Remote MCP setup and tool workflow | `references\u002Flatch-mcp.md` |\n\nBefore relying on a symbol, run `scripts\u002Finspect_latch_sdk.py` against the\ntarget SDK version. It performs local imports only and does not authenticate or\nmake network requests.\n\n## Installation and Authentication\n\nFor a reproducible environment:\n\n```bash\nuv venv --python 3.12\nsource .venv\u002Fbin\u002Factivate\nuv pip install \"latch==2.76.8\"\n```\n\nOn Windows, use WSL for the documented Linux workflow tooling.\n\nAuthenticate through the supported OAuth flow; do not read, print, copy, or\nparse `~\u002F.latch\u002Ftoken` manually:\n\n```bash\nlatch login\nlatch workspace\n```\n\nSelect a workspace non-interactively when its numeric ID is already known:\n\n```bash\nlatch workspace --id 12345\n```\n\n`latch login` credentials are for the SDK and CLI. Latch MCP uses a separate\nOAuth authorization and its credentials cannot be reused for general SDK\naccess.\n\n## Fast Path\n\nCreate and remotely register the maintained subprocess template:\n\n```bash\nlatch init covid-wf --template subprocess\nlatch register --yes --open covid-wf\n```\n\nRemote image building is the default. Use `--no-remote` only when a local\nDocker daemon is available and a local build is intentional.\n\n## Minimal Python Workflow\n\nKeep workflow bodies declarative: invoke tasks and return their promises.\nPerform computation and side effects inside tasks.\n\n```python\nfrom latch import small_task, workflow\n\n\n@small_task\ndef reverse_complement(sequence: str) -> str:\n    table = str.maketrans(\"ACGTacgt\", \"TGCAtgca\")\n    return sequence.translate(table)[::-1]\n\n\n@workflow\ndef reverse_complement_workflow(sequence: str) -> str:\n    \"\"\"Return the reverse complement of a DNA sequence.\"\"\"\n    return reverse_complement(sequence=sequence)\n```\n\nUse `@workflow(metadata)` when the generated interface needs custom labels,\nsections, validation rules, samplesheets, or documentation links. Use `LatchFile` or\n`LatchDir` for automatic task input staging and output upload; use `LPath` for\nimperative remote path operations.\n\n## Recommended Development Lifecycle\n\n1. **Inspect compatibility**\n   - Confirm the installed SDK and Python version.\n   - Identify whether the project is Python, Nextflow, the legacy Snakemake\n     flag path, or the separately pinned Snakemake v2 tutorial track.\n\n2. **Define a typed interface**\n   - Annotate every workflow and task input and output.\n   - Keep module import time free of network calls, data mutations, and secret\n     retrieval. Isolate documented exceptions such as `workflow_reference`,\n     which resolves the active workspace when its decorator is evaluated.\n   - Use dataclasses and enums for structured parameters.\n\n3. **Configure metadata and resources**\n   - Match metadata parameter keys to the workflow signature.\n   - Start with named task decorators, then use `custom_task` only when measured\n     requirements justify it.\n\n4. **Validate in the execution image**\n\n   Fresh Nextflow and Snakemake projects must generate their\n   version-compatible Python entrypoint before staging. In SDK 2.76.8, the\n   staging branch does not generate one from `--nf-script` or `--snakefile`.\n\n   ```bash\n   latch register --staging .\n   latch develop .\n   ```\n\n   Re-run staging registration after changing the Dockerfile or dependencies.\n   Edits made inside the development container are not synced back.\n\n5. **Register deliberately**\n\n   ```bash\n   latch register --yes --open .\n   ```\n\n   Useful controls:\n\n   ```bash\n   latch register --workspace-id 12345 .\n   latch register --mark-as-release .\n   latch register --workflow-module wf.custom_entrypoint .\n   ```\n\n   Duplicate registration exits with status `2`; it is not the same as a build\n   failure.\n\n6. **Launch only after reviewing cost and parameters**\n   - Prefer the Console or Latch MCP for interactive operation.\n   - Prefer `latch_cli.services.launch.launch_v2` for Python automation.\n   - Do not use the deprecated `latch launch` CLI as a new integration pattern.\n\n7. **Monitor and verify**\n   - Check terminal status, task logs, result links, and scientific outputs.\n   - Treat successful orchestration as necessary but not sufficient scientific\n     validation.\n\n## Operational Safety\n\n- Ask for confirmation before launching paid compute, especially GPU or large\n  batch runs.\n- Ask for confirmation before `LPath.rmr`, `latch rmr`, Registry deletion, or\n  overwriting shared destinations.\n- Never log secrets, SDK tokens, signed URLs, or secret values.\n- Call `get_secret()` only inside a task, use the returned value only for its\n  intended service, and never return it as workflow output.\n- Do not pass untrusted strings through shell commands. Prefer argument lists\n  with `subprocess.run(..., check=True)`.\n- Pin the SDK and workflow dependencies for releases. Upgrade only after\n  reviewing the changelog and re-running staging tests.\n- Treat generated files as generated: customize the documented extension file\n  rather than editing output that the CLI will overwrite.\n\n## Inspect the Installed SDK\n\nFrom this skill directory:\n\n```bash\nuv run --no-project --python 3.12 --with \"latch==2.76.8\" \\\n  python scripts\u002Finspect_latch_sdk.py\n```\n\nUse JSON output for automated comparisons:\n\n```bash\nuv run --no-project --python 3.12 --with \"latch==2.76.8\" \\\n  python scripts\u002Finspect_latch_sdk.py --json\n```\n\n## Authoritative Sources\n\n- Documentation index: https:\u002F\u002Fwiki.latch.bio\u002Fllms.txt\n- Workflow and SDK guides: https:\u002F\u002Fwiki.latch.bio\u002Fworkflows\u002Foverview\n- SDK API reference: https:\u002F\u002Fwiki.latch.bio\u002Freference\u002Fsdk\n- PyPI package: https:\u002F\u002Fpypi.org\u002Fproject\u002Flatch\u002F\n- SDK 2.76.8 release source: https:\u002F\u002Fgithub.com\u002Flatchbio\u002Flatch\u002Ftree\u002F0faa9dcd8186444ac008f50adf95d43f0fa30e06\n- SDK changelog: https:\u002F\u002Fgithub.com\u002Flatchbio\u002Flatch\u002Fblob\u002F0faa9dcd8186444ac008f50adf95d43f0fa30e06\u002FCHANGELOG.md\n- Latch Console: https:\u002F\u002Fconsole.latch.bio\n\n## Related skills\n\n- `dnanexus-integration`: Build and operate reproducible genomics workloads on DNAnexus with the dx CLI, dxpy, apps\u002Fapplets, native workflows, dxCompiler, and Nextfl…\n- `nextflow`: Build, run, and debug Nextflow data pipelines and nf-core workflows end to end.\n- `benchling-integration`: Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse…\n","# LatchBio Integration\n\n## Current Baseline\n\nThis skill targets **Latch SDK 2.76.8**, released July 10, 2026. The package\nmetadata supports Python 3.9–3.12 and declares Python 3.9+.\n\nTreat the installed package and its changelog as authoritative when a guide\ndisagrees with the SDK. Some Latch guides retain older Python ranges or\ncompatibility-specific pre-release pins, especially the Snakemake v2 tutorial.\nNever combine commands or imports from different tracks without checking their\nversion requirements.\n\n## When to Use\n\nUse this skill to:\n\n- Create or maintain Python SDK workflows and task graphs\n- Package and register Python, Nextflow, or Snakemake pipelines\n- Configure task CPU, memory, storage, GPU, caching, retries, and timeouts\n- Work with Latch Data through `LPath`, `LatchFile`, `LatchDir`, or the CLI\n- Read or update Latch Registry projects, tables, and records\n- Design workflow forms, launch plans, samplesheets, messages, and result links\n- Stage and debug workflow images with `latch register --staging` and `latch develop`\n- Launch and monitor workflows through Python or Latch MCP\n- Discover and use ready-to-run Latch workflows\n\n## Route to the Right Reference\n\nRead only the references needed for the task:\n\n| Need | Reference |\n|---|---|\n| Python workflows, tasks, maps, conditions, caching | `references\u002Fworkflow-creation.md` |\n| `LPath`, legacy file types, Latch URLs, data CLI | `references\u002Fdata-management.md` |\n| Registry reads, transactions, samplesheets | `references\u002Fregistry.md` |\n| CPU, memory, storage, GPU, dynamic resources | `references\u002Fresource-configuration.md` |\n| Nextflow and Snakemake packaging | `references\u002Fnextflow-snakemake.md` |\n| Metadata, forms, launch plans, messages, automations | `references\u002Fui-and-automation.md` |\n| Registration, development, execution, monitoring | `references\u002Foperations-and-debugging.md` |\n| Ready-to-use workflows and `latch.verified` | `references\u002Fverified-workflows.md` |\n| Remote MCP setup and tool workflow | `references\u002Flatch-mcp.md` |\n\nBefore relying on a symbol, run `scripts\u002Finspect_latch_sdk.py` against the\ntarget SDK version. It performs local imports only and does not authenticate or\nmake network requests.\n\n## Installation and Authentication\n\nFor a reproducible environment:\n\n```bash\nuv venv --python 3.12\nsource .venv\u002Fbin\u002Factivate\nuv pip install \"latch==2.76.8\"\n```\n\nOn Windows, use WSL for the documented Linux workflow tooling.\n\nAuthenticate through the supported OAuth flow; do not read, print, copy, or\nparse `~\u002F.latch\u002Ftoken` manually:\n\n```bash\nlatch login\nlatch workspace\n```\n\nSelect a workspace non-interactively when its numeric ID is already known:\n\n```bash\nlatch workspace --id 12345\n```\n\n`latch login` credentials are for the SDK and CLI. Latch MCP uses a separate\nOAuth authorization and its credentials cannot be reused for general SDK\naccess.\n\n## Fast Path\n\nCreate and remotely register the maintained subprocess template:\n\n```bash\nlatch init covid-wf --template subprocess\nlatch register --yes --open covid-wf\n```\n\nRemote image building is the default. Use `--no-remote` only when a local\nDocker daemon is available and a local build is intentional.\n\n## Minimal Python Workflow\n\nKeep workflow bodies declarative: invoke tasks and return their promises.\nPerform computation and side effects inside tasks.\n\n```python\nfrom latch import small_task, workflow\n\n\n@small_task\ndef reverse_complement(sequence: str) -> str:\n    table = str.maketrans(\"ACGTacgt\", \"TGCAtgca\")\n    return sequence.translate(table)[::-1]\n\n\n@workflow\ndef reverse_complement_workflow(sequence: str) -> str:\n    \"\"\"Return the reverse complement of a DNA sequence.\"\"\"\n    return reverse_complement(sequence=sequence)\n```\n\nUse `@workflow(metadata)` when the generated interface needs custom labels,\nsections, validation rules, samplesheets, or documentation links. Use `LatchFile` or\n`LatchDir` for automatic task input staging and output upload; use `LPath` for\nimperative remote path operations.\n\n## Recommended Development Lifecycle\n\n1. **Inspect compatibility**\n   - Confirm the installed SDK and Python version.\n   - Identify whether the project is Python, Nextflow, the legacy Snakemake\n     flag path, or the separately pinned Snakemake v2 tutorial track.\n\n2. **Define a typed interface**\n   - Annotate every workflow and task input and output.\n   - Keep module import time free of network calls, data mutations, and secret\n     retrieval. Isolate documented exceptions such as `workflow_reference`,\n     which resolves the active workspace when its decorator is evaluated.\n   - Use dataclasses and enums for structured parameters.\n\n3. **Configure metadata and resources**\n   - Match metadata parameter keys to the workflow signature.\n   - Start with named task decorators, then use `custom_task` only when measured\n     requirements justify it.\n\n4. **Validate in the execution image**\n\n   Fresh Nextflow and Snakemake projects must generate their\n   version-compatible Python entrypoint before staging. In SDK 2.76.8, the\n   staging branch does not generate one from `--nf-script` or `--snakefile`.\n\n   ```bash\n   latch register --staging .\n   latch develop .\n   ```\n\n   Re-run staging registration after changing the Dockerfile or dependencies.\n   Edits made inside the development container are not synced back.\n\n5. **Register deliberately**\n\n   ```bash\n   latch register --yes --open .\n   ```\n\n   Useful controls:\n\n   ```bash\n   latch register --workspace-id 12345 .\n   latch register --mark-as-release .\n   latch register --workflow-module wf.custom_entrypoint .\n   ```\n\n   Duplicate registration exits with status `2`; it is not the same as a build\n   failure.\n\n6. **Launch only after reviewing cost and parameters**\n   - Prefer the Console or Latch MCP for interactive operation.\n   - Prefer `latch_cli.services.launch.launch_v2` for Python automation.\n   - Do not use the deprecated `latch launch` CLI as a new integration pattern.\n\n7. **Monitor and verify**\n   - Check terminal status, task logs, result links, and scientific outputs.\n   - Treat successful orchestration as necessary but not sufficient scientific\n     validation.\n\n## Operational Safety\n\n- Ask for confirmation before launching paid compute, especially GPU or large\n  batch runs.\n- Ask for confirmation before `LPath.rmr`, `latch rmr`, Registry deletion, or\n  overwriting shared destinations.\n- Never log secrets, SDK tokens, signed URLs, or secret values.\n- Call `get_secret()` only inside a task, use the returned value only for its\n  intended service, and never return it as workflow output.\n- Do not pass untrusted strings through shell commands. Prefer argument lists\n  with `subprocess.run(..., check=True)`.\n- Pin the SDK and workflow dependencies for releases. Upgrade only after\n  reviewing the changelog and re-running staging tests.\n- Treat generated files as generated: customize the documented extension file\n  rather than editing output that the CLI will overwrite.\n\n## Inspect the Installed SDK\n\nFrom this skill directory:\n\n```bash\nuv run --no-project --python 3.12 --with \"latch==2.76.8\" \\\n  python scripts\u002Finspect_latch_sdk.py\n```\n\nUse JSON output for automated comparisons:\n\n```bash\nuv run --no-project --python 3.12 --with \"latch==2.76.8\" \\\n  python scripts\u002Finspect_latch_sdk.py --json\n```\n\n## Authoritative Sources\n\n- Documentation index: https:\u002F\u002Fwiki.latch.bio\u002Fllms.txt\n- Workflow and SDK guides: https:\u002F\u002Fwiki.latch.bio\u002Fworkflows\u002Foverview\n- SDK API reference: https:\u002F\u002Fwiki.latch.bio\u002Freference\u002Fsdk\n- PyPI package: https:\u002F\u002Fpypi.org\u002Fproject\u002Flatch\u002F\n- SDK 2.76.8 release source: https:\u002F\u002Fgithub.com\u002Flatchbio\u002Flatch\u002Ftree\u002F0faa9dcd8186444ac008f50adf95d43f0fa30e06\n- SDK changelog: https:\u002F\u002Fgithub.com\u002Flatchbio\u002Flatch\u002Fblob\u002F0faa9dcd8186444ac008f50adf95d43f0fa30e06\u002FCHANGELOG.md\n- Latch Console: https:\u002F\u002Fconsole.latch.bio\n\n## Related skills\n\n- `dnanexus-integration`: Build and operate reproducible genomics workloads on DNAnexus with the dx CLI, dxpy, apps\u002Fapplets, native workflows, dxCompiler, and Nextfl…\n- `nextflow`: Build, run, and debug Nextflow data pipelines and nf-core workflows end to end.\n- `benchling-integration`: Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse…\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":29,"compatibility":30},{"tags":25,"version":26,"category":27,"maintainer":28},"bioinformatics workflows, cloud computing, Nextflow, Snakemake, Latch","2.1","lab-automation","Kalaris Labs","Read Write Edit Bash","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.","main","29fe36d26127205057d5e0ed8425f6b0e9a8c13a","skills\u002Flatchbio-integration",16,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills","https:\u002F\u002Fdocs.kalarislabs.com\u002Fresearch-agent-skills","https:\u002F\u002Fgithub.com\u002FKalarisLabs","kalarislabs.com","Applied AI lab building the infrastructure for the agentic era","2026-11-14 17:49:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add KalarisLabs\u002Fresearch-agent-skills --skill latchbio-integration",{"tool":47,"command":48},"bunx","bunx skills add KalarisLabs\u002Fresearch-agent-skills --skill latchbio-integration",{"tool":50,"command":51},"pnpm","pnpm dlx skills add KalarisLabs\u002Fresearch-agent-skills --skill latchbio-integration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002FSKILL.md",true,[55,61,65,69,73,77,81,85,89,93],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdata-management.md","REFERENCE","参考文档",7417,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fdata-management.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Flatch-mcp.md",4474,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Flatch-mcp.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fnextflow-snakemake.md",8564,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fnextflow-snakemake.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Foperations-and-debugging.md",8545,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Foperations-and-debugging.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fregistry.md",7441,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fregistry.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fresource-configuration.md",7604,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fresource-configuration.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fui-and-automation.md",9490,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fui-and-automation.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fverified-workflows.md",6631,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fverified-workflows.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fworkflow-creation.md",8234,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Freferences\u002Fworkflow-creation.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Finspect_latch_sdk.py","SCRIPT","脚本",9254,"https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Flatchbio-integration\u002Fscripts\u002Finspect_latch_sdk.py",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M74Z8MGT305R11SNY5G28QH5","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.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fplos\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M74Z8CCN9APXYHNQ95V1EBGT","pkpd-modeling","Pharmacokinetic and pharmacodynamic modelling and simulation - non-compartmental analysis, compartmental and population PK, PK\u002FPD 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\u002FPD\", \"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\".","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpkpd-modeling\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M74Z86YHJJ1FM3X87BHN76KZ","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).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpinecone\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M74Z80T6E89SAJ8MYDD0767Q","pi-agent","Build with and use Pi, the minimal terminal coding harness. Use for installing Pi, configuring providers\u002Fmodels\u002Fsettings\u002Fenvironment variables, creating Pi skills\u002Fextensions\u002Fpackages\u002Fthemes\u002Fprompt 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\u002Forchestration), pi-mcp-adapter (MCP servers), pi-interview (interactive forms), and pi-web-access (web search, fetching, video understanding).","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpi-agent\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M74Z7WF1Y8Q3VFAQPPPRAFMV","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.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fphoenix-observability\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M74Z7HNEH1A2AVYR3G1X2QV6","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.","https:\u002F\u002Fgithub.com\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpeft-fine-tuning\u002FSKILL.md",[],[]]