Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
imsg - Skill - OpenSmartRoute
Skillv1.0.0
imsg
iMessage/SMS CLI for listing chats, history, watch, and sending.
Imported from sundial-org/awesome-openclaw-skills (skills/imsg/SKILL.md). Install upstream with npx skills add sundial-org/awesome-openclaw-skills --skill imsg. Copyright stays with the author.
imsg
Use imsg to read and send Messages.app iMessage/SMS on macOS.
Requirements
Messages.app signed in
Full Disk Access for your terminal
Automation permission to control Messages.app (for sending)
Common commands
List chats: imsg chats --limit 10 --json
History: imsg history --chat-id 1 --limit 20 --attachments --json
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install imsg and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
