About

Imported from joelhooks/joelclaw (skills/runtime-monitor/SKILL.md). Install upstream with npx skills add joelhooks/joelclaw --skill runtime-monitor. Copyright stays with the author.

Runtime Monitor

Name: runtime-monitor
Author: joelhooks

Use this skill when the task is real workload monitoring, not vague status-checking.

The canonical operator surfaces are:

joelclaw jobs status
joelclaw queue depth
joelclaw queue control status
joelclaw queue observe
joelclaw restate status
joelclaw restate cron status
pi extension tool: runtime_jobs_monitor

Load order

Before doing runtime monitor work:

load system-architecture
load pi-tui-design if you are building or changing the monitor widget/TUI
load joelclaw for CLI operator flows

What to use when

First glance

joelclaw jobs status --hours 1 --count 10

This is the first operator answer to:

can the system take more work right now?
is the queue/runtime layer healthy?
is Dkron alive?
is Inngest still healthy during transition?

Queue-specific investigation

joelclaw queue depth
joelclaw queue control status --hours 1
joelclaw queue observe --hours 1
joelclaw queue stats --since <iso|ms>

Use these once jobs status tells you the queue layer is the interesting bit.

Runtime substrate investigation

joelclaw restate status
joelclaw restate cron status
joelclaw runs --count 20 --hours 1

Use these when the top-level surface says Restate, Dkron, or transitional Inngest needs a closer look.

Async pi monitor

The loaded pi extension at packages/pi-extensions/inngest-monitor/index.ts exposes:

runtime_jobs_monitor
inngest_send
inngest_runs

Start

{"action":"start","interval":5,"report":true}

Effects:

polls joelclaw jobs status in the background
paints a persistent TUI widget
emits OTEL on runtime severity changes and meaningful workload-state changes
sends hidden follow-up summaries when the runtime meaningfully changes or the monitor stops/times out

Status

{"action":"status"}

Returns the latest runtime snapshot:

overall status/summary
queue depth
active pause count
Restate / Dkron / Inngest state

Stop

{"action":"stop"}

Stops the background poller and sends a final follow-up summary.

Rules

joelclaw jobs status is the aggregated truth surface; do not rebuild the same picture by hand unless the command is wrong.
If jobs status is noisy or misleading, report the defect and use bounded underlying evidence. Change the CLI only when implementation is in scope.
For TUI work, prefer compact status blocks with explicit severity and short summaries. No decorative sludge.
Any runtime monitor widget line must be clamped to the active terminal width with pi-tui truncation (truncateToWidth / visibleWidth). Pi will crash narrow terminals if a custom widget emits over-wide lines.
During transition, Inngest stays visible but must not dominate the runtime story when Restate + queue + Dkron are the real workload path.
Report earned truth only. If the monitor compiles but hasn’t been dogfooded, say that.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/joelhooks-joelclaw-runtime-monitor/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

joelhooks-joelclaw-runtime-monitor.ocm.jsonjson

{
  "ocm": "1",
  "id": "joelhooks-joelclaw-runtime-monitor",
  "kind": "skill",
  "name": "runtime-monitor",
  "description": "Monitor ADR-0217 real workloads across Redis queue, Restate, Dkron, and transitional Inngest using joelclaw CLI plus the pi TUI monitor extension. Use when asked to monitor jobs, watch runtime health, keep an eye on async work, run a workload dashboard, or report back on system state. Always pair with `pi-tui-design` for TUI work and `system-architecture` for topology truth.",
  "publisher": "joelhooks",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "data_analysis"
    ],
    "tags": [
      "skill-md",
      "runtime",
      "monitor",
      "queue",
      "restate",
      "dkron",
      "inngest",
      "tui",
      "adr-0217",
      "skills-sh"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Monitor ADR-0217 real workloads across Redis queue, Restate, Dkron, and transitional Inngest using joelclaw CLI plus the pi TUI monitor extension. Use when asked to monitor jobs, watch runtime health, keep an eye on async work, run a workload dashboard, or report back on system state. Always pair with `pi-tui-design` for TUI work and `system-architecture` for topology truth."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "skills.sh",
      "repository": "https://github.com/joelhooks/joelclaw",
      "path": "skills/runtime-monitor/SKILL.md",
      "ref": "HEAD",
      "url": "https://github.com/joelhooks/joelclaw/blob/HEAD/skills/runtime-monitor/SKILL.md",
      "key": "joelhooks/joelclaw/skills/runtime-monitor/SKILL.md"
    }
  },
  "instructions": "# Runtime Monitor\n\nUse this skill when the task is **real workload monitoring**, not vague status-checking.\n\nThe canonical operator surfaces are:\n\n- `joelclaw jobs status`\n- `joelclaw queue depth`\n- `joelclaw queue control status`\n- `joelclaw queue observe`\n- `joelclaw restate status`\n- `joelclaw restate cron status`\n- pi extension tool: `runtime_jobs_monitor`\n\n## Load order\n\nBefore doing runtime monitor work:\n\n1. load `system-architecture`\n2. load `pi-tui-design` if you are building or changing the monitor widget/TUI\n3. load `joelclaw` for CLI operator flows\n\n## What to use when\n\n### First gl",
  "cost": {
    "context_tokens": 747
  }
}

Fetch it by URL: GET /api/v1/registry/joelhooks-joelclaw-runtime-monitor/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.