CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

85

2.08x
Quality

81%

Does it follow best practices?

Impact

96%

2.08x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 with executable code and well-sequenced tiered workflows backed by a verification checklist. Its main weakness is structure: it inlines a large volume of code and detail that would be better split into reference files, leaving progressive disclosure well below the ideal. Conciseness is moderate due to this same inline volume.

Suggestions

Split the full extension source, watchdog snippet, and launchd plist into separate reference files (e.g., references/tier1-extension.ts, references/tier2-launchd.plist) and link to them from the body so SKILL.md reads as an overview.

Add an explicit validate/feedback loop for the Redis write path (e.g., verify the event was delivered, retry on failure) to turn the workflow_clarity 4 into a 5.

Trim the inline ADR decision-chain table and Known Limitations to a short pointer summary, moving the detail into a referenced ADR/limitations file to reduce inline length.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but the Decision Chain ADR table, Known Limitations, and Credits sections plus full multi-tier inline code (~460 lines) add material length that a leaner overview pointing to references could trim. It does not over-explain basic concepts, so it stays above a 2, but the volume pushes it below the lean 4/5 anchors.

3 / 5

Actionability

Fully executable copy-paste-ready TypeScript and bash (e.g., the complete index.ts extension, crontab one-liner, launchd plist, curl-piped setup script) covering the common cases with specific commands and realistic examples.

5 / 5

Workflow Clarity

Tiered build steps are clearly sequenced and a Verification Checklist provides explicit checkpoints (status bar, test event push, watchdog alarm after 30 min). The drain race-condition caveat is disclosed but the destructive/batch redis write path is not guarded by an explicit validate-then-retry loop, capping it just below 5.

4 / 5

Progressive Disclosure

The body is a near-monolithic wall of inline code and detail (full extension source, plist, multiple tier implementations) rather than an overview pointing to one-level-deep references; the only external pointer is to a joelclaw.com article, and the ADR links point outside the bundle with no local reference files present.

2 / 5

Total

14

/

20

Passed

Description

95%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 strong: concrete capabilities, an explicit 'Use when' trigger list with natural phrasings, and a distinct niche. It is written in third person and avoids vague fluff. Minor gap in capability breadth (cron/scheduled events implied but not enumerated) keeps specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "Redis event bridge, heartbeat monitoring, and multi-session routing", "embedded daemon + Telegram + watchdog" — with minor gaps (e.g., no mention of the cron/scheduled-event path). It is above the 3-anchor (which names domain + only 1-2 actions) but stops short of the comprehensive, many-action coverage of a 5.

4 / 5

Completeness

Clearly answers both 'what' (persistent AI agent gateway on macOS with Redis event bridge, heartbeat monitoring, multi-session routing) and 'when' via the explicit "Use when:" clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides an explicit quoted trigger list — "'set up a gateway'", "'I want my agent always on'", "'event bridge'", "'heartbeat monitoring'", "'agent notifications'" — plus a catch-all phrasing users would naturally say, giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (persistent AI agent gateway on macOS with Redis/heartbeat/multi-session routing) with role-specific triggers; minimal realistic overlap with unrelated skills.

5 / 5

Total

19

/

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.

Validation14 / 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: 7 suspicious

Warning

Total

14

/

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.