메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
| name | inkbox-contact-rules |
| description | 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 this skill when the user asks about who can reach the agent's Inkbox mailbox, phone number, or shared iMessage line.
inkbox_list_mail_contact_rules — email allow/block rulesinkbox_list_phone_contact_rules — SMS + voice allow/block rulesinkbox_list_imessage_contact_rules — shared iMessage line allow/block rulesThe API is read-only for agents by design: an agent-scoped key can VIEW its contact rules but never create, change, or delete them. Rule changes are made by a human in the Inkbox console (https://inkbox.ai/console/contact-rules).
action: "block" rejects matching traffic, action: "allow"
permits it when a whitelist posture is active, status: "paused" means
the rule exists but is not enforced.exact_email or domain; phone and iMessage
rules use exact_number (E.164, e.g. +15551234567). Phone rules apply
to both SMS and voice on the dedicated number.