inkbox-ai

Use when the user asks to send an iMessage, reply on iMessage, or explain how to reach the agent over iMessage — also use automatically when an inbound `imessage.received` event arrives from Inkbox. Handles the connect/router model, the recipient-first rule, and tapback reactions.

Use when an inbound email arrives at the agent's Inkbox mailbox or when the user asks the agent to send/reply to email. Hermes can send and reply from current inbound context, but does not expose mailbox queue/read/forward/archive tools.

Use when the user asks to send a text, reply to an SMS, or process the SMS queue — also use automatically when an inbound `text.received` event arrives from Inkbox. Handles per-conversation context, opt-in/opt-out gates, and the 10DLC carrier propagation window.

Use when the user asks the agent to place an outbound Inkbox phone call, call a phone number/contact, or call someone with a specific purpose or opening message.

Use when adding support for verifying a new inbound-webhook source (a third-party service that will POST signed events to this agent's /webhook endpoint), or when asked how the plugin decides whether an incoming webhook is authentic. Explains the webhook_providers registry and how to onboard a new provider.

Use when the user asks about Inkbox calls, call transcripts, missed calls, or follow-up work. Hermes can use current live/post-call context, but does not expose historical call-read tools.

Use when the user asks "who is X", "what's the email for Y", "find a contact named Z", "save this contact", or any question that needs contact context. Hermes can read and write Inkbox contacts visible to this identity, but does not expose contact admin tools.

Use when the user wants to block, allow, pause, delete, or list Inkbox contact-rule filters for the agent's mailbox or phone number. Hermes does not expose contact-rule edit tools; guide the user to Inkbox Console or explain the limitation.

Use when the user asks who can reach the agent's Inkbox mailbox, phone number, or shared iMessage line — viewing email/SMS/call/iMessage allow and block rules, checking why a sender was filtered, or handling a request to block or allow someone.

Use when the user asks "who is X", "what's the email for Y", "find a contact named Z", "save this contact", or any request that needs contact context. The agent can read and write Inkbox contacts visible to the configured identity; contact access grants, contact rules, and vCard flows are separate surfaces.

Use when the user asks the agent to "log into X", "get the API key for Y", "fetch the SSH key for Z", or "give me the TOTP code for service A". Covers the credential vault path through the Inkbox plugin. Always list-then-get; never enumerate plaintext.

Use when the user asks the agent to triage its Inkbox inbox or unread queue, or to reply to, forward, or send mail on its Inkbox identity. Does not cover the human owner's personal email.

Use when the user asks which Inkbox agent identities can see a contact or note, or asks to grant/revoke cross-identity access to contacts or notes.

Use when the user asks to send an iMessage, reply to or triage the agent's iMessage conversations, or explain how to reach the agent over iMessage. Covers the connect/router model, the recipient-first rule, and tapback reactions.

Use when the user asks to save, remember, list, retrieve, update, or delete notes in Inkbox. This is for persistent Inkbox notes, not workspace-local memory.

Use when the user asks the agent to place an outbound Inkbox phone call, call a phone number, or call a contact by voice.

Use when an inbound email arrives at the agent's Inkbox mailbox, when the user asks the agent to triage its Inkbox inbox or unread queue, or when the user asks the agent to reply/forward/archive mail on its Inkbox identity. Does not cover the human owner's personal email.

Use when the user asks to send an iMessage, reply on iMessage, or explain how to reach the agent over iMessage — also use automatically when an inbound `imessage.received` event arrives from Inkbox. Handles the connect/router model, the recipient-first rule, and tapback reactions.

Use when the user asks the agent to place an outbound Inkbox phone call, call a phone number/contact, or call someone with a specific purpose or opening message.

Use when the user asks to send a text, reply to an SMS, or process the SMS queue — also use automatically when an inbound `text.received` event arrives from Inkbox. Handles per-conversation context, opt-in/opt-out gates, and the 10DLC carrier propagation window.

Use when the user asks "who is X", "what's the email for Y", "find a contact named Z", "save this contact", or any question that needs contact context. OpenClaw can read and write Inkbox contacts visible to this identity, but contact access/rules and vCard flows are separate admin surfaces.

Use when the user asks to save, remember, list, retrieve, update, or delete notes in Inkbox. This is for persistent Inkbox notes, not workspace-local memory.

Use when the user asks to review recent Inkbox calls, inspect missed calls, fetch call transcripts, summarize a past call, or prepare follow-up work based on call history.

Use when the user wants to block, allow, pause, delete, or list Inkbox contact-rule filters for the agent's mailbox or phone number, including email allow/block rules, SMS/call allow/block rules, allowlists, blocklists, spam blocking, or "only accept from" requests.

Use when writing Python code that imports from `inkbox`, uses `pip install inkbox`, or when adding email, phone, text/SMS, iMessage, contacts, notes, contact rules, vault, tunnels, mailbox storage, mail clients (IMAP/SMTP), or agent identity features using the Inkbox Python SDK.

Use when writing TypeScript or JavaScript code that imports from `@inkbox/sdk`, uses `npm install @inkbox/sdk`, or when adding email, phone, text/SMS, iMessage, contacts, notes, contact rules, vault, tunnels, mailbox storage, mail clients (IMAP/SMTP), or agent identity features using the Inkbox TypeScript SDK.

Use when running or writing shell commands with the Inkbox CLI (`inkbox` / `@inkbox/cli`) for identities, email, phone, text/SMS, iMessage, contacts, notes, contact rules, vault, mailbox, mailbox storage, mail clients (IMAP/SMTP), phone number, webhook, or signup workflows.

Index of all Inkbox skills in this repository, including the example skills under `examples/`, with GitHub links and short guidance on when to use each one.

Use when bringing a local server online behind a public Inkbox URL via `inkbox.tunnels.connect(...)` — covers edge vs passthrough TLS, URL forwarding, and in-process Fetch/ASGI/WebSocket handlers in both Python and TypeScript SDKs.

Use when guiding or implementing the Inkbox agent self-signup flow, including verification, resend-verification, signup restrictions, and optional signup fields like agent handles or mailbox local parts.

System prompt for an AI agent with Browser Use browser automation and Inkbox email. Drop this into your agent loop to get browser automation and email tools out of the box.

System prompt for an AI agent with a Kernel cloud browser and Inkbox email. Drop this into your agent loop to get browser automation and email tools out of the box.

Use for WHOOP questions and every verified WHOOP workout, sleep, or recovery webhook. Fetches official WHOOP data and decides whether to contact the configured human through Inkbox.

Render WHOOP sleep, workout, and daily report cards.

Direct iPhone control via Appium/XCUITest. Use when the user wants to automate, inspect, or interact with a real iPhone tethered via USB.