slurm

Submit, monitor, and cancel SLURM jobs on remote Linux clusters.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill slurm-14790897
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slurm
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/slurm
Command: npx skills add https://github.com/14790897/MiQi --skill slurm-14790897

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the friction of managing high-performance computing jobs by providing a unified interface for submitting, monitoring, and controlling tasks on a SLURM cluster.

Core Features & Use Cases

  • Job Lifecycle Management: Easily submit batch jobs, monitor queue status, and cancel pending or running tasks.
  • Cluster Interaction: Provides standardized commands for checking partition status and inspecting detailed job metrics.
  • Use Case: A researcher can use this skill to submit a complex simulation script to the cluster and monitor its progress in real-time without manually logging into the control node.

Quick Start

Use the slurm skill to submit the job script named simulation.sh to the cluster and then check the status of your current jobs.

Frequently Asked Questions about slurm

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

FAQPage Schema
How do I submit and monitor a SLURM job on a remote Linux cluster?

To manage SLURM jobs on a remote Linux cluster, you can submit batch scripts, monitor queue status, and cancel tasks using standardized interactions with sbatch, squeue, and scancel utilities. This requires SSH access to the cluster control node with appropriate user permissions for execution.

What is the best way to automate high-performance computing job lifecycles?

Automating high-performance computing job lifecycles involves streamlining the submission, monitoring, and cancellation of compute tasks. A unified interface removes friction by providing standardized commands for interacting with SLURM utilities, ensuring efficient management of complex simulation scripts without manual logins.

Do I need SSH access to manage SLURM batch jobs?

Yes, managing SLURM batch jobs requires SSH access to the cluster control node and appropriate user permissions for job execution. This connection facilitates interaction with sbatch, squeue, and scancel utilities to handle the compute job lifecycle on remote Linux clusters.

Can I cancel pending or running SLURM tasks without manually logging into the control node?

Yes, you can cancel pending or running SLURM tasks without manually logging into the control node by using a unified interface that interacts with the scancel utility. This streamlines cluster interaction and simplifies the control of high-performance computing job lifecycles.