sync

Syncs tracked ML experiments with actual SLURM job states and metrics from logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize local experiment tracking with actual SLURM job states to ensure dashboards and records reflect real progress.

Core Features & Use Cases

  • Load tracked experiments using MCP and filter for non-terminal states.
  • For each active experiment, query SLURM with job_info, map states (PENDING to queued, RUNNING to running, COMPLETED to completed, FAILED to failed, CANCELLED to cancelled, TIMEOUT to failed), and collect any relevant runtime data.
  • For completed experiments, tail logs to extract metrics like best_metric and val_loss, and update local records accordingly.
  • For failed experiments, capture error messages from logs and append them to notes for troubleshooting.
  • Update local records for any state changes and generate a concise summary.

Quick Start

Run the sync to refresh active experiments against SLURM and update local tracking.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I sync local experiment tracking with actual SLURM job states?▼

To sync local experiment tracking with SLURM job states, this Skill queries SLURM job_info, maps states like PENDING to queued and RUNNING to running, and updates local records to reflect real progress across multi-cluster setups.

Can I extract metrics like best_metric and val_loss from SLURM logs automatically?▼

Yes, you can extract metrics automatically. For completed SLURM experiments, the Skill tails logs to parse values like best_metric and val_loss, then updates local tracking records with the extracted results.

How do I track failed SLURM jobs and capture their error messages?▼

To track failed SLURM jobs, the Skill maps FAILED, CANCELLED, and TIMEOUT states to a failed status, captures error messages from logs, and appends them to local records for troubleshooting.

What is the best way to monitor queued and running experiments across multiple SLURM clusters?▼

The best way to monitor active experiments across multi-cluster SLURM setups is to filter local records for non-terminal states, query SLURM for job_info, parse the runtime states, and generate a concise summary of all progress.

Does this SLURM synchronization method work without any external dependencies?▼

Yes, this SLURM synchronization method works without external dependencies. It loads tracked experiments using MCP, queries SLURM directly for job_info, parses the states, and updates local records independently.

Why does my local dashboard show outdated experiment progress from SLURM?▼

Your local dashboard shows outdated progress because local records are not synchronized with actual SLURM job states. Running a sync refreshes active experiments against SLURM to ensure dashboards reflect real-time progress.