Skip to content
Back to skills

Installation Assets

ASecurity

"Plan and troubleshoot OpenFold installation, package builds,

  • 247 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
toolspythondockerapidatabasebackend

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 8, 2026

npx -y skills add VectorSpaceLab/AREX-Skill --skill installation-assets --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Installation Assets?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Installation Assets
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-installation-assets/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-installation-assets)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: installation-assets
description: "Plan and troubleshoot OpenFold installation, package builds,
  runtime dependencies, parameters, databases, Docker prerequisites, and safe
  environment validation."
disable-model-invocation: true
metadata:
  disco-role: operating
license: Apache 2.0
---

# OpenFold Installation and Runtime Assets

Use this sub-skill when a user needs to set up OpenFold, diagnose installation or import failures, plan model parameters/databases, check CUDA/PyTorch/OpenMM/TensorRT/DeepSpeed/cuEquivariance readiness, or validate an environment before inference or training.

## Start Here

1. Read `references/environment-and-assets.md` for supported runtime assumptions, package build behavior, dependency families, Docker notes, and asset requirements by workflow.
2. Run `python scripts/check_openfold_environment.py --json` inside the target environment to report imports, optional backends, extension availability, CUDA state, and external binaries without running downloads, inference, training, or builds.
3. Run `python scripts/plan_asset_downloads.py --workflow monomer`, `--workflow multimer`, `--workflow soloseq`, or `--workflow training` to produce a dry-run parameter/database plan. The planner never downloads or creates files.
4. Use `references/troubleshooting.md` to map symptoms such as missing `torch` during build isolation, missing `attn_core_inplace_cuda`, CUDA library failures, absent optional dependencies, missing HMMER/HHSuite/Kalign binaries, or absent parameters/databases to recovery actions.

## Boundaries

- For inference command construction, route to `../inference/` after environment and assets are selected.
- For alignment, mmCIF, cache, and training data layouts, route to `../data-preparation/`.
- For training or fine-tuning command execution, route to `../training/`.
- For model internals, TensorRT/DeepSpeed/cuEquivariance APIs, kernel behavior, and weight import details, route to `../model-apis/`.

## Safety Notes

The bundled scripts are validation and planning helpers only. They do not download assets, create conda environments, build extensions, run unit tests, run inference, run training, mutate repositories, or require a source checkout. CLI `--help` probing is opt-in and only inspects user-supplied script paths.

Files in this skill

  • SKILL.md2.2 KB
  • references/environment-and-assets.md11.2 KB
  • references/troubleshooting.md12 KB
  • scripts/check_openfold_environment.py12.7 KB
  • scripts/plan_asset_downloads.py21 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.