vimalinx/bio-agent / .claude/skills/rfdiffusion
rfdiffusion
VerifiedUse when working from the local RFdiffusion repository to generate protein backbones or binder designs through its Docker Compose workflows.
rfdiffusion
Workspace-local gateway for /home/vimalinx/Projects/bio_studio/repositories/active/RFdiffusion. The repo contains a Chinese quickstart, test_rfdiffusion.sh, design_ebola_binder.sh, a populated models/ directory, and Docker/Compose entrypoints for inference.
Quick Start
- Repository:
/home/vimalinx/Projects/bio_studio/repositories/active/RFdiffusion - Primary smoke test:
./test_rfdiffusion.sh - Primary build step:
docker compose build
When To Use This Tool
- Running RFdiffusion locally from the checked-out workspace repo
- Generating monomer or binder backbones with the repo's inference script
- Reusing the bundled
models/directory and test harness - Exploring the repo's Ebola binder design example
Common Patterns
# Build the RFdiffusion container stack
cd /home/vimalinx/Projects/bio_studio/repositories/active/RFdiffusion
docker compose build
# Run the repo's built-in smoke test
cd /home/vimalinx/Projects/bio_studio/repositories/active/RFdiffusion
./test_rfdiffusion.sh
# Run direct inference through the repo's compose service
docker compose run --rm --entrypoint /bin/bash rfdiffusion -c \
"python3 scripts/run_inference.py 'contigmap.contigs=[150-150]' inference.output_prefix=outputs/test_run/test inference.num_designs=1 inference.model_directory_path=/app/RFdiffusion/models inference.input_pdb=/app/RFdiffusion/examples/input_pdbs/1qys.pdb"
Recommended Workflow
- Work from the local RFdiffusion repo rather than stale absolute paths copied from older notes.
- Build the Docker/Compose environment first.
- Run
./test_rfdiffusion.shbefore attempting custom binder or motif jobs. - Only move on to custom scripts like
design_ebola_binder.shafter the compose test succeeds.
Guardrails
- Docker images are not prebuilt in this workspace.
docker image inspect rfdiffusionfailed withNo such image: rfdiffusion:latest. - The quickstart document still references
/media/vimalinx/Data/bio_studio/RFdiffusion; the actual workspace repo is under/home/vimalinx/Projects/bio_studio/repositories/active/RFdiffusion. - The quickstart notes GPU memory around
8GB+for binder design. test_rfdiffusion.shdepends on Docker Compose and the repo'smodels/directory layout.- RFdiffusion is a generative structure-design tool, not a drop-in sequence-to-structure predictor.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |