Tencent tFold Antigen Antibody Complex Structure Prediction Model

Problem

Nextflow omics apps such as tFold Collection (Nextflow) usually require checking login state, project configuration, sub-app AppId, Nextflow version, and import name before submission. Manual command assembly can accidentally use the collection AppId as a runnable app, or import a duplicate name and fail.

How It Works

• Scoped collection: only runs the 4 sub-apps in tFold Collection (Nextflow), including tFold_ab_predict, tFold_ag_predict, tFold_ag_predict_icf, and tFold_tcr_predict.
• Preflight checks: verifies omics CLI, whoami, and config show; C-end users also get quota checks before the first submission and before each run.
• Execution guardrails: matches a target from the hardcoded sub-app list, blocks running the collection directly, performs duplicate-name checks, and asks for confirmation before omics run.
• Failure handling: gives explicit guidance for DUPLICATE_APP_NAME, missing nf-version, and authentication failures, and reminds users of the outdir result path.

Boundaries

This skill targets public app runs on the Tencent Health Omics Platform. It does not cover other platforms, project-owned apps, or out-of-scope direct CLI usage. Local file inputs must be uploaded to the user's bound COS bucket first.