gateway-setup

Set up a persistent AI agent gateway on macOS with Redis event bridge, heartbeat monitoring, and multi-session routing. Interactive Q&A to match your intent — from minimal (Redis + extension) to full (embedded daemon + Telegram + watchdog). Use when: 'set up a gateway', 'I want my agent always on', 'event bridge', 'heartbeat monitoring', 'agent notifications', or any request to make an AI agent persistent and reachable.

2.08x

Quality

88%

Does it follow best practices?

Impact

96%

2.08x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

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 a strong skill description that clearly communicates specific capabilities (persistent agent gateway, Redis event bridge, heartbeat monitoring, multi-session routing), provides explicit trigger guidance via a 'Use when' clause with natural phrases, and occupies a distinctive niche unlikely to conflict with other skills. The description is well-structured, uses third person voice appropriately, and balances technical specificity with user-friendly trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'persistent AI agent gateway on macOS', 'Redis event bridge', 'heartbeat monitoring', 'multi-session routing', 'embedded daemon', 'Telegram', 'watchdog'. Also describes the interactive Q&A approach and the range from minimal to full setup.	3 / 3
Completeness	Clearly answers both 'what' (set up a persistent AI agent gateway with Redis, heartbeat, multi-session routing, interactive Q&A for configuration) and 'when' (explicit 'Use when:' clause with multiple trigger phrases and a catch-all condition).	3 / 3
Trigger Term Quality	Includes a strong set of natural trigger terms: 'set up a gateway', 'agent always on', 'event bridge', 'heartbeat monitoring', 'agent notifications', 'persistent and reachable'. These cover both specific technical terms and natural user phrasings.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche — persistent AI agent gateway on macOS with Redis event bridge is very specific and unlikely to conflict with other skills. The combination of macOS, Redis, heartbeat monitoring, and Telegram integration creates a clear, unique identity.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

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

This is a highly actionable and well-structured skill with excellent executable code examples and clear multi-step workflows across four progressive tiers. Its main weakness is length — at 400+ lines it's a monolithic document that would benefit from splitting tier-specific details into separate referenced files. The Intent Alignment Q&A section and verification checklist are strong additions that guide both scoping and validation.

Suggestions

Split Tiers 2-4 into separate referenced files (e.g., TIER2-HEARTBEAT.md, TIER3-MULTISESSION.md) and keep only Tier 1 + brief tier summaries in the main SKILL.md to improve progressive disclosure and reduce token cost.

Move the Decision Chain/ADR table and Credits section to a separate ARCHITECTURE.md file — these are reference material, not setup instructions.

Consider moving the full extension source code into a referenced file and showing only the key patterns (drain function, pub/sub setup) inline to reduce the main document's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) and includes some sections that could be trimmed or externalized (e.g., the full Decision Chain/ADR table, Credits, detailed Known Limitations). However, most content is concrete code rather than explanatory fluff, and it doesn't over-explain concepts Claude already knows. The tiered architecture adds necessary length but some tiers (especially Tier 4) could be offloaded to separate files.	2 / 3
Actionability	Excellent actionability throughout — every tier includes fully executable code (TypeScript extension, bash commands, crontab entries, launchd plist XML), specific file paths, and copy-paste ready snippets. The pushEvent utility, the full extension source, and verification commands are all concrete and complete.	3 / 3
Workflow Clarity	Each tier has clearly numbered build steps with explicit sequencing. The verification checklist at the end provides validation checkpoints per tier. Critical setup notes at the top call out common failure modes (GATEWAY_ROLE, serveHost, ioredis issues) with specific fixes. The watchdog provides a feedback loop for heartbeat failures. The Known Limitations section honestly documents the drain race condition and suggests fixes.	3 / 3
Progressive Disclosure	The tiered architecture (1-4) provides good conceptual progressive disclosure, and the Intent Alignment section helps scope the build. However, the entire skill is monolithic — Tiers 2-4 could be separate files referenced from the main skill. The ADR table references external files which is good, but the inline content is very long. The full extension source code (~80 lines) could be in a separate file with just the key patterns shown inline.	2 / 3
	Total	10 / 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: ce9ca8e

Reviewed: 1 day 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.