CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gateway

Operate the joelclaw gateway daemon — the always-on pi session that receives events, notifications, and messages. Use the joelclaw CLI for ALL gateway operations. Use when: 'restart gateway', 'gateway status', 'is gateway healthy', 'push to gateway', 'gateway not responding', 'telegram not working', 'messages not going through', 'gateway stuck', 'gateway debug', 'check gateway', 'drain queue', 'test gateway', 'stream events', or any task involving the gateway daemon.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gateway/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 genuinely operational and actionable — real commands, complete code, and an excellent failure-mode table — but it reads partly as a changelog of ADR slices rather than a lean instruction file. Verbosity, missing validation around the destructive drain operation, and the absence of any reference-file split hold it back from the top band.

Suggestions

Move the per-ADR implementation details (session pressure, interruptibility, operator tracing, channel runtime contracts, rank-slice behavior) into one-level-deep reference files and keep SKILL.md as an operator overview with the command reference, triage flow, and failure-mode table.

Add validation guidance for destructive/batch operations — e.g., what to check before and after 'joelclaw gateway drain' (verify pending events per session with 'gateway events', confirm the queues were the actual problem) — and remove changelog-style 'now exposes/now distinguishes' phrasing in favor of current-state documentation.

Close the small actionability gaps: add 'joelclaw gateway diagnose' to the CLI command list (it is referenced throughout but never defined) and briefly explain how to obtain the Telegram platformMessageId required by 'doctor --live'.

DimensionReasoningScore

Conciseness

The body is information-dense and assumes operator knowledge (no basic-concept explanations), but at ~330 lines it includes changelog-style prose ('now distinguishes', 'now exposes', 'Current rank-6 behavior'), an exhaustive 15-bullet low-signal guardrail enumeration, and version-sensitive details (the 'claude-opus-4-6' fallbackTimeoutMs floor) not quarantined in a deprecated/old-patterns section. Mostly valuable content that still could be tightened considerably — fits the 3 anchor better than 4's 'minor instances'.

3 / 5

Actionability

Highly executable: a copy-paste CLI command block with per-command comments, complete TypeScript examples for gateway.notify() and pushGatewayEvent(), a symptom→cause→fix failure table, and a key-files table. Minor gaps keep it from 5: 'joelclaw gateway diagnose' is used throughout but missing from the command list, and doctor --live's required 'Telegram platformMessageId' is never explained or sourced.

4 / 5

Workflow Clarity

Triage and recovery flows are sequenced with checkpoints (restart prints the doctor summary, 'gateway test' verifies delivery, expected disabled-channel state is specified, restart-only-on-evidence rules), but the skill includes destructive/batch operations — notably 'joelclaw gateway drain' (clear all event queues) — with no validation or verification guidance. Per the rubric's explicit cap, missing validation for destructive/batch operations caps this at 3 despite otherwise good sequencing.

3 / 5

Progressive Disclosure

The bundle contains no references/ or scripts/ directories (only two unreferenced logo assets), so all content lives inline in a ~330-line SKILL.md. Section headers are clear and there are some one-level pointers (.brain/...svx, ADR anchors, related skills), but content that clearly belongs in separate files — the failure-modes table, channel runtime contracts, Inngest integration details — is inlined. Matches the 3 anchor: some structure, but content that should be separate is inline.

3 / 5

Total

13

/

20

Passed

Description

91%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 clearly states what the skill does and when to use it, with an unusually rich set of natural trigger phrases including failure-state language. The only weaknesses are a thin set of explicit action verbs and a couple of generic symptom triggers with mild overlap risk against neighboring skills.

DimensionReasoningScore

Specificity

Names the domain ('Operate the joelclaw gateway daemon — the always-on pi session that receives events, notifications, and messages') and concrete operations (restart, status, push, drain, test, stream) via its trigger phrases, but the explicit action verbs describing what the skill does are limited to 'operate' and 'use the joelclaw CLI', leaving minor coverage gaps. Not 5 because a comprehensive list of specific concrete actions is not stated directly; not 3 because it goes beyond naming the domain with only 1-2 generic actions.

4 / 5

Completeness

Explicitly answers both: what ('Operate the joelclaw gateway daemon... Use the joelclaw CLI for ALL gateway operations') and when ('Use when: ... or any task involving the gateway daemon') with a long list of concrete trigger phrases. This is a direct match for the top anchor; the 4-anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Comprehensive natural phrasings users would actually say, including failure-state variants: 'restart gateway', 'is gateway healthy', 'gateway not responding', 'telegram not working', 'messages not going through', 'gateway stuck', 'drain queue', 'test gateway', 'stream events'. Clearly matches the comprehensive-coverage anchor; nothing significant is missing.

5 / 5

Distinctiveness Conflict Risk

A named, unique system ('joelclaw gateway daemon') with mostly distinct triggers gives a clear niche, but generic symptom phrases like 'telegram not responding... not working' and 'messages not going through' carry minor overlap risk with adjacent messaging/webhook/event-bus skills. Mostly distinct with minor overlap — matches the 4 anchor better than 5's 'minimal conflict risk'.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/gateway/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.