complexa-setup
Installation
SKILL.md
Complexa Setup Skill
Drive the three steps a fresh Proteina-Complexa checkout needs before any
design run: create .env, fetch model weights, and sanity-check the env.
Probe the host for GPU / disk / tool binaries first so the user does not
discover a missing dependency mid-pipeline. End with a JSON setup artifact the
user (or a future agent) can re-read instead of re-deriving state.
CLI vs direct file-edit — pick the cheapest path per step
| Step | Preferred path | Why |
|---|---|---|
.env creation (Step 2) |
File edit (copying the env template + 3 line swaps) or complexa init |
complexa init is a thin wrapper around cp + 3 regex swaps (_swap_runtime_in_env in cli_runner.py). Either path works; pick CLI for new humans, direct edit for agents. |
.env value edits (Step 3) |
File edit (StrReplace LOCAL_CODE_PATH=… etc.) |
No CLI for this — the values are user-specific paths. |
| Download model weights (Step 4) | CLI (complexa download --…) |
Dispatches to env/download_startup.sh (~1000 lines of bash with NGC URLs, retries, checksum-style skip-if-present). Don't try to replicate. |
| Validate env (Step 5) | CLI (complexa validate env) or test -f .env && test -d $DATA_PATH |
CLI prints a nicer report; the manual check is one-liner-safe. |
| Validate full design config (after picking a pipeline) | CLI (complexa validate design CONFIG) |
Non-trivial Hydra defaults traversal + ckpt + env-var checks; not worth replicating. |