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 well-crafted description with strong specificity and highly distinctive terminology that clearly identifies its niche. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The technical terms are appropriate and would naturally match user queries about this specific system.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about imsg-rpc setup, iMessage daemon issues, launchd configuration for imsg, or code signing problems related to the iMessage gateway.'
| 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 specific subtopics), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'imsg-rpc', 'Unix socket daemon', 'iMessage', 'JSON-RPC', 'FDA setup', 'code signing', 'launchd service', 'imsg'. These are specific technical terms a user working with this system would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with very specific niche terms like 'imsg-rpc', 'iMessage access via JSON-RPC', 'launchd service', and 'FDA setup'. Extremely unlikely to conflict with other skills. | 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 operational skill that provides precise, actionable guidance for managing a specific launchd service. Its strengths are concrete executable commands, clear architecture context, and thorough troubleshooting with diagnostic queries. The only minor weakness is that the content is moderately long and could benefit from splitting the FDA setup or protocol reference into separate files for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place — architecture diagram, concrete paths, executable commands, and troubleshooting steps all convey non-obvious, project-specific information. No padding or explanation of concepts Claude already knows. | 3 / 3 |
Actionability | Fully executable commands throughout: status checks, restart sequences, build commands, FDA certificate creation, TCC database queries, and JSON-RPC examples are all copy-paste ready with specific paths and flags. | 3 / 3 |
Workflow Clarity | The FDA setup is clearly sequenced (1-4) with verification at each stage. Troubleshooting section provides explicit diagnostic commands with expected outputs and decision trees (auth_value 2 vs 0). The rebuild workflow has a clear validation step (tail logs for 'watch.subscribe OK'). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a summary files table, but it's a fairly long single file. The JSON-RPC protocol reference and the full certificate creation script could potentially be split into referenced files. However, without bundle files, this is a reasonable single-file approach for the complexity level. | 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
03f0a59
- 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.