{"id":65269,"plugin_id":"plugin_asdk_app_6a5163accce48191ab3fac53d63cb197","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-27T06:06:45.423Z","digest":"e77b70158d08ccc60aae8f6dc1fb5d4226d090bc7a1b3e5cfe3bbd199350f423","against":null,"payload":{"description":"Presents the authenticated RingEX Phone user's fax inbox as a clickable list of recent faxes, then reads back the selected fax's sender, time, and cover-page text when available. Excludes SMS and voicemail, and cannot retrieve the fax document body itself. Use when the user asks to see their faxes, check for a new fax, or find out who sent a fax.","included_files":[],"name":"fax-inbox","skill_md_contents":"---\nname: fax-inbox\ndescription: Presents the authenticated RingEX Phone user's fax inbox as a clickable list of recent faxes, then reads back the selected fax's sender, time, and cover-page text when available. Excludes SMS and voicemail, and cannot retrieve the fax document body itself. Use when the user asks to see their faxes, check for a new fax, or find out who sent a fax.\n---\n\n# Fax Inbox\n\n## Goal\n\nGive the user a browsable view of recent faxes — who sent one, when, and any cover-page text —\nwithout making them dig through a phone app. This skill has a hard limitation worth stating\nup front: no tool on this server can retrieve or OCR the actual fax document content, only\nmetadata and cover-page text. Be upfront about that rather than implying more access than exists.\n\n## Trigger examples\n\n- \"Do I have any new faxes?\"\n- \"Show me my fax inbox.\"\n- \"Who sent that fax this morning?\"\n- \"Any faxes from this week I haven't seen?\"\n\n## Scope boundary\n\n- Fax only. Never include SMS or voicemail records, even if the user says \"messages\" generically —\n  if they explicitly ask for SMS or voicemail, say this skill doesn't cover that and point to\n  `sms-inbox` or `voicemail-inbox` instead of quietly including it.\n- Read-only. This skill never deletes, marks read/unread, or forwards a fax — there is no tool\n  exposed on this server for those actions.\n- **Cannot read the fax document itself.** `get_my_message_detail` never returns attachment ids,\n  URIs, or binary/base64 content, and `get_my_communication_inbox`'s `keyword` filter only matches\n  fax cover-page text — it does not search the fax PDF/OCR content. If the user wants the actual\n  document contents, say plainly that this skill only surfaces metadata and cover-page text, and\n  suggest they open the fax directly in the RingCentral app or online account.\n\n## Workflow\n\n1. **Pull recent fax activity.** Call `get_my_communication_inbox` with `messageTypes: [\"Fax\"]`\n   (SMS and voicemail are separate `messageTypes` values and must not be requested). Default the\n   window to the last 14 days unless the user asks for a different range, and pass\n   `readStatus: \"Unread\"` only if the user specifically asked for unread/new faxes.\n\n2. **Resolve sender names.** For each fax's sender number, try `search_my_contacts` (personal\n   address book) then `resolve_directory_person` (company directory); fall back to the raw phone\n   number if neither resolves.\n\n3. **Sort and present as a choice.** Sort newest first.\n      - If there are 2–4 recent faxes, use a structured multiple-choice control, when the client\n        provides one: one option per fax, labeled with the resolved\n        sender name, with the timestamp (and page count, if the record includes one) as the\n        description.\n      - If there are more than 4, or fewer than 2 (zero or one), list them as a plain-text ranked\n        list instead — a multiple-choice prompt can't show more than 4 options, and a single fax\n        doesn't need a picker at all (just confirm and proceed to step 4).\n      - If nothing was found in the window, say so and offer to check a wider date range instead of\n        guessing at prior activity.\n\n4. **Fetch the selected fax's detail.** Take the `messageId` of the chosen fax and call\n   `get_my_message_detail`. This returns metadata and, if the fax had one, cover-page text — never\n   the document's page images, PDF, or OCR'd body text.\n\n5. **Render the result.** Show the sender (resolved name or raw number), the timestamp, and the\n   cover-page text if present. If there's no cover-page text, say so plainly, and remind the user\n   this skill can't surface the fax's actual document content — that requires opening it directly\n   in RingCentral.\n\n## Guidance\n\n- Never invent a fax's sender, timestamp, or cover-page text — if a field is missing, say it's\n  unavailable.\n- Never imply the fax document itself was read, summarized, or searched — only metadata and\n  cover-page text are ever available through this skill.\n- Never fold SMS or voicemail into this view.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}