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.
86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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%
Without context: $0.3436 · 1m 45s · 14 turns · 19 in / 6,874 out tokens
With context: $0.4846 · 2m 3s · 18 turns · 274 in / 8,084 out tokens
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%
Without context: $0.3922 · 1m 55s · 19 turns · 25 in / 6,371 out tokens
With context: $0.4746 · 1m 51s · 22 turns · 26 in / 5,937 out tokens
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%
Without context: $0.3584 · 2m 5s · 12 turns · 19 in / 7,721 out tokens
With context: $0.3741 · 1m 57s · 15 turns · 20 in / 6,807 out tokens
Table of Contents
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.