overview

Define a mental model for Yale SOM HPC cluster login and compute nodes.

5|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/yale-som-hpc/claude-code-marketplace --skill overview-yale-som-hpc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overview
Source: https://github.com/yale-som-hpc/claude-code-marketplace/tree/main/plugins/hpc/skills/overview
Command: npx skills add https://github.com/yale-som-hpc/claude-code-marketplace --skill overview-yale-som-hpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mental model and safety guidance for using the Yale SOM HPC cluster, helping users distinguish login vs compute nodes, partitions, GPFS, Slurm, and default safety rules.

Core Features & Use Cases

  • Mental model for cluster navigation including login nodes for editing and compute nodes for analysis, plus guidance on partitions, GPFS, and modules.
  • Clear decision guidance on where tasks belong (login vs compute), when to use each resource, and how to plan workflows that respect shared resources.
  • Use Case: When starting work on a project, or deciding how to submit a job, this skill helps you align actions with cluster rules and best practices.

Quick Start

Ask Claude Code to provide the Yale SOM HPC cluster orientation and safety guidance before starting any cluster tasks.

Frequently Asked Questions about overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate the Yale SOM HPC cluster without violating safety rules?

The Yale SOM HPC cluster separates login nodes for editing and compute nodes for analysis. Apply this mental model to decide where tasks belong, plan workflows across partitions, and manage GPFS scratch space while respecting Slurm resource limits.

What is the difference between login nodes and compute nodes on an HPC cluster?

Login nodes handle editing and light tasks, while compute nodes run heavy analysis. Using login nodes for intensive compute violates safety rules, so submit resource-heavy jobs to compute nodes via Slurm to protect shared cluster resources.

How do I plan Slurm workflows across partitions and GPFS storage?

Plan Slurm workflows by matching job requirements to partitions and staging data on GPFS. Align actions with cluster rules by submitting compute jobs via Slurm, managing scratch space, and keeping login nodes clear of heavy processing.

Can I run heavy compute tasks directly on HPC login nodes?

No, running heavy compute on login nodes violates cluster safety rules. Login nodes are for editing and light tasks. Submit intensive jobs to compute nodes through Slurm to maintain cluster stability for all users.

When do I need cluster orientation guidance before submitting a job?

You need cluster orientation guidance when starting a project or deciding how to submit a job. It helps align your actions with cluster rules, clarifying node selection, partition usage, and GPFS scratch space management.