joelclaw-system-check
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.
91
89%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly enumerates the specific components being checked, clearly describes the output format, and provides a comprehensive set of natural trigger terms in an explicit 'Use when' clause. It is highly distinctive due to the named system and specific component list, making it very unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists numerous specific concrete components checked: k8s cluster, worker, Inngest, Redis, Typesense/OTEL, tests, TypeScript, repo sync, memory pipeline, pi-tools, git config, active loops, disk, stale tests. Also specifies the output format (1-10 score with per-component breakdown). | 3 / 3 |
Completeness | Clearly answers both 'what' (run comprehensive health check across many named components, output a 1-10 score with breakdown) and 'when' (explicit 'Use when:' clause with multiple trigger phrases and the additional context of session start). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'system health', 'health check', 'is everything working', 'system status', 'how's the system', 'check everything', and 'at session start to orient'. These cover both formal and casual phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to the 'joelclaw system' with a unique combination of components (k8s, Inngest, Redis, Typesense, pi-tools, memory pipeline). The system-wide health check with scoring output is a clear niche unlikely to conflict with individual component skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent conciseness — the table format for 16 components is particularly effective. The main weakness is the lack of explicit feedback loops after remediation steps (re-run health check to confirm fix) and the content could benefit from splitting the detailed troubleshooting into a separate file to keep the main skill leaner.
Suggestions
Add an explicit feedback loop after each fix: e.g., 'After fixing, re-run `scripts/health.sh` to verify the component scores green.'
Consider moving the 'Fixing Common Issues' and 'Inngest Hung-Run Quick Triage' sections to a separate TROUBLESHOOTING.md and linking from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. The table format is extremely efficient for conveying 16 component checks with their scoring thresholds. No unnecessary explanations of what k8s or Redis are — assumes Claude's competence throughout. | 3 / 3 |
Actionability | Fully executable commands throughout: the main health script, every fix command is copy-paste ready with full paths, and the Inngest triage section provides a concrete step-by-step diagnostic flow with real CLI commands. | 3 / 3 |
Workflow Clarity | The 'When to Run' section provides clear triggers, and the fixing section gives concrete remediation steps. However, the main workflow is essentially 'run one script,' and the fixing steps lack validation checkpoints — e.g., after running a fix, there's no explicit 'now re-run health.sh to verify' feedback loop. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (table, when to run, fixes, triage), but everything is inline in one file. The 16-component table and all fix commands could benefit from splitting detailed remediation into a separate troubleshooting reference, keeping SKILL.md as a concise overview. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- joelhooks/joelclaw
- Commit
ce9ca8e
- Reviewed
Table of Contents
Is this your skill?
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.