Official agent skill

Msa Search Nim

by NVIDIA in NVIDIA/skills

Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM.

OfficialApache-2.0Auto-check: notesDevOps & Cloud

Install Msa Search Nim

skills CLI
$ npx skills add NVIDIA/skills --skill msa-search-nim -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/skills msa-search-nim --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bionemo-msa-search-nim .claude/skills/msa-search-nim && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
msa-search-nim
GitHub stars
3.5k
Used in
1 other repo
Token cost
~4.6k tokens
SKILL.md length
1,397 words
Files
15 (incl. scripts, references)
Skills in repo
386
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM.

  • UniRef30/ColabFold env searches
  • SKILL.md covers Choose Mode And Endpoint, Local Docker, Faster Startup: Task-Specific… and Recommended: Parallel Download…, plus 5 more sections
  • Runs Python scripts from its folder; calls docker, curl and python3; reaches health.api.nvidia.com and api.ngc.nvidia.com; needs NGC_API_KEY and NVIDIA_API_KEY
  • FASTA alignments

What it does

Msa Search Nim is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM. Use for homolog search, UniRef30/ColabFold env searches, A3M or FASTA alignments, paired MSA search for complexes, PDB70 structural templates, hosted NVIDIA API calls, or local Docker deployment. For local deployment, download the databases in parallel with aria2c and launch via NIMMODELNAME (the recommended default fast path, ~14 min vs over 80 min for the built-in downloader); a plain docker run uses the slow…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts and reference files (for example `BENCHMARK.md`, `config/skillspector-baseline.yml` and `evals/config.yml`). Compatibility notes: requests=2.28

It sits in DevOps & Cloud, covering Containers and Deployment. It works with NVIDIA AI Platform and Docker. 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

  • UniRef30/ColabFold env searches
  • FASTA alignments
  • Paired MSA search for complexes
  • PDB70 structural templates

Example prompts

  • “/msa-search-nim”

Requirements

  • Python 3
  • Docker
  • A credential in NGC_API_KEY
  • A credential in NVIDIA_API_KEY
  • Compatibility (from SKILL.md): requests>=2.28
  • Pre-approved tools (allowed-tools): Bash, Read, Write, AskUserQuestion

What it can do on your machine

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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • docker
    • curl
    • python3
    • jq
    • 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
    • api.ngc.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
    • NVIDIA_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    requests>=2.28

    From compatibility in the SKILL.md frontmatter.

Context cost

Msa Search Nim loads about 4.6k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 139 tokens; SKILL.md has 1,397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~139
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8k

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.

  • NoteMentions a .env fileSKILL.md:62
    [ -f .env ] && . ./.env
  • 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); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit dfdd080, republished under its Apache-2.0 licence (© NVIDIA). 1,397 words, ~4,555 tokens.

Download SKILL.mdSave it as .claude/skills/msa-search-nim/SKILL.md (or your agent's skills folder). This skill also uses 14 other files; get the full folder from GitHub.
name
msa-search-nim
description
Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM. Use for homolog search, UniRef30/ColabFold env searches, A3M or FASTA alignments, paired MSA search for complexes, PDB70 structural templates, hosted NVIDIA API calls, or local Docker deployment. For local deployment, download the databases in parallel with aria2c and launch via NIM_MODEL_NAME (the recommended default fast path, ~14 min vs over 80 min for the built-in downloader); a plain docker run uses the slow built-in downloader.
allowed-tools
Bash, Read, Write, AskUserQuestion
compatibility
requests>=2.28
license
Apache-2.0 AND CC-BY-4.0
permissions
env, network

MSA-Search NIM

Generate protein MSAs with GPU-accelerated MMSeqs2. Use this guide for first-pass hosted/local usage; load supplemental files only when needed:

  • references/api.md: exact endpoints, schemas, Docker flags, response fields.
  • references/science.md: MSA purpose, pairing/templates, limits, handoffs.
  • references/parameters.md: database, pairing, depth, and template tuning.
  • references/validation.md: alignment, template, and artifact checks.
  • references/examples.md: compact hosted/local request patterns.

Choose Mode And Endpoint

Ask only when context is unclear:

Hosted NVIDIA API or local Docker NIM?

  • Hosted standard MSA: https://health.api.nvidia.com/v1/biology/colabfold/msa-search/predict
  • Hosted paired MSA: https://health.api.nvidia.com/v1/biology/colabfold/msa-search/paired/predict
  • Local standard MSA: http://localhost:8000/biology/colabfold/msa-search/predict
  • Local paired MSA: http://localhost:8000/biology/colabfold/msa-search/paired/predict
  • Local templates: http://localhost:8000/biology/colabfold/msa-search/structure-templates/predict

Local inference paths do not include /v1/. Hosted requests use Authorization: Bearer $NGC_API_KEY. Supported local Docker startup uses NGC_API_KEY (or NVIDIA_API_KEY via the preflight) for registry login, entitlement checks, and first-run model downloads; pass it into the container with -e NGC_API_KEY. Local inference requests use no auth header after readiness. Warm-cache key-free startup varies by image/version and should not be assumed. The hosted template path returned HTTP 404 in validation, so use local Docker for template search unless the hosted docs/service changes.

Local Docker

Default local deployment = parallel download + NIM_MODEL_NAME. The first recipe below is the one to use for real workflows. It downloads the database(s) with a range-parallel downloader (aria2c) and starts the NIM against those files — ~14 min for UniRef30 vs >80 min for the NIM's built-in downloader (measured, H100). Do not reach for the plain docker run (the "Fallback" subsection) unless you only want a databases:pdb70 smoke test or you deliberately want the NIM to manage its own blob cache.

Local setup requires a GPU. Size the NVMe volume to the profile you pick (UniRef30 ~490 GB; full set ~1.4 TB). For setup answers, include env preflight, docker login, the parallel download, NIM_MODEL_NAME launch, readiness, and then no-auth local inference. Do not invent a cache default or drop the NVIDIA_API_KEY fallback.

bash
# --- env preflight (do not drop the NVIDIA_API_KEY fallback) ---
set -a
[ -f .env ] && . ./.env
set +a
if [ -z "${NGC_API_KEY:-}" ] && [ -n "${NVIDIA_API_KEY:-}" ]; then
  export NGC_API_KEY="$NVIDIA_API_KEY"
fi
: "${NGC_API_KEY:?Set NGC_API_KEY or NVIDIA_API_KEY}"
: "${DB_DIR:=/data/fast-db}"          # where the parallel download lands

echo "$NGC_API_KEY" | docker login nvcr.io --username '$oauthtoken' --password-stdin

# --- 1) pick the DB version(s) you need (paired/complex work = uniref30 only) ---
DB_VERSION=uniref30_2302-m18v1
command -v aria2c >/dev/null || { echo "aria2c required; install it (e.g. apt-get install -y aria2) and re-run"; exit 1; }
mkdir -p "$DB_DIR"

# --- 2) parallel download from NGC (see "Parallel Download" section for the all-DB loop) ---
curl -fsS -H "Authorization: Bearer $NGC_API_KEY" \
  "https://api.ngc.nvidia.com/v2/org/nim/team/colabfold/models/msa-search/${DB_VERSION}/files" \
  -o /tmp/files.json
DB_DIR="$DB_DIR" python3 - <<'PY'
import json, os
d = json.load(open("/tmp/files.json")); dbdir = os.environ["DB_DIR"]; lines = []
for url, path in zip(d["urls"], d["filepath"]):
    lines += [url.strip(), f"  dir={dbdir}", f"  out={path}"]
open("/tmp/aria.in", "w").write("\n".join(lines) + "\n")
PY
aria2c -i /tmp/aria.in --max-concurrent-downloads=4 --max-connection-per-server=16 \
  --split=16 --min-split-size=1M --continue=true --file-allocation=none

# --- 3) launch the NIM against the downloaded files (skips the slow built-in download) ---
docker run -d --name msa-search --runtime=nvidia --gpus all \
  -e NGC_API_KEY \
  -e NIM_MODEL_NAME=/databases \
  -v "${DB_DIR}:/databases" \
  -p 8000:8000 \
  nvcr.io/nim/colabfold/msa-search:2

Readiness:

bash
until curl -sf http://localhost:8000/v1/health/ready; do sleep 5; done

If the DB is already present in $DB_DIR, skip steps 1-2 — the launch alone is a ~20 s warm start. See "Parallel Download For Any Database Set" for the multi-database (databases:all) loop and the full rationale.

Fallback: Let The NIM Download Its Own Databases (slower)

Use this only for a quick databases:pdb70 smoke test, or when you specifically want the NIM to manage its own blob cache. It uses the built-in downloader, which is slow on large profiles (UniRef30 stalled past 80 min in testing). Pin the smallest profile with NIM_MODEL_PROFILE (see "Faster Startup") so it does not fetch the full 1.4 TB.

bash
: "${LOCAL_NIM_CACHE:?Set LOCAL_NIM_CACHE}"
mkdir -p "${LOCAL_NIM_CACHE}"; chmod 755 "${LOCAL_NIM_CACHE}"
docker run --rm --name msa-search \
  --runtime=nvidia --gpus all \
  -e NGC_API_KEY \
  -e NIM_MODEL_PROFILE=<hash-from-list-model-profiles> \
  -v "${LOCAL_NIM_CACHE}:/opt/nim/.cache" \
  -p 8000:8000 \
  nvcr.io/nim/colabfold/msa-search:2

Faster Startup: Task-Specific Database Profiles

The full database download is ~1.4 TB and can take well over an hour on first launch. If you only need some databases, select a task-specific profile so the NIM downloads just those. This is the single biggest lever on local startup time.

List the profiles your image actually ships (hashes change between releases — never hardcode them):

bash
docker run --rm --entrypoint list-model-profiles nvcr.io/nim/colabfold/msa-search:2

Then pass the chosen hash with NIM_MODEL_PROFILE:

bash
docker run --rm --name msa-search \
  --runtime=nvidia --gpus all \
  -e NGC_API_KEY \
  -e NIM_MODEL_PROFILE=<hash-from-list-model-profiles> \
  -v "${LOCAL_NIM_CACHE}:/opt/nim/.cache" \
  -p 8000:8000 \
  nvcr.io/nim/colabfold/msa-search:2

Profiles available in this image (confirm hashes with list-model-profiles):

Profile tagsDatabasesBest forStorage
databases:pdb70PDB70Quick testing / smoke check~100 MB
databases:uniref30UniRef30Paired MSA search for complexes — UniRef30 is the only DB used for species-based pairing~500 GB
databases:uniref30,pdb70,pdbUniRef30 + PDB70 + PDB structuresStructural template search~700 GB
databases:all (default)UniRef30 + ColabFold envdb + PDB70 + PDB100 + PDB structuresFull sensitivity, all databases~1.2 TB

Verify the loaded profile after readiness:

bash
curl -s localhost:8000/v1/metadata | jq

Notes:

  • The request-level databases parameter only selects among databases already downloaded; it does NOT change what is fetched at startup. Startup footprint is set by NIM_MODEL_PROFILE alone.
  • Paired search needs UniRef30 only. colabfold_envdb_202108 has no taxonomy and cannot be used for pairing, so databases:uniref30 is the correct, smallest profile for complex/paired workflows — it skips the envdb, the largest part of the full set.
  • For maximum monomer sensitivity (UniRef30 + envdb merged) you still need databases:all; there is no envdb-inclusive profile smaller than the full set.
Custom Or Individual Databases

To use a single manually downloaded database (or your own MMSeqs2 DB), download it from NGC and point the NIM at the mount with NIM_MODEL_NAME instead of a profile:

bash
ngc registry model download-version nim/colabfold/msa-search:uniref30_2302-m18v1
# then mount the directory and set -e NIM_MODEL_NAME=/databases

NIM_MODEL_NAME replaces the profile databases entirely — the NIM uses only what is under that directory (discovered by scanning for **/*.idx). Mount multiple databases under one parent to combine them. NGC-downloaded databases are pre-indexed for GPU Server; custom databases must be indexed with mmseqs createindex first. Individually downloadable NGC model versions: uniref30_2302-m18v1, colabfold_envdb_202108-m18v1, pdb70_220313-m18v1, pdb100_230517-m18v1, pdb_20251028_zip-m18v1.

Show full SKILL.md (677 more words)Show less

This is the recommended way to download the databases at all — for any profile, including the full databases:all set. Task-specific profiles cut what you download; this parallel downloader cuts how long that download takes. Use it whether you need one database or all of them. The gain is largest for the databases:uniref30 profile, which is ~490 GB dominated by two very large files (a ~241 GB GPU index and a ~134 GB sequence DB).

The NIM's built-in downloader parallelizes across files (max_parallel_files=10) but pulls each file over roughly one connection. The NGC CDN throttles a single connection to ~20–25 MB/s, so while the downloader is fetching one of the two giant files, most of its parallel slots sit idle and throughput collapses to that single-flow rate. Measured on an H100 node, the built-in path did not reach /health/ready in over 80 minutes.

A range-parallel downloader splits each file into many byte-range segments (the NGC CDN advertises accept-ranges: bytes), so a single 241 GB file is pulled over 16 connections at once — ~15× the single-flow rate. Same node, aria2c fetched the full ~490 GB in ~13.5 minutes.

Workflow (download once with aria2, then start the NIM against the files via NIM_MODEL_NAME):

bash
# 1) Get presigned file URLs for the individual database model version from NGC.
#    (Requires NGC_API_KEY. The response arrays `urls` and `filepath` are positionally paired.)
curl -s -H "Authorization: Bearer $NGC_API_KEY" \
  'https://api.ngc.nvidia.com/v2/org/nim/team/colabfold/models/msa-search/uniref30_2302-m18v1/files' \
  -o files.json

# 2) Build an aria2 input file (URL + target filename per entry) and download in parallel.
python3 - <<'PY'
import json
d = json.load(open("files.json"))
lines = []
for url, path in zip(d["urls"], d["filepath"]):
    lines += [url.strip(), "  dir=/data/fast-db", f"  out={path}"]
open("aria.in", "w").write("\n".join(lines) + "\n")
PY
aria2c -i aria.in \
  --max-concurrent-downloads=4 --max-connection-per-server=16 --split=16 \
  --min-split-size=1M --continue=true --file-allocation=none

# 3) Start the NIM against the downloaded directory. NIM_MODEL_NAME makes the NIM discover
#    databases by scanning for **/*.idx, bypassing the profile/blob cache entirely.
docker run -d --name msa-search --runtime=nvidia --gpus all \
  -e NGC_API_KEY \
  -e NIM_MODEL_NAME=/databases \
  -v /data/fast-db:/databases \
  -p 8000:8000 \
  nvcr.io/nim/colabfold/msa-search:2

For all databases (equivalent to databases:all), repeat step 1 for each individual DB version and download them into sibling directories under one parent, then point NIM_MODEL_NAME at that parent — the NIM discovers every DB by scanning **/*.idx:

bash
# fetch each DB's file list into /data/all-db/<db>/ ... then one aria2c per list, e.g.:
for V in uniref30_2302-m18v1 colabfold_envdb_202108-m18v1 pdb70_220313-m18v1 \
         pdb100_230517-m18v1 pdb_20251028_zip-m18v1; do
  curl -s -H "Authorization: Bearer $NGC_API_KEY" \
    "https://api.ngc.nvidia.com/v2/org/nim/team/colabfold/models/msa-search/$V/files" \
    -o "files_$V.json"
  # build an aria2 input from files_$V.json (dir=/data/all-db) and run aria2c on it
done
# then launch once against the parent:
#   docker run -d ... -e NIM_MODEL_NAME=/databases -v /data/all-db:/databases ...

The per-connection CDN throttle is the same for every database, so parallel download helps the full set proportionally — the more you download, the more absolute time it saves.

Notes:

  • The presigned URLs expire (typically within a day) — build the aria2 input and start the download promptly after fetching files.json.
  • Keep the downloaded directory's internal layout intact (e.g. uniref30_2302/…); the filepath values already encode it. The NIM needs the .idx file plus its companion files and the small .UNIREF30_READY / *.tar.gz.unpacked markers.
  • The bottleneck is the CDN's per-connection cap, not local disk or CPU — a fast NVMe volume writes far faster than the network delivers. Raising --split / --max-connection-per-server helps only up to the node's aggregate egress ceiling.
  • Best of all: download the profile once, then persist the cache volume (or this fast-db directory) and mount it on future nodes for a ~20 s warm start with no re-download.

Standard MSA Request

Use exact case-sensitive database names and response keys.

For a hosted standard search, run the bundled client from this skill's directory. It submits the real request, validates both database results, and saves the raw JSON and A3M files. Choose a new output directory for each run:

bash
python scripts/hosted_search.py \
  --sequence SGSMKTAISLPDETFDRVSRRASELGMSRSEFFTKAAQR \
  --output-dir msa-output

The client reads NGC_API_KEY or NVIDIA_API_KEY from the environment. It permits at most two requests, each with a 10-second connection timeout and a 300-second read timeout, with five seconds between attempts. If it exits nonzero, report the service failure and stop. Do not restart it repeatedly, extend timeouts beyond the task budget, or replace the missing response with synthetic alignments.

The underlying request format, also usable with a running local NIM, is:

python
import os
import requests

HOSTED = True
url = (
    "https://health.api.nvidia.com/v1/biology/colabfold/msa-search/predict"
    if HOSTED else "http://localhost:8000/biology/colabfold/msa-search/predict"
)
headers = {"Content-Type": "application/json"}
if HOSTED:
    headers["Authorization"] = f"Bearer {os.getenv('NGC_API_KEY')}"

payload = {
    "sequence": "SGSMKTAISLPDETFDRVSRRASELGMSRSEFFTKAAQR",
    "databases": ["Uniref30_2302", "colabfold_envdb_202108"],
    "e_value": 0.0001,
    "output_alignment_formats": ["a3m"],
}
response = requests.post(url, headers=headers, json=payload, timeout=300)
response.raise_for_status()
result = response.json()

Paired MSA Request

Use paired search for protein complexes; payload field is sequences plural, and output is alignments_by_chain.

python
url = (
    "https://health.api.nvidia.com/v1/biology/colabfold/msa-search/paired/predict"
    if HOSTED else "http://localhost:8000/biology/colabfold/msa-search/paired/predict"
)
payload = {
    "sequences": [chain_a_sequence, chain_b_sequence],
    "e_value": 0.0001,
    "output_alignment_formats": ["a3m"],
}

Use local Docker for structural templates. Set max_msa_sequences=500 unless NIM_GLOBAL_MAX_MSA_DEPTH was changed.

python
url = "http://localhost:8000/biology/colabfold/msa-search/structure-templates/predict"
headers = {"Content-Type": "application/json"}
payload = {
    "sequence": "VLSPADKTNVKAAWGKVGAHAGEYGAEALERMFLSFPTTKTYFPHFDLSHGSAQVKGHGKKVADALTNAVA",
    "structural_template_databases": ["pdb70_220313"],
    "max_structures": 20,
    "max_msa_sequences": 500,
}

Save Outputs

python
# Standard MSA: result["alignments"][database][format]["alignment"]
for db_name, formats in result.get("alignments", {}).items():
    for fmt_name, data in formats.items():
        with open(f"msa_{db_name}.{fmt_name}", "w", encoding="utf-8") as handle:
            handle.write(data["alignment"])

# Paired MSA: one alignment set per chain
for chain_id, chain_data in result.get("alignments_by_chain", {}).items():
    for db_name, formats in chain_data.items():
        for fmt_name, data in formats.items():
            with open(f"msa_chain_{chain_id}_{db_name}.{fmt_name}", "w", encoding="utf-8") as handle:
                handle.write(data["alignment"])

# Template search: save mmCIF structures and M8 hit tables
for name, cif in result.get("structures", {}).items():
    open(f"template_{name}.cif", "w", encoding="utf-8").write(cif)
for name, hit_table in result.get("search_hits", {}).items():
    open(f"template_hits_{name}.m8", "w", encoding="utf-8").write(hit_table)

A3M output can feed OpenFold3, AlphaFold2, or RoseTTAFold. For alignment depth, template, and sequence sanity checks, read references/validation.md.

Limits And Troubleshooting

  • Sequence length: 1-4096 amino acids; X works since v2.3.0.
  • max_msa_sequences: 1-500; local GPU server default must match NIM_GLOBAL_MAX_MSA_DEPTH.
  • Paired MSA requires at least two sequences.
  • Local URL 404 usually means an accidental /v1/ prefix.
  • First local run can take hours while databases populate LOCAL_NIM_CACHE.
  • Hosted HTTP 502/503/504 or repeated read timeouts indicate that the hosted request did not complete. Check service availability after the bounded retry; a longer client timeout cannot fix a server-generated HTTP 504.
  • Do not invent a polling URL for health.api.nvidia.com. The published standard MSA example uses synchronous POST; a pending response needs a documented service-specific completion mechanism before it can count as a result.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (scripts, references) in skills/bionemo-msa-search-nim of NVIDIA/skills.

  • SKILL.md
  • BENCHMARK.md
  • config/skillspector-baseline.yml
  • evals/config.yml
  • evals/evals.json
  • evals/trigger_evals.json
  • references/api.md
  • references/examples.md
  • references/parameters.md
  • references/science.md
  • references/validation.md
  • scripts/hosted_search.py
  • skill-card.md
  • skill.oms.sig
  • tests/test_hosted_search.py

Open the folder on GitHubat commit dfdd080

Used in 1 other repository

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.

Compare with similar skills

Msa Search Nim 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 Search Nim compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Msa Search Nim this skillNVIDIA/skills3.5k1 repos~4.6kAutomated safety check: NotesApache-2.0
Setup Workshopbrevdev/workshop-build-an-agent146—~2.3kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Setup Workshop

    brevdev/workshop-build-an-agent

    This skill should be used when the user wants to set up, install, deploy, bootstrap, or "spin up" the Build-an-Agent workshop (a.k.a.

    146 GitHub stars~2.3k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Classical Poem Silk Video

    Mr-funny/hbg-classical-poem-silk-video

    Turn Chinese classical poems and ci into coherent vertical Chinese-art videos with poem-driven scene grouping, GPT ImageGen stills, Docker-only Gemini I2V, retained model-generated ambience, Gemini…

    361 GitHub stars~1.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from NVIDIA/skills

All 386 skills in this repo
  • Official

    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.

    3.5k GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • Official

    Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.

    3.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Official

    Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.

    3.5k GitHub stars~4.8k tokensUpdated today
    Auto-check passed
  • 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.

    3.5k GitHub stars~5k tokensUpdated today
    Auto-check: notes
  • Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.

    3.5k GitHub stars~4.7k tokensUpdated today
    Auto-check: notes
  • Official

    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.

    3.5k GitHub stars~2.7k tokensUpdated today
    Auto-check: notes

Categories

Questions about Msa Search Nim

What does Msa Search Nim do?

Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM. Msa Search Nim is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Generate multiple sequence alignments (MSAs) for protein sequences using the ColabFold MSA-Search NIM.

When should I use Msa Search Nim?

Msa Search Nim fits situations like: uniRef30/ColabFold env searches; FASTA alignments; paired MSA search for complexes; PDB70 structural templates.

How do I install Msa Search Nim in Claude Code?

Run `npx skills add NVIDIA/skills --skill msa-search-nim -a claude-code`. Or copy the skill folder (skills/bionemo-msa-search-nim in NVIDIA/skills) into .claude/skills/msa-search-nim in your project. Claude Code loads it when a task matches its description.

How do I install Msa Search Nim in Codex?

Run `npx skills add NVIDIA/skills --skill msa-search-nim -a codex`. Or copy the skill folder (skills/bionemo-msa-search-nim in NVIDIA/skills) into .agents/skills/msa-search-nim in your project. Codex loads it when a task matches its description.

Can I use Msa Search Nim 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-search-nim -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-search-nim, .gemini/skills/msa-search-nim, .github/skills/msa-search-nim and .opencode/skills/msa-search-nim in your project.

What does Msa Search Nim need to run?

Going by SKILL.md and its folder, Msa Search Nim needs Python for the scripts in its folder, the command-line tools its instructions call (docker, curl, python3, jq and python) and credentials named NGC_API_KEY and NVIDIA_API_KEY. Our summary lists: Python 3; Docker; A credential in NGC_API_KEY; A credential in NVIDIA_API_KEY. Its frontmatter pre-approves these tools: Bash, Read, Write, AskUserQuestion. Compatibility (from SKILL.md): requests>=2.28.

Does Msa Search Nim access the network?

SKILL.md names 2 domains. In commands or code: health.api.nvidia.com and api.ngc.nvidia.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Msa Search Nim safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file; pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Msa Search Nim use?

Msa Search Nim 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 Search Nim use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.

What are the alternatives to Msa Search Nim?

Skills that share tags, products or a category with Msa Search Nim: Setup Workshop (brevdev/workshop-build-an-agent, 146 stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Msa Search Nim?

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.