Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .claude/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .agents/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .cursor/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .gemini/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .github/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "msa-structure-prediction-pipeline" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/bionemo-msa-structure-prediction-pipeline into .opencode/skills/msa-structure-prediction-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "msa-structure-prediction-pipeline", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
msa-structure-prediction-pipeline
GitHub stars
3.5k
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
287 words
Files
5
Skills in repo
386
Repo updated
First seen
Licence
Apache-2.0
At a glance
NOTE: your protein sequence and the retrieved MSA alignment are transmitted to external NVIDIA-hosted APIs (health.api.nvidia.com) on every call.
Works in 2 steps: Search for MSA with MSA-Search → Predict structure with OpenFold3
The user wants to predict a protein structure with maximum accuracy using MSA context
SKILL.md covers Overview, Before you start, Step 1: Search for MSA with… and Step 2: Predict structure with…, plus 3 more sections
Reaches health.api.nvidia.com; needs NGC_API_KEY
What it does
Msa Structure Prediction Pipeline is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. NOTE: your protein sequence and the retrieved MSA alignment are transmitted to external NVIDIA-hosted APIs (health.api.nvidia.com) on every call. Use local NIM containers for confidential or proprietary sequences. Run a complete protein structure prediction pipeline using NVIDIA BioNeMo NIMs: search for MSA alignments with MSA-Search (ColabFold), then predict the structure with OpenFold3 using the retrieved alignments. Use this skill whenever the user wants to predict a protein structure with maximum accuracy…
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).
It sits in Research & Science, covering Protein structure and design and Microservices. It works with NVIDIA AI Platform. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.
When your agent uses it
The user wants to predict a protein structure with maximum accuracy using MSA context
Run the full AlphaFold3-style pipeline
Generate MSA-informed structure predictions
Improve structure prediction accuracy by providing evolutionary information
Read from SKILL.md and the folder at commit dfdd080. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash
Read
Write
AskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
health.api.nvidia.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
NGC_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Msa Structure Prediction Pipeline loads about 1.6k tokens when it runs. Until then it costs about 252 tokens; SKILL.md has 287 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~252
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Write, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/msa-structure-prediction-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
msa-structure-prediction-pipeline
description
NOTE: your protein sequence and the retrieved MSA alignment are transmitted to external NVIDIA-hosted APIs (health.api.nvidia.com) on every call. Use local NIM containers for confidential or proprietary sequences. Run a complete protein structure prediction pipeline using NVIDIA BioNeMo NIMs: search for MSA alignments with MSA-Search (ColabFold), then predict the structure with OpenFold3 using the retrieved alignments. Use this skill whenever the user wants to predict a protein structure with maximum accuracy using MSA context, run the full AlphaFold3-style pipeline, generate MSA-informed structure predictions, or improve structure prediction accuracy by providing evolutionary information. Triggers on: MSA structure prediction pipeline, structure prediction pipeline, MSA-informed prediction, OpenFold3, ColabFold MSA, AlphaFold3 pipeline, protein structure, homology search, a3m alignment, UniRef30, NIM microservice. This pipeline chains MSA-Search and OpenFold3.
allowed-tools
Bash, Read, Write, AskUserQuestion
license
Apache-2.0 AND CC-BY-4.0
MSA Structure Prediction Pipeline
Predict protein structures with high accuracy by chaining two BioNeMo NIMs:
MSA-Search finds evolutionary homologs in UniRef30 and ColabFold databases using GPU-accelerated MMSeqs2. The resulting alignment provides crucial evolutionary information.
OpenFold3 uses the MSA to improve structure prediction accuracy — especially for sequences where no close homolog exists in PDB.
Running MSA-Search first means OpenFold3 gets the full evolutionary context rather than a single-sequence prediction.
Before you start
Confirm with the user:
Query sequence: amino acid sequence to predict
MSA depth: how many sequences to retrieve (default 500; more = slower but more context)
API mode: hosted or local Docker?
Note: local MSA-Search requires 1.4 TB of database storage — strongly recommend hosted unless the user has that infrastructure.
For local Docker, do not assume MSA-Search and OpenFold3 are both on
localhost:8000 concurrently. Run one container at a time and hand off the A3M
file, or start each NIM on a distinct host port and set the URLs explicitly.
Step 1: Search for MSA with MSA-Search
python
import requests, json, os
from pathlib import Path
NGC_API_KEY = os.getenv("NGC_API_KEY")
HOSTED = True
query_sequence = "<YOUR_PROTEIN_SEQUENCE>"
if HOSTED:
msa_url = "https://health.api.nvidia.com/v1/biology/colabfold/msa-search/predict"
headers = {"Content-Type": "application/json",
"Authorization": f"Bearer {NGC_API_KEY}"}
else:
msa_url = "http://localhost:8000/biology/colabfold/msa-search/predict"
headers = {"Content-Type": "application/json"}
payload = {
"sequence": query_sequence,
"databases": ["Uniref30_2302", "colabfold_envdb_202108"],
"e_value": 0.0001,
"output_alignment_formats": ["a3m"],
}
r = requests.post(msa_url, headers=headers, json=payload)
r.raise_for_status()
msa_result = r.json()
# Extract the A3M alignment
a3m_alignment = msa_result["alignments"]["Uniref30_2302"]["a3m"]["alignment"]
# Save for reference
with open("query_msa.a3m", "w") as f:
f.write(a3m_alignment)
# Count sequences in alignment
n_seqs = a3m_alignment.count(">")
print(f"Step 1 complete: found {n_seqs} homologous sequences")
print(f"MSA saved to query_msa.a3m")
Step 2: Predict structure with OpenFold3
Pass the MSA directly into OpenFold3's msa field:
python
if HOSTED:
of3_url = "https://health.api.nvidia.com/v1/biology/openfold/openfold3/predict"
else:
of3_url = "http://localhost:8000/biology/openfold/openfold3/predict"
# Build the OpenFold3 MSA structure from the retrieved alignment
msa_data = {
"uniref30": {
"a3m": {
"alignment": a3m_alignment,
"format": "a3m"
}
}
}
# Optionally also include colabfold_envdb alignment if requested
# env_alignment = msa_result["alignments"]["colabfold_envdb"]["a3m"]["alignment"]
# msa_data["colabfold_env"] = {"a3m": {"alignment": env_alignment, "format": "a3m"}}
payload = {
"inputs": [{
"input_id": "prediction_with_msa",
"output_format": "pdb",
"molecules": [
{
"type": "protein",
"sequence": query_sequence,
"diffusion_samples": 1,
"msa": msa_data
}
]
}]
}
r = requests.post(of3_url, headers=headers, json=payload, timeout=300)
r.raise_for_status()
result = r.json()
output = result["outputs"][0]
for i, sample in enumerate(output["structures_with_scores"]):
fmt = sample["format"]
filename = f"predicted_structure_{i+1}.{fmt}"
with open(filename, "w") as f:
f.write(sample["structure"])
print(f"\nStep 2 complete: {filename} saved")
print(f" Confidence: {sample['confidence_score']:.4f}")
print(f" pLDDT: {sample['complex_plddt_score']:.4f}")
print(f" pTM: {sample['ptm_score']:.4f}")
Comparing single-sequence vs MSA-informed prediction
If the user wants to see the impact of MSA, run OpenFold3 twice — once with the full MSA and once with just the query sequence as a minimal alignment:
python
# Minimal MSA (single sequence — same as no MSA context):
minimal_msa = {
"main": {
"a3m": {
"alignment": f">query\n{query_sequence}",
"format": "a3m"
}
}
}
A larger, higher-quality MSA typically yields higher pLDDT and lower pDE, especially for proteins with many known homologs.
For protein complexes
Use the /paired/predict endpoint of MSA-Search to get paired alignments for multi-chain complexes, then pass each chain's alignment into the corresponding molecule's msa field and paired_msa fields:
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NVIDIA/skills, which our catalogue first saw on October 7, 2026.
Msa Structure Prediction Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Msa Structure Prediction Pipeline compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Msa Structure Prediction Pipeline this skillNVIDIA/skills
Run a complete protein binder design campaign with NVIDIA Proteina-Complexa: resolve a target structure and hotspots from a name/sequence/PDB, co-design binder sequence+structure with reward-guided…
Add agent-ready vision capabilities — dense captioning, detection, search, alerting, summarization — to an agent or application through a customizable, self-contained vision stack built on the…
A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.
NOTE: your protein sequence and the retrieved MSA alignment are transmitted to external NVIDIA-hosted APIs (health.api.nvidia.com) on every call. Msa Structure Prediction Pipeline is an agent skill from NVIDIA/skills, published by the product's own GitHub organization.com) on every call.
When should I use Msa Structure Prediction Pipeline?
Msa Structure Prediction Pipeline fits situations like: the user wants to predict a protein structure with maximum accuracy using MSA context; run the full AlphaFold3-style pipeline; generate MSA-informed structure predictions; improve structure prediction accuracy by providing evolutionary information.
How do I install Msa Structure Prediction Pipeline in Claude Code?
Run `npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a claude-code`. Or copy the skill folder (skills/bionemo-msa-structure-prediction-pipeline in NVIDIA/skills) into .claude/skills/msa-structure-prediction-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Msa Structure Prediction Pipeline in Codex?
Run `npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a codex`. Or copy the skill folder (skills/bionemo-msa-structure-prediction-pipeline in NVIDIA/skills) into .agents/skills/msa-structure-prediction-pipeline in your project. Codex loads it when a task matches its description.
Can I use Msa Structure Prediction Pipeline in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill msa-structure-prediction-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/msa-structure-prediction-pipeline, .gemini/skills/msa-structure-prediction-pipeline, .github/skills/msa-structure-prediction-pipeline and .opencode/skills/msa-structure-prediction-pipeline in your project.
What does Msa Structure Prediction Pipeline need to run?
Going by SKILL.md and its folder, Msa Structure Prediction Pipeline needs credentials named NGC_API_KEY. Our summary lists: Python 3; Docker; A credential in NGC_API_KEY. Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion.
Does Msa Structure Prediction Pipeline access the network?
SKILL.md names 1 domain. In commands or code: health.api.nvidia.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Msa Structure Prediction Pipeline safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Msa Structure Prediction Pipeline use?
Msa Structure Prediction Pipeline is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Msa Structure Prediction Pipeline use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Msa Structure Prediction Pipeline?
Skills that share tags, products or a category with Msa Structure Prediction Pipeline: Complexa Binder Design (NVIDIA-BioNeMo/bionemo-agent-toolkit, 478 stars), Proteina Complexa (BioTender-max/awesome-bio-agent-skills, 199 stars), Vss Build Vision AI (NVIDIA-AI-Blueprints/video-search-and-summarization, 1.9k stars) and Fda Database (jaechang-hits/SciAgent-Skills, 371 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Msa Structure Prediction Pipeline?
NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,546 GitHub stars. The repository holds 386 skills in this directory. The repository was last updated on October 9, 2026.
Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.