Run a comprehensive health check of the joelclaw system — k8s cluster, worker, Inngest, Redis, Typesense/OTEL, tests, TypeScript, repo sync, memory pipeline, pi-tools, git config, active loops, disk, stale tests. Outputs a 1-10 score with per-component breakdown. Use when: 'system health', 'health check', 'is everything working', 'system status', 'how's the system', 'check everything', or at session start to orient.
92
89%
Does it follow best practices?
Impact
99%
7.07xAverage score across 3 eval scenarios
Passed
No known issues
Health check runbook and fix commands
Uses health.sh path
0%
100%
Session start trigger
66%
100%
1-10 scoring explained
0%
100%
Worker fix command
0%
100%
PDS port-forward fix
0%
100%
PDS restart fix
0%
100%
Repo drift fix command
25%
100%
pi-tools fix packages
0%
100%
Stale tests fix command
0%
100%
Loop tmp cleanup caveat
25%
100%
joelclaw CLI consistency
25%
100%
Inngest hung-run triage procedure
joelclaw run command
0%
100%
Finalization failure signature
0%
100%
Unable to reach SDK URL
0%
100%
joelclaw inngest status check
0%
100%
Function presence verification
0%
100%
Stale app registration check
58%
100%
Handler blocking categories
21%
100%
Post-first-step context
100%
100%
Ordered steps
50%
100%
Component health diagnostics and thresholds
Worker function threshold
0%
100%
Worker CLI command
0%
100%
Redis pending queue threshold
0%
100%
Redis CLI command
0%
100%
Disk usage threshold
0%
90%
Loop tmp threshold
0%
100%
Memory pipeline CLI
0%
100%
Typesense endpoint
100%
100%
OTEL CLI command
0%
100%
Active loops CLI
0%
100%
Tests use bun
0%
100%
TSC uses bunx
0%
100%
825972c
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.