Menu

Individual skill

setup-proteinmpnn-remote-tool

0upvotes

Set up, launch, validate, and troubleshoot the ProteinMPNN / SolubleMPNN fixed-backbone sequence-design ToolUniverse remote tool and optionally relay it through ToolUniverse Connect. Use when deploying or auditing this implementation.

skills/setup-proteinmpnn-remote-tool/SKILL.md

Read pinned source

Source commit 5598a9fc97e32964fe9b703818e7d0747142f179

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,780
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Set up ProteinMPNN sequence design as a remote tool

> Validation status (2026-10-14): ProteinMPNN sequence design ran on the NVIDIA
> GB10 host (aarch64, 20 cores, 121.6 GiB unified memory, cc 12.1, driver
> 580.173.02) **on the CPU**, holding stock ProteinMPNN at commit `8907e667`.
> **`[gpu] policy = "none"` and `vram_budget_gb` is absent, which is the point of
> this provider:** `remote_resident/admission.py` skips a provider with no
> declared budget, so this one is admitted while the card is full and can be
> resident alongside every folding model on the box. Its central claim is
> equivalence, not speed: the worker holds stock's own loop and the acceptance
> suite byte-compares its reply against `run.sh design --mode off` across five
> cases — two backbones, two seeds, two temperatures, two batch layouts and both
> weight sets — comparing every field stock writes, which came out **identical**.
> The optimization kit's `exact` line also runs on this CPU host and is also
Back to top