Skip to content
Back to skills

Distributed And Backends

ASecurity

"Choose and troubleshoot DALLE-pytorch CUDA, DeepSpeed, Horovod,

  • 247 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 8, 2026
developmentdockerbackend

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 distributed-and-backends --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Distributed And Backends?

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

Security grade badge for Distributed And Backends
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vectorspacelab-distributed-and-backends/badge)](https://www.skillsdirectory.com/skills/vectorspacelab-distributed-and-backends)

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: distributed-and-backends
description: "Choose and troubleshoot DALLE-pytorch CUDA, DeepSpeed, Horovod,
  Apex, Docker, sparse attention, and distributed checkpoint paths."
metadata:
  disco-role: operating
disable-model-invocation: true
license: MIT
---

# Distributed and backend workflows

Use this sub-skill for CUDA readiness, DeepSpeed, Horovod, Apex AMP, Docker GPU images, sparse attention, distributed parser flags, and checkpoint behavior.

## Read first

- `references/distributed-backends.md` for backend flags, module availability, sparse attention, precision, and checkpoint notes.
- `references/docker-and-system-setup.md` for Docker/source-build caveats.
- `references/troubleshooting.md` for backend import, CUDA, Apex, Horovod, and DeepSpeed failures.
- `scripts/check_backend_availability.py` to inspect safe backend availability without launching training.

## Typical routes

| Request | Action |
| --- | --- |
| "Can I use DeepSpeed?" | Run/describe backend availability check, confirm `deepspeed` import, decide whether sparse attention or only distributed training is needed. |
| "What does `--deepspeed` do?" | Explain parser wrapping and that `args.deepspeed` maps to the `DeepSpeed` backend when available. |
| "Use Horovod" | Confirm `horovod.torch` import and use `horovodrun`-style launch; batch size semantics differ from DeepSpeed. |
| "Install Apex or sparse attention" | Treat as CUDA/source-build task requiring explicit approval; do not run bundled source install scripts blindly. |
| "Choose `attn_types`" | Use package attention options; only `sparse` needs DeepSpeed sparse attention, while `full`, `axial_row`, `axial_col`, and `conv_like` are package-level options. |

## Boundary notes

- Single-process VAE training belongs to `../vae-training/SKILL.md`.
- Single-process DALL-E training/data/tokenizer issues belong to `../dalle-training/SKILL.md`.
- Generation belongs to `../generation-and-ranking/SKILL.md`.

## Safety rules

- Do not run source builds, `sudo apt-get`, Docker builds, or distributed launchers without explicit approval.
- A CUDA allocation smoke is not proof that full training works; it only proves torch can see a device.
- Keep DeepSpeed/Apex/Horovod optional unless the user's selected workflow requires them.

Files in this skill

  • SKILL.md2.2 KB
  • references/distributed-backends.md3.2 KB
  • references/docker-and-system-setup.md1.6 KB
  • references/troubleshooting.md1.8 KB
  • scripts/check_backend_availability.py2.1 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.