Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
joelhooks avatar

Joelclaw System Check

  • 36 installs
  • 61 repo stars
  • Updated August 4, 2026
  • joelhooks/joelclaw

Run a comprehensive joelclaw health check across k8s, worker, Inngest, Redis, OTEL, tests, and more, outputting a 1-10 score with per-component breakdown.

About

Runs health.sh to produce a scored, per-component report of system state across 16 checks. A developer uses it at session start or after loops/infra changes to orient and triage.

  • Single script scores 16 components green/yellow/red
  • Run at session start, after loops, after infra changes, or when something feels off

Joelclaw System Check by the numbers

  • 36 all-time installs (skills.sh)
  • Ranked #341 of 596 Debugging skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/joelhooks/joelclaw --skill joelclaw-system-check

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs36
repo stars61
Last updatedAugust 4, 2026
Repositoryjoelhooks/joelclaw

What it does

Run a comprehensive joelclaw health check across k8s, worker, Inngest, Redis, OTEL, tests, and more, outputting a 1-10 score with per-component breakdown.

Files

SKILL.mdMarkdownGitHub ↗

joelclaw System Health Check

Run scripts/health.sh for a full system health report with 1-10 score.

~/Code/joelhooks/joelclaw/skills/joelclaw-system-check/scripts/health.sh

What It Checks (16 components)

CheckWhatGreen (10)Yellow (5-7)Red (1-3)
k8s clusterpods in joelclaw namespace4/4 Running, 0 restartspartial podsno pods
pdsAT Proto PDS on :9627version + collectionspod running, host publish degradedpod not running
workersystem-bus on :311116+ functionsresponding, low countdown
inngest server:8288 reachablerespondingdown
redis/gatewayRedis + gateway session queuesconnected, low pending queueconnected, backlog risingunavailable
typesense/otelTypesense health + OTEL query pathhealthy + queryablehealthy, query degradedunavailable
testsisolated per-file bun test in system-bus0 failfailures
tsctsc --noEmitcleantype errors
repo syncmonorepo HEAD vs origin/mainin syncahead/behindrepo unavailable
memory pipelinejoelclaw inngest memory-healthhealthy checksdegraded checksfailing checks
pi-toolsextension deps installedall 3 depsmissing
git configuser.name + email setsetmissing
active loopsjoelclaw loop listqueryablequery degradedunavailable
gogcliGoogle Workspace authaccount authed, token validtoken stored, no passwordnot configured
diskfree space + loop tmp<80% used>80%
stale tests__tests__/ + acceptance testscleanpresent

When to Run

  • Session start — orient on system state before doing work
  • After loops complete — verify nothing broke
  • After infra changes — k8s, worker, Redis config
  • When something feels off — quick triage

Fixing Common Issues

Repo drift: cd ~/Code/joelhooks/joelclaw && git fetch origin && git status -sb

pi-tools broken: cd ~/.pi/agent/git/github.com/joelhooks/pi-tools && bun add @sinclair/typebox @mariozechner/pi-coding-agent @mariozechner/pi-tui @mariozechner/pi-ai

PDS unreachable: curl -fsS http://localhost:9627/xrpc/_health then kubectl get deploy,svc,pods,pvc -n joelclaw | rg 'bluesky-pds|NAME' (or if pod down: kubectl rollout restart deployment/bluesky-pds -n joelclaw)

Worker down: joelclaw inngest restart-worker --register

Stale tests: rm -rf ~/Code/joelhooks/joelclaw/packages/system-bus/__tests__/ && find ~/Code/joelhooks/joelclaw/packages/system-bus/src -name "*.acceptance.test.ts" -delete

System-bus test false reds: the health script runs each src/**/*.test.ts file in its own Bun process because several legacy tests monkey-patch globals or use mock.module. If the aggregate health check is green but raw bun test is red, suspect inter-file mock leakage before treating runtime code as broken.

Loop tmp bloat: rm -rf /tmp/agent-loop/loop-*/ (only when no loops are running)

Inngest Hung-Run Quick Triage

When a run appears stuck after first step:

joelclaw run <run-id>

If trace shows Finalization failure with "Unable to reach SDK URL":

1. Verify registration/health: joelclaw inngest status

2. Verify function is present where expected: joelclaw functions | rg -i "manifest-archive|<function-name>"

3. Check for stale app registrations in Inngest UI/API and remove stale SDK URLs.

4. Assume possible handler blocking (not just network): review recent step code for filesystem/Redis/subprocess blocking before step response.

Related skills

Debuggingmonitoringinfra

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.