foundry

Automate Foundry toolkit extension and de novo design workflows.

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/LiorZ/protein-design-skills --skill foundry-liorz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry
Source: https://github.com/LiorZ/protein-design-skills/tree/main/skills/foundry
Command: npx skills add https://github.com/LiorZ/protein-design-skills --skill foundry-liorz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundry provides a unified infrastructure to run, extend, and manage three model families (RFD3, RF3, MPNN variants) for de novo design and structure prediction, reducing setup overhead and enabling reproducible experiments.

Core Features & Use Cases

  • Centralized CLI and Python APIs to install/checkpoint data, run inference, and hook new MPNN architectures.
  • Extension pathways to register new checkpoints and integrate custom inference engines, enabling teams to plug in proprietary models or new architectures.
  • Use Case: A team wants to add a new enhanced MPNN checkpoint and wire it into existing Foundry workflows without modifying tooling.

Quick Start

Install a checkpoint and run a quick design through the rfd3, rf3, and mpnn workflows.

Frequently Asked Questions about foundry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register new MPNN checkpoints in a de novo design workflow?

You register new MPNN checkpoints in a de novo design workflow by using a registry-based discovery system that enforces metadata-driven extension points, allowing teams to plug in new architectures without modifying existing tooling. This ensures scalable collaboration and reproducible experiments.

Can I run RFD3 and RF3 inference campaigns from a centralized Python API?

Yes, you can run RFD3 and RF3 inference campaigns from a centralized Python API. Foundry provides unified CLI and Python interfaces to install checkpoint data, run structure prediction, and manage end-to-end design workflows across multiple model families.

What is Hydra config wiring and how does it work with custom inference engines?

Hydra config wiring is a configuration management mechanism that connects custom inference engines to Foundry workflows. It enforces metadata-driven extension points, enabling researchers to integrate proprietary models into RFD3, RF3, and MPNN variants for scalable collaboration.

Does Foundry support integrating custom inference engines for structure prediction?

Yes, Foundry supports integrating custom inference engines for structure prediction. It provides dedicated extension pathways that allow teams to wire in proprietary models or new architectures, reducing setup overhead while maintaining reproducible experiment infrastructure.

What's the best way to manage checkpoints across RFD3, RF3, and MPNN variants?

The best way to manage checkpoints across RFD3, RF3, and MPNN variants is through a centralized registry-based discovery system. Foundry enforces metadata-driven checkpoint registration, enabling reproducible experiments and scalable collaboration across all three model families.