jobs

A simple and elegant solution for managing your to-do lists.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kang-jaehyun/Mac-the-researcher --skill jobs-kang-jaehyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jobs
Source: https://github.com/kang-jaehyun/Mac-the-researcher/tree/main/.claude/skills/jobs
Command: npx skills add https://github.com/kang-jaehyun/Mac-the-researcher --skill jobs-kang-jaehyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and viewing SLURM job statuses across multiple clusters can be time-consuming and fragmented. This Skill provides a unified view of running, pending, and recent jobs to accelerate cluster monitoring and troubleshooting.

Core Features & Use Cases

  • Multi-cluster monitoring: aggregate and group jobs by cluster.
  • Status breakdown: clearly show Running, Pending, and Recent (completed/failed) jobs with key details.
  • Smart hints: highlight delays or anomalies and cross-reference with local experiments when available.

Quick Start

Run the check_queue tool to fetch current jobs across all clusters, then use recent_jobs to review the last 3 days of activity and present a clean, grouped summary.

Frequently Asked Questions about jobs

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

FAQPage Schema
How do I check SLURM job status across multiple clusters at once?

To check SLURM job status across multiple clusters, this Skill uses the check_queue MCP tool to fetch and aggregate current running, pending, and recent jobs into a unified, grouped summary for easy monitoring.

What is the best way to view recent SLURM jobs and queue delays?

Viewing recent SLURM jobs and queue delays is done by running the recent_jobs MCP tool to review the last 3 days of activity, highlighting anomalies and presenting a clean, per-cluster breakdown of completed and failed jobs.

Can I diagnose SLURM pending jobs and queue anomalies across different clusters?

Yes, you can diagnose SLURM pending jobs and queue anomalies across different clusters by fetching current statuses and cross-referencing them with local experiments, utilizing smart hints to highlight delays or irregularities in the queue.

Does this multi-cluster SLURM monitoring approach require any specific dependencies?

This multi-cluster SLURM monitoring approach requires no external dependencies, relying solely on configured MCP tools like check_queue and recent_jobs to gather and format per-cluster summaries of running, pending, and recent jobs.

Why are my SLURM jobs stuck pending and how can I monitor them?

SLURM jobs stuck pending can be monitored by fetching a unified view of all clusters to identify queue delays, with smart hints highlighting anomalies and grouping statuses to accelerate troubleshooting and diagnosis.