skills/modal-compute/SKILL.md
Run explicitly chosen research benchmark or replication jobs on Modal's serverless infrastructure. Use when a Feynman research workflow needs burst remote GPU compute and the Modal CLI is available.
npx skillsauth add getcompanion-ai/feynman modal-computeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use the modal CLI for bounded research experiments that need burst GPU compute. No pod lifecycle to manage; write a decorated Python script, run it, and save raw outputs back into the research artifact folder. Do not use this skill to deploy services or unrelated batch jobs.
pip install modal
modal setup
| Command | Description |
|---------|-------------|
| modal run script.py | Run one research experiment script on Modal |
| modal run --detach script.py | Run a long research experiment and record the returned app/run identifier |
| modal shell --gpu a100 | Open an interactive GPU shell for research environment debugging |
T4, L4, A10G, L40S, A100, A100-80GB, H100, H200, B200
Multi-GPU: "H100:4" for 4x H100s.
import modal
app = modal.App("experiment")
image = modal.Image.debian_slim(python_version="3.11").pip_install("torch==2.8.0")
@app.function(gpu="A100", image=image, timeout=600)
def train():
import torch
# training code here
@app.local_entrypoint()
def main():
train.remote()
command -v modaldevelopment
Call a configured Feynman model endpoint and interpret its response. Use when a task needs inference from a registered endpoint, remote model API, local model service, or custom connector-backed predictor.
data-ai
Design or screen protein sequences for solubility-aware constraints with SolubleMPNN-style workflows. Use when a task asks for soluble protein design, expression-friendly variants, or solubility risk filtering.
data-ai
Create or revise Feynman skills. Use when a research workflow needs a reusable on-demand capability, skill metadata, trigger wording, references, scripts, or skill validation.
tools
Inspect the active Feynman workbench session, artifacts, execution log, settings, and provenance. Use when the task asks what happened in this session, which files were written, what tools ran, or what remains unverified.