/exp-status

Check local screen sessions and remote endpoints for experiment status anomalies.

1.6k|208|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/skyllwt/AutoSci --skill exp-status-skyllwt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /exp-status
Source: https://github.com/skyllwt/AutoSci/tree/main/.claude/skills/exp-status
Command: npx skills add https://github.com/skyllwt/AutoSci --skill exp-status-skyllwt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It helps you track which training experiments are still running, which have anomalies, and which are ready to be collected, so your research pipeline does not stall.

Core Features & Use Cases

  • Unified experiment status monitoring: Scans running experiments and checks local screen sessions or remote jobs to report alive, anomaly, and completion states.
  • Optional auto-collection: When sessions are finished but not yet collected, it triggers /exp-run <slug> --collect to update wiki experiment pages.
  • Pipeline auto-advance: For a specified pipeline, it can automatically trigger /research --start-from stage4 once all experiments are completed.

Quick Start

Run /exp-status --pipeline <pipeline-slug> to see progress for that pipeline and identify which experiments need collection or attention.

Frequently Asked Questions about /exp-status

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

FAQPage Schema
How do I monitor running training experiments in a research pipeline?

To monitor running training experiments, you can check local screen sessions or remote experiment endpoints to report alive, anomaly, and completion states. This prevents your research pipeline from stalling by identifying which runs need collection or attention.

How do I detect anomalies in ongoing training runs?

Anomaly detection for ongoing training runs is handled by scanning active experiments and checking their local or remote status commands to summarize anomalies. It flags sessions that exhibit irregular states alongside those that are alive or ready for collection.

How do I auto-collect finished screen sessions and update wiki experiment pages?

Auto-collecting finished screen sessions triggers a collection command like `/exp-run <slug> --collect` to update wiki experiment pages. This automates the gathering of completed training runs and conditionally updates wiki outputs for finished but uncollected sessions.

Do I need remote job access to check experiment status?

You do not strictly need remote job access; the status check supports both local screen sessions and remote experiment endpoints. You can monitor ongoing and completed training runs by reading wiki experiment pages and running status commands in either environment.

What is the best way to track experiment completion readiness across multiple sessions?

The best way to track completion readiness is unified experiment status monitoring, which scans running sessions and reports alive, anomaly, and completion states. This summarizes which experiments are ready to be collected to prevent pipeline bottlenecks.