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
Evaluation results
100%
85%iMessage Gateway Channel Implementation
JSON-RPC socket client protocol
Correct socket path
0%
100%
JSON-RPC version
0%
100%
Subscribe method name
0%
100%
Subscribe participants param
0%
100%
Send method name
100%
100%
Send to param
0%
100%
Send text param
100%
100%
Inbound notification method
0%
100%
Notification subscription field
0%
100%
Notification message field
0%
100%
100%
95%New Developer Machine Setup for iMessage Bridge
FDA setup and local code signing
Uses build-local.sh
0%
100%
No make build
100%
100%
Cert identity name
0%
100%
PKCS12 legacy cipher flags
0%
100%
PKCS12 macalg flag
0%
100%
PKCS12 password
0%
100%
FDA targets app bundle
0%
100%
Launchd plist path
0%
100%
Source repo path
0%
100%
Service name
0%
100%
100%
65%On-Call Runbook: iMessage Bridge Service
Service operations and troubleshooting runbook
Status check command
0%
100%
Healthy state definition
50%
100%
Restart procedure
0%
100%
Socket-missing kickstart fix
66%
100%
Kickstart service target
0%
100%
TCC.db FDA check
100%
100%
TCC auth_value interpretation
100%
100%
Log file paths
0%
100%
Error log for crash diagnosis
0%
100%
Post-rebuild FDA fix
0%
100%
- Repository
- joelhooks/joelclaw
- Commit
825972c
- Evaluated
- Agent
- Claude Code
- Model
- Claude Sonnet 4.6
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.