experiment-monitor

Inspect background experiment job status and collect completion signals without altering research state.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-monitor-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: experiment-monitor
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/experiment-monitor
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill experiment-monitor-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running screening and confirmation experiments run as background jobs, and checking them manually risks corrupting the research pipeline by acting on partial logs or misreading process handles. This Skill provides a safe, read-only way to check job status and detect completion without changing any scientific state. ## Core Features & Use Cases - Status Inspection: Resolves the registered DSH background job id and reports whether the job is running, completed, failed, or missing, along with the last meaningful metric or error. - State Safety Guarantees: Never creates goal rounds, increments attempts, rejects candidates, changes phases, or triggers reviewers based on partial logs. - Completion Handoff: When a job finishes, passes raw artifact paths to experiment-run for metric collection and routing; on infrastructure failure, preserves the candidate and plan while the launch issue is fixed. - Use Case: A screening job wakes your session via a job event. Use this Skill to confirm it completed, retrieve the artifact paths, and hand them off for metric collection instead of polling logs and guessing at results. ## Quick Start Check the status of the currently registered background experiment job and tell me whether it completed, failed, or is still running.

Frequently Asked Questions about experiment-monitor

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

FAQPage Schema
How do I check the status of a running background experiment job?▼

Resolve the DSH background job id recorded by experiment-bridge and inspect the job with its latest logs. The status is reported as running, completed, failed, or missing, along with the last meaningful metric or error.

How to monitor long-running experiments without polling?▼

Wait for job events to wake the session or use bounded status checks instead of busy-polling. Event-driven monitoring avoids wasting cycles while still catching completion or failure signals promptly.

Can monitoring a job change the research pipeline state?▼

No. Monitoring is strictly read-only: it never creates goal rounds, increments attempts, rejects candidates, changes phases, or calls reviewers based on partial logs. Scientific state only advances through the dedicated pipeline skills.

What happens when a monitored experiment job completes?▼

On completion, the raw artifact paths are handed to experiment-run for metric collection and routing. The monitor itself does not parse metrics or make promotion decisions.

What should I do when an experiment job fails due to infrastructure errors?▼

If infrastructure fails before a scientific result exists, preserve the same candidate and plan while fixing the launch issue. The failure is treated as an operational problem, not a negative experimental result.