run-agent-monitor
Run, drive, and smoke-test the monitorcore agent tail + discovery — the read-only per-agent tailer and flat/workflow subagent discovery for Claude Code Task subagents. Use when asked to run, start, monitor, watch, or smoke-test the agent monitor / subagent dashboard, tail a subagent transcript, or verify agent-monitor works.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- run-agent-monitor
- description
- Run, drive, and smoke-test the monitorcore agent tail + discovery — the read-only per-agent tailer and flat/workflow subagent discovery for Claude Code Task subagents. Use when asked to run, start, monitor, watch, or smoke-test the agent monitor / subagent dashboard, tail a subagent transcript, or verify agent-monitor works.
02 资源文件 5
- 许可证LICENSE1.0 KB
- 参考文档NOTICE.md879 B
- 参考文档provenance/original-agents/openai.yaml261 B
- 参考文档provenance/original-SKILL.md11.5 KB
- 脚本references/contracts.ts633 B
03 SKILL.md 正文
Run: agent-monitor (monitorcore)
The former standalone agent-monitor tool has been consolidated into the shared
monitorcore package (vendored inside the sibling workflow-monitor skill). This skill is
the read-only driver for its two agent-domain surfaces:
monitorcore.agent_tail— a live, colored tail of one agent's transcript (python -m monitorcore.agent_tail <agent-*.jsonl>), plus the one-shottail_once.pyhere (backfill N events, then exit — headless-safe).monitorcore.discovery— flat + workflow subagent discovery (find_subagent_dirs,scan,pick_active_dir): everyagent-*.jsonlunder~/.claude/projects/<project>/<session>/subagents/(includingsubagents/workflows/<wf>/…), each summarised with a cheap last-event line.
Everything is read-only — it only ever reads each subagent's own JSONL transcript, so it
never disturbs the monitored session. (For the whole-fleet Workflow cockpit, use the
workflow-monitor skill; for freeze detection, python -m monitorcore.watchdog.)
Windows-native, system Python (no venv). The
monitorcorepackage is stdlib-only, so any Python 3.11+ works (this machine: 3.14.3).monitorcoreis vendored in the siblingworkflow-monitorskill;tail_once.pyadds that dir tosys.pathautomatically, andsmoke.ps1setsPYTHONPATHto it.
Run (agent path) — START HERE
Deterministic, side-effect-free smoke of BOTH surfaces against a committed fixture transcript (no live Claude session, no windows opened):
Run: per-agent tail
Non-interactive: render the last N events of a transcript, then EXIT.
Run: discovery
From the sibling workflow-monitor dir on PYTHONPATH:
-> fixture-agent True general-purpose
(prints ASCII fields only: a bare python -c skips the UTF-8 stdout reconfigure, so don't
print the 'last' field — its ↳ glyph crashes a cp1252 pipe.)
Spawn one terminal per agent (power user)
Gotchas
Troubleshooting
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files