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.
91
87%
Does it follow best practices?
Impact
100%
5.55xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
82%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, specific description that clearly identifies a narrow technical domain (imsg-rpc daemon for iMessage) with concrete actions and relevant technical keywords. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The specificity and distinctiveness are excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about imsg-rpc, iMessage daemon setup, launchd service configuration for iMessage, or troubleshooting the Unix socket connection.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Set up, maintain, and debug' the daemon, and covers specific subtopics: 'FDA setup, code signing, launchd service, and the imsg source repo.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' (set up, maintain, debug the imsg-rpc daemon with FDA, code signing, launchd, source repo), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes highly specific natural keywords a user would mention: 'imsg-rpc', 'Unix socket daemon', 'iMessage', 'JSON-RPC', 'FDA', 'code signing', 'launchd', 'imsg'. These are domain-specific terms that would naturally appear in user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely specific niche — 'imsg-rpc Unix socket daemon' for iMessage access is highly distinctive and unlikely to conflict with any other skill. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, operationally-focused skill that provides excellent actionable guidance for managing the imsg-rpc daemon. It excels at conciseness and actionability — every section delivers concrete, executable commands without unnecessary explanation. The only minor weakness is that the document is somewhat long and could benefit from splitting the FDA setup and protocol reference into separate files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. No unnecessary explanations of what launchd, FDA, or Unix sockets are. Every section provides actionable information without padding. The architecture diagram is minimal but informative. | 3 / 3 |
Actionability | Fully executable commands throughout — from status checks, to certificate creation, to build steps, to troubleshooting queries. All commands are copy-paste ready with concrete paths and flags. The troubleshooting section provides specific diagnostic commands with expected outputs. | 3 / 3 |
Workflow Clarity | The FDA setup is clearly sequenced (1-4) with verification at each critical step. Troubleshooting flows include diagnostic commands followed by conditional remediation steps. The rebuild workflow explicitly warns against using `make build` and explains why. Validation checkpoints like 'should show watch.subscribe OK' are present. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a files reference table, but it's a fairly long single document (~150 lines of substantive content). The JSON-RPC protocol reference and the full certificate creation script could potentially be split into referenced files. However, the ADR reference and file table provide good navigation. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
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.