CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

imsg-rpc

Set up, maintain, and debug the imsg-rpc Unix socket daemon that gives the gateway iMessage access via JSON-RPC. Covers FDA setup, code signing, launchd service, and the imsg source repo.

Quality

82%

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

88%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 dense, highly operational runbook: every section is executable commands with explicit healthy-state definitions and symptom-based troubleshooting feedback loops. The only structural refinements are trimming the build-local.sh duplication and potentially splitting the protocol reference into a separate file.

DimensionReasoningScore

Conciseness

The body is lean: terse architecture diagram, command blocks, and a files table with no padding or explanations of concepts Claude already knows. Not 5 because "cd ~/Code/steipete/imsg && ./build-local.sh" and its behavior description are repeated across Rebuild, FDA Setup step 2, and Troubleshooting.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (launchctl print/kickstart, lsof, sqlite3 TCC query, log show predicate, open System Settings URL) with concrete interpretation guidance like "auth_value 2 = allowed, 0 = denied". Not 4 because no section relies on hints or pseudocode.

5 / 5

Workflow Clarity

FDA Setup is a numbered 4-step sequence with an explicit verification step ("Verify: tail -f ... should show watch.subscribe OK"), Status Check defines the healthy state, and Troubleshooting provides symptom → diagnostic command → fix feedback loops for each failure mode. Not 4 because validation checkpoints and error-recovery loops are explicit rather than implicit.

5 / 5

Progressive Disclosure

Clear section headers, a Files table mapping every path, and no nested references; with no bundle files present, everything is one level deep. Not 5 because at ~165 lines (above the under-50-line exception) content like the JSON-RPC Protocol Reference and FDA Setup guide are borderline candidates for separate reference files.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific, well-scoped description with strong domain keywords and near-zero conflict risk. Its main weakness is the absence of an explicit "Use when..." trigger clause, leaving the invocation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when the gateway can't send/receive iMessages, the com.joel.imsg-rpc service needs setup or restart, or when troubleshooting FDA/launchd/socket issues."

Spell out "Full Disk Access (FDA)" on first mention so users who say the expanded term still match the description.

Name the concrete debugging surface (e.g. "diagnose permissionDenied and socket ENOENT errors") to round out action coverage.

DimensionReasoningScore

Specificity

"Set up, maintain, and debug" plus "FDA setup, code signing, launchd service, and the imsg source repo" lists several concrete actions with specific coverage areas. Not 5 because coverage is not comprehensive (no troubleshooting/verification actions named); not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

The "what" is clear (set up, maintain, debug the daemon; covers FDA, signing, launchd), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3. Not 2 because the "what" is concrete and specific.

3 / 5

Trigger Term Quality

Natural domain terms users would say are present: "iMessage", "daemon", "JSON-RPC", "launchd", "FDA", "gateway", "imsg". Not 5 because common variations like "Full Disk Access" spelled out or phrasing like "iMessage not working" are missing.

4 / 5

Distinctiveness Conflict Risk

"imsg-rpc Unix socket daemon that gives the gateway iMessage access via JSON-RPC" carves out a clear niche with distinct triggers; no other plausible skill would compete for these terms.

5 / 5

Total

16

/

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/imsg-rpc/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.