Menu
How to check if deployed projects are healthy. What "healthy" means per project type.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Complete reference for the factory CLI — all commands, arguments, options, and usage. Use when an agent needs to invoke factory commands, check correct syntax, or understand available options.
When and how to write a human-action-needed entry to memory/{agent}/needs.md. Agents write these entries when they hit blockers that only a human can resolve.
When you encounter a failure, correction, or new pattern, write a learning and optionally propose a skill.
How the factory workspace is organized and what each directory means.
What to examine during a reflection pass and how to write observations to memory/{agent}/needs.md.
When and how to write scenario holdouts for factory verification.
| name | monitoring |
| description | How to check if deployed projects are healthy. What "healthy" means per project type. |
CLI tool — healthy if:
Web API / service — healthy if:
/health or /ping) returns 200Data pipeline — healthy if:
Background worker / scheduled job — healthy if:
On each hourly heartbeat, for each active deployed project:
tasks/maintenance/{project}-{YYYY-MM-DD}-health.md
with: what was checked, what was found, suggested remediationDo not attempt automated remediation without a maintenance task being created first. The human decides whether to act on a health alert.
Write a maintenance task for:
A single transient failure is noted in the daily log but does not create a task.