Update to RingCentral Phone

{
  "name": "daily-communications-digest",
  "description": "Produces a daily RingEX Phone communications digest from recent calls, SMS, voicemail, contacts, presence, and message-store data. Use when the user asks for a daily digest, morning briefing, catch-up report, missed communications, unresolved calls or texts, voicemail follow-up, or what to work on today.",
  "included_files": [],
  "skill_md_contents": "---\nname: daily-communications-digest\ndescription: Produces a daily RingEX Phone communications digest from recent calls, SMS, voicemail, contacts, presence, and message-store data. Use when the user asks for a daily digest, morning briefing, catch-up report, missed communications, unresolved calls or texts, voicemail follow-up, or what to work on today.\n---\n\n# Daily Communications Digest\n\n## Goal\n\nHelp the user prepare for the day by reviewing personal RingEX Phone communications from the last\n24 hours and turning them into a prioritized action report.\n\nFocus on what needs attention, not on exhaustively listing every record.\n\n## Trigger examples\n\n- \"Give me my daily communications digest.\"\n- \"What did I miss in RingEX over the last 24 hours?\"\n- \"Summarize my calls, texts, and voicemails since yesterday morning.\"\n- \"What communications do I need to follow up on today?\"\n- \"Show me unresolved calls, SMS, and voicemail from the past day.\"\n\n## Workflow\n\n1. Use the past 24 hours by default unless the user gives a different time range.\n2. Call `list_user_call_log` for recent inbound, outbound, and missed calls.\n3. Call `list_message_store_records` with SMS-focused filters for recent text messages.\n4. Call `list_message_store_records` with voicemail-focused filters for recent voicemail records.\n5. Use `read_message_store_record` and `read_message_store_content` when voicemail or message\n   details are needed to understand the action item.\n6. Use `search_directory_entries`, `platform_list_contacts`, `platform_read_contact`,\n   `read_extension_profile`, or `team_messaging_get_person` only when useful to identify people.\n7. Use `read_user_presence` or `platform_read_user_presence_status` only when presence helps decide\n   whether to call, text, or defer.\n8. Summarize patterns across all records before writing the report.\n\n## What to identify\n\n- Missed inbound calls without a later outbound call to the same person or number.\n- Inbound SMS messages without a later user reply.\n- Voicemail that has not clearly been addressed.\n- Repeated contact attempts from the same person or number.\n- Communications that mention urgency, deadlines, blockers, scheduling, customer issues, or needed\n  decisions.\n- Follow-ups that can be batched by person, account, customer, or topic.\n\n## Output format\n\n```md\n# Daily Communications Digest\n\n## Top Priorities\n- [Most important follow-up and why it matters.]\n- [Second most important follow-up.]\n\n## Unreturned Calls\n- [Caller/contact] called at [time]. Action: [call back, text, defer, or no action].\n\n## Unanswered SMS\n- [Contact/number] sent: [brief summary]. Action: [suggested response or next step].\n\n## Voicemail Needing Attention\n- [Caller/contact] left voicemail at [time]. Key point: [summary]. Action: [follow-up].\n\n## Other Notable Activity\n- [Useful context that is not urgent.]\n\n## Suggested Plan\n1. [Highest-priority response or call-back.]\n2. [Next follow-up.]\n3. [Lower-priority cleanup.]\n```\n\n## Guidance\n\n- Be concise, practical, and action-oriented.\n- Avoid dumping raw logs unless the user asks for them.\n- Group related calls, texts, and voicemail from the same person together.\n- State uncertainty when identity matching is unclear.\n- Do not invent message contents, call outcomes, voicemail transcripts, or follow-up status.\n- If tool results are empty, say that no relevant activity was found for the time range.\n\n"
}