CtrlK
BlogDocsLog inGet started
Tessl Logo

gateway-diagnose

Diagnose gateway failures by reading daemon logs, session transcripts, Redis state, and OTEL telemetry. Full Telegram path triage: daemon process → Redis channel → command queue → pi session → model API → Telegram delivery. Use when: 'gateway broken', 'telegram not working', 'why is gateway down', 'gateway not responding', 'check gateway logs', 'what happened to gateway', 'gateway diagnose', 'gateway errors', 'review gateway logs', 'fallback activated', 'gateway stuck', or any request to understand why the gateway failed. Distinct from the gateway skill (operations) — this skill is diagnostic.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a lean, well-sequenced diagnostic playbook that adds only non-obvious domain guidance. It could be slightly more actionable by listing concrete joelclaw diagnostic subcommands rather than relying on the --help pointer.

Suggestions

Add one or two concrete `joelclaw gateway` diagnostic subcommands (e.g. status, events, tail) so the guidance is executable without first running --help.

Make the validation checkpoint explicit mid-flow — e.g. 'after tracing the path, confirm the failure localizes to one stage before following it to cause'.

Consider a short inline checklist of the path stages (ingress → durable queue → policy → gateway session → adapter → delivery receipt) to make the trace sequence scannable.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence; every paragraph carries domain-specific gotchas Claude would not already know ('Queue age alone does not prove a hung agent', 'A successful queue submission is not proof of delivery') with no padding or basic-concept explanations.

5 / 5

Actionability

Gives one concrete command (`joelclaw gateway --help`) and specific things to read and compare (timestamps, correlation ids, progress, timeouts across ingress→queue→policy→session→adapter→receipt), but stops short of enumerating specific diagnostic subcommands beyond the --help pointer.

4 / 5

Workflow Clarity

Clear sequenced flow (find failing id → read entrypoint/config/runbook → resolve placement → trace path → compare → follow first failure → verify and report) with a terminal verification step, though intermediate validation checkpoints are mostly implicit rather than gated.

4 / 5

Progressive Disclosure

A focused under-50-line single-purpose skill with well-organized topical sections and no need for external references; meets the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

100%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.

The description is specific, trigger-rich, and clearly distinguishes this diagnostic skill from the operational gateway skill. It uses third-person voice and answers both what and when with concrete, natural triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions on named artifacts — 'reading daemon logs, session transcripts, Redis state, and OTEL telemetry' plus a full Telegram path triage through daemon process → Redis channel → command queue → pi session → model API → Telegram delivery.

5 / 5

Completeness

Explicitly answers both what (diagnose gateway failures by reading logs/transcripts/Redis/OTEL and triaging the Telegram path) and when (a concrete 'Use when:' clause with many trigger phrases).

5 / 5

Trigger Term Quality

Comprehensive set of natural phrases a user would actually say ('gateway broken', 'telegram not working', 'why is gateway down', 'gateway stuck', 'fallback activated') including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Carves a clear diagnostic niche and explicitly disambiguates — 'Distinct from the gateway skill (operations) — this skill is diagnostic' — minimizing overlap risk.

5 / 5

Total

20

/

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.

Validation15 / 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
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.