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.

Quality

89%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 use of a table format for the 16-component breakdown and concrete, copy-paste-ready fix commands. Its main weaknesses are the lack of a structured triage workflow (prioritizing which failures to address first) and the monolithic structure that could benefit from splitting the fixing guide and Inngest triage into separate referenced files.

Suggestions

Add a brief triage priority guide after the table — e.g., 'If score < 5: check k8s cluster and worker first, then Redis, then tests' — to create a clearer decision workflow.

Consider splitting 'Fixing Common Issues' and 'Inngest Hung-Run Quick Triage' into a separate TROUBLESHOOTING.md to keep the main skill lean and 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 health script invocation, specific fix commands for each common issue (git fetch, curl, kubectl, bun add, rm -rf), and the Inngest triage workflow are all copy-paste ready with concrete paths and flags.	3 / 3
Workflow Clarity	The 'When to Run' section provides clear triggers, and the Inngest triage has a numbered sequence. However, the main health check is a single script invocation with no explicit validation/feedback loop for what to do when the overall score is low — the 'Fixing Common Issues' section is a flat list without a structured triage workflow (e.g., 'if score < 5, check these first').	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and the table is excellent for scanning, but everything is in a single file with no references to supporting documentation. The health.sh script is referenced but no bundle files are provided, and the 16-component table plus fixing instructions plus Inngest triage makes this fairly long for a single SKILL.md.	2 / 3
	Total	10 / 12 Passed

Description

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 hits all the marks. It provides highly specific component-level detail about what gets checked, clearly defines the output format, and includes a comprehensive 'Use when' clause with natural trigger phrases covering both formal and informal user requests. The description is concise yet thorough, and the system-specific naming makes it highly distinctive.

Dimension	Reasoning	Score
Specificity	Lists numerous specific concrete components to check: 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 of specific 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 distinctive — it's specific to the 'joelclaw system' with a unique set of named components (Inngest, Typesense, pi-tools, memory pipeline). The combination of system-specific health checking with a scored output format makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

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: 2ca3686

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.