moveon

Restore and revalidate SLURM job monitors after session reconnect.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/KangOxford/auto-quant-research --skill moveon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moveon
Source: https://github.com/KangOxford/auto-quant-research/tree/main/execution-layer/skills/moveon
Command: npx skills add https://github.com/KangOxford/auto-quant-research --skill moveon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a session is interrupted or reattached, this skill reestablishes and validates active background monitors for SLURM jobs, ensuring no running task is left unmanaged.

Core Features & Use Cases

  • Re-scan and re-launch monitors for active jobs listed in the persistent state file.
  • Distinguish RUNNING, PENDING, and COMPLETED jobs and take appropriate recovery actions.
  • Report completed jobs with final status, logs, and metrics to help auditing and continuity.

Quick Start

Run moveon after reconnect to restore all active monitors.

Frequently Asked Questions about moveon

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

FAQPage Schema
How do I restore SLURM job monitors after a session reconnect?

To restore SLURM job monitors after a session reconnect, run the moveon command to re-scan the persistent state file and re-launch background monitors for active jobs.

Why are my background SLURM jobs left untracked when I reattach a CLAUDE session?

Background SLURM jobs are left untracked because session interruptions terminate active monitors. This skill reestablishes and validates these monitors using a persistent state file.

How does this skill handle pending or completed SLURM jobs during recovery?

During recovery, the skill distinguishes RUNNING, PENDING, and COMPLETED SLURM jobs, taking appropriate recovery actions like re-launching monitors or reporting final status and metrics.

Do I need a specific state file to track active HPC tasks?

Yes, you need a persistent state file at .claude/active_monitors.jsonl to track active HPC tasks and successfully restore your background SLURM monitors.

Can I clear all active SLURM monitors from the persistent state file?

Yes, you can clear all active SLURM monitors by executing the skill with the optional --clean flag to remove untracked job entries from the state file.

What SLURM commands are used to check running and completed jobs?

The skill executes Bash-based checks using squeue and sacct commands to validate running and completed SLURM jobs and report final results.