monitor
Skill25 starsChanged 2 months agoMITView on GitHub
Use when checking a running experiment, diagnosing a stalled job, or reviewing failures in an `expNNx` run. Triggers on "check status", "看看实验", "how's the run", "any failures", "is it done", "monitor experiment", "experiment status".
30 other projects use a version of this.
Adopted by
Most recently taken up by
- Mahiler1909/burnlogtheir own version, first seen Nov 8, 2026
- cihantopac/searvextheir own version, first seen Nov 8, 2026
- gspencergoog/skillstheir own version, first seen Nov 1, 2026
- neurospin-projects/2026_bdrabczuk_champollion_mcptheir own version, first seen Nov 1, 2026
- GuanceCloud/ai-skillstheir own version, first seen Oct 25, 2026
- osteel/agent-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use spec, debug and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 3 projects that use this
AnthropicSkilldebug
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- NVIDIA/TensorRT-Model-Optimizer★ 5.6ksame name
- NVIDIA/Model-Optimizer★ 5.6ksame name
- H-mmer/pentest-agents★ 815same name
- elitan/frost★ 324same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- block/builderbot★ 108same name
- no-session/pstack★ 96same name
- joelhooks/joelclaw★ 65same name
- rainday/smart-blog-skills★ 35same name
- spotify/ads-agentic-tools★ 20same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-skillSkill
- project-skillSkill
- analyze-experimentSkill
- commit-changelogSkill
- init-projectSkill
- new-experimentSkill
- read-paperSkill
- survey-literatureSkill
- todoSkill
- update-docsSkill
- update-knowhowSkill
- update-project-skillSkill
- visualizeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run scripts/monitor_exp.sh <exp_id> when available and inspect the relevant log tail and process state.
- Very specific: line 15
Follow ../../references/agent-routing.md for the exp-manager role when diagnosis is needed.
- Distinctive: line 19
Do not kill, retry, or relaunch work without clear authorization and an exact target.
“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Monitor
Perform one status cycle per invocation. Recurrence belongs to the host's scheduler.
- Resolve the experiment from the argument or
.pipeline-state.json. - Run
scripts/monitor_exp.sh <exp_id>when available and inspect the relevant log tail and process state. - Follow
../../references/agent-routing.mdfor theexp-managerrole when diagnosis is needed. - Report status, evidence, uncertainty, and the next safe action.
Do not kill, retry, or relaunch work without clear authorization and an exact target. For repeated checks, offer the current host's native scheduler when it has one; otherwise suggest another invocation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.