How do I install the Agent Healthcheck skill?

Run npx skillmds@latest add omninode-ai/agent-healthcheck in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Agent Healthcheck safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Agent Healthcheck?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Agent Healthcheck free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Agent Healthcheck?

OmniNode-ai (@omninode-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Agent Healthcheck by omninode-ai — Agent Skill

Name: Agent Healthcheck
Author: OmniNode-ai

Agent Healthcheck

Dispatch-only shim for agent stall detection and recovery. All detection and recovery logic lives in node_worker_stall_recovery (omnimarket). The skill parses args, builds the input envelope, dispatches to the node, and renders the receipt.

OmniNode-ai 0ad732d 2 files · 2.1 KB Updated Sep 17, 2026

File contents

/onex:agent_healthcheck — dispatch-only shim

Skill ID: onex:agent_healthcheck · Backing node: omnimarket/src/omnimarket/nodes/node_worker_stall_recovery/

Routing Contract

Classification: Deterministic
Dispatch: single invocation of node_worker_stall_recovery
No inline stall detection: all heuristics (inactivity, context overflow, rate limits, Bash long-timeout) live in the handler, not this skill
Routing failure handling: on dispatch failure, raise SkillRoutingError — surface it directly, do not produce prose

Dispatch

This skill is a thin shim — all stall detection and recovery logic lives in node_worker_stall_recovery (omnimarket).

INPUT_JSON='{"ticket_id":"<ticket_id>","agent_id":"<agent_id>","timeout_minutes":2,"context_threshold_pct":80,"max_redispatches":2,"dry_run":true}'
uv run onex run-node node_worker_stall_recovery --input "${INPUT_JSON}"

The node returns ModelStallRecoveryResult:

status: healthy | stalled | recovered | failed | escalated
stall_reason: non-empty string if stalled
checkpoint_path: path written on recovery
redispatch_count: number of redispatches performed
error: error message if status == failed

Checkpoint and relaunch semantics are governed by the recovery protocol implemented in the backing node. The backing node writes the recovery checkpoint, captures completed and remaining work, and relaunches or redispatches a fresh agent when recovery is required; this shim only forwards the invocation and returns the receipt.

Surface the JSON output directly. Do not implement detection inline.

Backing node: omnimarket/src/omnimarket/nodes/node_worker_stall_recovery/ Contract: node_worker_stall_recovery/contract.yaml

---name: agent-healthcheckdescription: Dispatch-only shim for agent stall detection and recovery. All detection and recovery logic lives in node_worker_stall_recovery (omnimarket). The skill parses args, builds the input envelope, dispatches to the node, and renders the receipt.---# /onex:agent_healthcheck — dispatch-only shim**Skill ID**: `onex:agent_healthcheck` · **Backing node**: `omnimarket/src/omnimarket/nodes/node_worker_stall_recovery/`## Routing Contract- **Classification**: Deterministic- **Dispatch**: single invocation of `node_worker_stall_recovery`- **No inline stall detection**: all heuristics (inactivity, context overflow, rate limits, Bash long-timeout) live in the handler, not this skill- **Routing failure handling**: on dispatch failure, raise `SkillRoutingError` — surface it directly, do not produce prose## DispatchThis skill is a **thin shim** — all stall detection and recovery logic lives in`node_worker_stall_recovery` (omnimarket).```bashINPUT_JSON='{"ticket_id":"<ticket_id>","agent_id":"<agent_id>","timeout_minutes":2,"context_threshold_pct":80,"max_redispatches":2,"dry_run":true}'uv run onex run-node node_worker_stall_recovery --input "${INPUT_JSON}"```The node returns `ModelStallRecoveryResult`:- `status`: `healthy | stalled | recovered | failed | escalated`- `stall_reason`: non-empty string if stalled- `checkpoint_path`: path written on recovery- `redispatch_count`: number of redispatches performed- `error`: error message if `status == failed`Checkpoint and relaunch semantics are governed by the recovery protocolimplemented in the backing node. The backing node writes the recovery checkpoint, captures completedand remaining work, and relaunches or redispatches a fresh agent when recoveryis required; this shim only forwards the invocation and returns the receipt.Surface the JSON output directly. Do not implement detection inline.**Backing node:** `omnimarket/src/omnimarket/nodes/node_worker_stall_recovery/`**Contract:** `node_worker_stall_recovery/contract.yaml`

Frequently asked questions