alliance-canlisted
Work with Digital Research Alliance of Canada (alliancecan.ca) HPC and cloud resources — Fir, Nibi, Rorqual, Narval, Trillium, Killarney, Vulcan, tamIA, Arbutus. Use when the user wants a GPU, an interactive session, an allocation, a compute node, or an instance; wants to write, submit, monitor, right-size, or debug a Slurm job (sbatch/salloc/srun/squeue/sacct/seff); mentions SSH into a cluster, Duo/MFA login prompts, module load, a Python virtualenv or wheel on the cluster, PyTorch/TensorFlow/HuggingFace on a cluster; asks about home/scratch/project/nearline quotas, diskusage_report, scratch purging, rsync or Globus transfers; mentions MIG, H100, A100, L40S, H200, MI300A, RGU, def-/rrg-/rpp-/aip- accounts, CCDB, RAS/RAC allocations, JupyterHub, Open OnDemand, Metrix portal, or OpenStack/Arbutus cloud. Also use for "I have Alliance/Compute Canada access", "run this on the cluster", "why is my job pending", "my job was OOM-killed", "how many GPUs should I ask for".
pouriamrt/alliance-can-skills · ★ 0 · AI & Automation · score 67
Install: claude install-skill pouriamrt/alliance-can-skills
# Alliance Canada (alliancecan.ca)
Drive Alliance HPC clusters from this machine over one MFA-authenticated SSH
session. Write correct Slurm scripts, submit them, watch them, and right-size
them from real efficiency data.
## Non-negotiables
These come from Alliance policy, not preference. Do not work around them.
1. **Never use the automation/robot nodes.** `robot.*.alliancecan.ca` exists for
deterministic pipelines. The wiki states plainly: *"The automation nodes are
designed for predictable workloads. They are not suitable for usage of AI
agents."* Use the normal login node with a human-authenticated session.
2. **Never bypass, disable, or automate around Duo MFA.** An SSH key is not a
substitute for the second factor. If a connection needs a second factor, the
human provides it. Never ask for, echo, store, or log a passcode.
3. **Never compute on a login node.** Login nodes allow roughly ≤10 CPU-minutes
and ≤4 GB RAM for compiling and small tasks. Everything else goes through Slurm.
4. **Confirm before spending or destroying.** `sbatch`, `scancel`, `rm`, quota-
affecting moves, and cloud instance changes are shown to the user and approved
before they run. Read-only commands (`squeue`, `sacct`, `seff`,
`diskusage_report`, `module spider`, `sinfo`) run freely.
5. **No secrets in prompts, scripts, tickets, or repos** — API keys, passwords,
private keys, MFA codes. Alliance general-purpose systems are not approved for
sensitive data; say so