CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

messaging

Send facts to Joel through the Agent Comms Gateway, trace decisions by flowId, and preserve single-owner transport safety. Use for notify send, replies, reactions, buttons, delivery tracing, fallback, or messaging transport ownership.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized operational contract: executable commands, exact env vars and paths, a guarded rollback sequence with verification, and clear one-level-deep delegation to docs/gateway.md. Weaknesses are minor: an inline review date, a convoluted reserved-flag paragraph, and a missing concrete invocation for the rollback script and duplicate-poller diagnosis.

Suggestions

Move the 2026-08-12 `--kind` review date (and other migration-state notes) into an 'old patterns / deprecated' section so time-sensitive details don't age the main guidance.

Show the exact guarded invocation of `scripts/gateway-cutover-rollback.sh` (with the old pane ID argument) rather than describing it, and give a concrete step for locating a duplicate Telegram poller on a 409.

Consider moving the recurring-incident producer contract and fallback batching rules into a reference file (e.g., references/incident-contract.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep pointers.

DimensionReasoningScore

Conciseness

The body is dense with project-specific policy Claude cannot know (latch reconstruction, three-slot limit, fallback batch rules, single-owner doctrine) — nearly every token earns its place. Not 5 because a time-sensitive date is inline outside any 'old patterns' section ("Review making `--kind` required on 2026-08-12") and the reserved-but-unimplemented `--data`/`--ref` paragraph is slightly tangled; not 3 because there is no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Concrete, copy-paste-ready commands are given: `joelclaw notify send "The deploy failed..."`, the `--context '{...}'` JSON example, `joelclaw messages trace <flowId>`, plus exact env vars (`FALLBACK_CHANNEL=telegram`, `GATEWAY_TRANSPORT_SLIM_DOWN=1`) and file paths. Not 5 because the rollback script's invocation syntax is never shown ("invoke the script with the old pane ID" without the exact command) and how to locate a duplicate Telegram poller after a 409 is unspecified.

4 / 5

Workflow Clarity

The destructive rollback flow has an explicit guarded sequence with verification checkpoints ("verify the backup, stop the driver, close the gateway pane, verify the stable label is absent, then invoke the script"), and error recovery is addressed (a 409 means a forbidden second poller — find and stop it; do not mask it). Not 5 because the checkpoints are prose rather than a numbered validate/recover loop, and the duplicate-poller diagnosis step has no concrete procedure; not 3 because validation for the risky rollback operation is explicitly present, avoiding the destructive-operation cap.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body appropriately delegates runtime operations and rollback detail one level deep with a clearly signaled pointer: "Load `docs/gateway.md` or the `gateway` skill for runtime operations". Sections are well-organized and navigable. Not 5 because specialized policy (the recurring-incident producer contract and fallback batching rules) is fully inlined in SKILL.md where a reference file would keep the overview leaner.

4 / 5

Total

16

/

20

Passed

Description

87%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: third-person, concise, with an explicit 'Use for' trigger clause covering the real command surface (notify send, replies, reactions, buttons, tracing, fallback). Its only weaknesses are the slightly abstract "single-owner transport safety" phrase and a few missing natural synonyms (alert, ping, message).

DimensionReasoningScore

Specificity

Concrete actions named: "Send facts to Joel through the Agent Comms Gateway", "trace decisions by flowId", plus trigger-listed capabilities (notify send, replies, reactions, buttons, delivery tracing, fallback). Not 5 because "preserve single-owner transport safety" is an abstract doctrine phrase rather than a concrete action, and coverage has minor gaps (e.g., no mention of the Telegram platform or inbound interpretation). Not 3 because it lists several specific actions beyond the 1-2 anchor.

4 / 5

Completeness

Both parts are explicit: what — "Send facts to Joel through the Agent Comms Gateway, trace decisions by flowId, and preserve single-owner transport safety"; when — "Use for notify send, replies, reactions, buttons, delivery tracing, fallback, or messaging transport ownership." This matches the score-5 anchor (clear what AND when with concrete trigger phrases), and the explicit 'Use for' clause avoids the completeness cap of 3.

5 / 5

Trigger Term Quality

"notify send, replies, reactions, buttons, delivery tracing, fallback, or messaging transport ownership" are natural terms a user in this environment would say, matching the actual CLI surface (joelclaw notify send, messages trace). Not 5 because common synonyms like "alert", "ping", or "message Joel" are absent; not 3 because coverage goes well beyond a couple of generic keywords and includes the real command verbs.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct triggers: "Agent Comms Gateway", "flowId", "transport ownership", "fallback" framed around a single-owner gateway model. The proper nouns and CLI verbs make confusion with a generic messaging or notification skill very unlikely; minor overlap only on generic words like "replies" or "buttons".

5 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

joelhooks/joelclaw

Path

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