CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

runtime-monitor

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.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and lean: concrete CLI commands with flags, complete JSON payloads, an explicit load order, and a clear first-glance-to-deep-dive escalation path. Its only weaknesses are a duplicated command listing and implicit rather than explicit validation checkpoints.

DimensionReasoningScore

Conciseness

The body is almost entirely terse commands, payloads, and rules with no explanations of concepts Claude already knows. The 'canonical operator surfaces' list at the top duplicates commands re-shown with flags in 'What to use when', which is the kind of minor redundancy that keeps it below a 5.

4 / 5

Actionability

Copy-paste ready commands with flags throughout ('joelclaw jobs status --hours 1 --count 10', 'joelclaw queue observe --hours 1') and complete JSON payloads covering the pi monitor's start/status/stop cases; the '<iso|ms>' placeholder is an explicitly signaled parameter rather than pseudocode. Matches anchor 5.

5 / 5

Workflow Clarity

An explicit load-order sequence (system-architecture, then pi-tui-design, then joelclaw) and a clear escalation path ('Use these once jobs status tells you the queue layer is the interesting bit'). Validation checkpoints are implicit rather than explicit steps, matching anchor 4; the read-only nature of monitoring means the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

Single-file skill with clean section headers and clearly signaled cross-skill references in the Load order section. At roughly 105 lines with the pi-monitor action API inlined, it exceeds the under-50-line simple-skill case, so the inlined action reference represents a minor organization gap — anchor 4, not 5.

4 / 5

Total

17

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states a concrete what (specific systems and tools), an explicit when with five natural trigger phrases, and pairing guidance that reduces conflict risk. The only gaps are missing system-name trigger terms and monitoring-verb-only action coverage.

DimensionReasoningScore

Specificity

Names concrete systems (Redis queue, Restate, Dkron, transitional Inngest) and tools (joelclaw CLI, pi TUI monitor extension) plus several actions (monitor workloads, run a workload dashboard, report system state). Not a 5 because the actions are all monitoring-verb variants rather than a comprehensive set of distinct capabilities.

4 / 5

Completeness

Explicitly answers both what ('Monitor ADR-0217 real workloads across Redis queue, Restate, Dkron, and transitional Inngest using joelclaw CLI plus the pi TUI monitor extension') and when with concrete trigger phrases ('Use when asked to monitor jobs, watch runtime health...'). Matches the anchor 5 example structure; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

'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' provides five natural phrasings with colloquial synonyms. Not a 5 because it omits system-name triggers a user would naturally say (e.g., 'check Restate' or 'queue depth').

4 / 5

Distinctiveness Conflict Risk

ADR-0217, joelclaw, and the named runtime systems carve a clear niche, and pairing guidance ('Always pair with pi-tui-design... system-architecture') further disambiguates. Broad triggers like 'watch runtime health' and 'report back on system state' leave minor overlap risk with a generic health-check skill, matching anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/runtime-monitor/SKILL.md

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.