complexa-setup SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
complexa-setup from nvidia-bionemo/bionemo-agent-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nvidia-bionemo/bionemo-agent-toolkit/complexa-setup@git:20261016.a6eced5Pins git:20261016.a6eced5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nvidia-bionemo/bionemo-agent-toolkit
- Path
skills/bionemo-agent-toolkit/skills/complexa-setup/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261016.a6eced5, committed Oct 16, 2026
- First version recorded
- Aug 25, 2026
- Size
- 13,989 bytes
- Repository stars
- 503
- License
- a license file GitHub does not identify
First-time setup, environment configuration, and model-weight installation for Proteina-Complexa. Reach for this skill whenever the user says "set up complexa", "install complexa", "configure my .env", "first-time setup", "what models do I have installed", "what's in my .env", "download model weights", "download Complexa / AF2 / RF3 / ProteinMPNN / LigandMPNN / ESM2 / ESMFold checkpoints", "preflight my GPU", "verify environment", "complexa init", "complexa download…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Complexa Setup Skill Drive the three steps a fresh Proteina-Complexa checkout needs before any design run: create `.env`, fetch model weights, and sanity-check the env. Probe the host for GPU / disk / tool binaries first so the user does not discover a missing dependency mid-pipeline. End with a JSON setup artifact the user (or a future agent) can re-read instead of re-deriving state. ## CLI vs direct file-edit — pick the cheapest path per step | Step | Preferred path | Why | |---|---|---| | `.env` creation (Step 2) | **File edit** (`cp .env_example .env` + 3 line swaps) or `complexa init` | `complexa init` is a thin wrapper around `cp + 3 regex swaps` (`_swap_runtime_in_env` in `cli_runner.py`). Either path works; pick CLI for new humans, direct edit for agents. | | `.env` value edits (Step 3) | **File edit** (StrReplace `LOCAL_CODE_PATH=…` etc.) | No CLI for this — the values are user-specific paths. | | Download model weights (Step 4) | **CLI** (`complexa download --…`) | Dispatches to `env/download_startup.sh` (~1000 lines of bash with NGC URLs, retries, checksum-style skip-if-present). Don't try to replicate. | …
Read the whole file at its exact version.
How to install
mdr add nvidia-bionemo/bionemo-agent-toolkit/complexa-setup@sha256:aeb450ce7472384fThe line at the top of this page pins the label git:20261016.a6eced5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_sezsrprqle2h4qvp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 25, 2026 and Oct 16, 2026, about one every 52 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.a6eced5 latest | 2026-10-16 | a6eced5 | 13,989 B | A | view · diff |
| git:20260825.0e67a61 | 2026-08-25 | 0e67a61 | 14,015 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13989 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nvidia-bionemo/bionemo-agent-toolkit · 503 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_sezsrprqle2h4qvp GET https://markdownregistry.com/api/v1/resolve?ref=nvidia-bionemo/bionemo-agent-toolkit/complexa-setup GET https://markdownregistry.com/api/v1/blob/aeb450ce7472384f3f1d5396af68de1ecb2fe92457cb87046dfbf5ac08d18c46
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from nvidia-bionemo/bionemo-agent-toolkit
Every file in nvidia-bionemo/bionemo-agent-toolkit