メニュー
Use when a mylab executor needs to start, poll, or inspect a long-running job. Prefer the documented `mylab tool start-job`, `wait-job`, and `tail-job` CLI flow instead of reading source code or inventing alternate entrypoints.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the main loop is parameter generation -> batch experiments -> result collection -> comparison for a parameter experiment round.
Use when the main loop is idea -> implementation -> training -> eval -> analysis for a structural experiment round.
Use when the main loop is parameter generation -> batch experiments -> result collection -> comparison for a parameter experiment round.
Use when the main loop is idea -> implementation -> training -> eval -> analysis for a structural experiment round.
| name | mylab-job-monitor |
| description | Use when a mylab executor needs to start, poll, or inspect a long-running job. Prefer the documented `mylab tool start-job`, `wait-job`, and `tail-job` CLI flow instead of reading source code or inventing alternate entrypoints. |
Use this skill when the task is to launch or track long-running work inside a mylab run.
mylab tool start-job.job_id, stdout_path, and stderr_path in structured logs when the surrounding workflow expects it.mylab tool wait-job instead of switching back to a foreground shell command.mylab tool tail-job.mylab source code just to discover an alternative way to start jobs unless the documented CLI fails in the current run.python -c wrappers around cmd_start_job or start_job when the CLI already works.Read references/complete-example.md for a full end-to-end example, including the expected JSON payload and structured log append.