Update to Zime

{
  "description": "Gives you your day at a glance. Today's meetings, what changed on your deals, and what needs attention now.",
  "included_files": [],
  "name": "daily-briefing",
  "skill_md_contents": "---\nname: daily-briefing\ndescription: \"Gives you your day at a glance. Today's meetings, what changed on your deals, and what needs attention now.\"\nlicense: MIT\nmetadata:\n  zime:skill-id: aa4d7a1f-2f3c-4c5d-be5f-6d7cec6f6816\n  zime:tag: workflow\n  zime:roles: ae,bdr\n  zime:visibility: global\n  zime:skill-version: \"1\"\n  zime:marketplace-version: 0.1.20\n---\n\n# Daily Briefing\n\nBefore anything else, call the Zime connector tool `skill_used` with skill_id `aa4d7a1f-2f3c-4c5d-be5f-6d7cec6f6816`, skill_version `1` and skill_slug `daily-briefing`. It records which skill ran for Zime usage analytics. If the Zime connector is not available, skip this step and continue.\n\nAnswers \"what do I need to know this morning?\" — the day's meetings, what\nmoved on the deals, and what's about to slip. It's the skill a rep runs\nbefore their first call, so the briefing stays short.\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                      DAILY BRIEFING                              │\n├─────────────────────────────────────────────────────────────────┤\n│  NO ENTITY RESOLVE                                               │\n│  ✓ Scope is the rep's whole day — nothing to pin                 │\n├─────────────────────────────────────────────────────────────────┤\n│  OPTIONAL — CONCRETE SCHEDULE                                    │\n│  ✓ list_meetings for today's actual meetings, with times         │\n├─────────────────────────────────────────────────────────────────┤\n│  DELEGATE (Zime agent)                                           │\n│  + ask_zime for what changed and what needs attention            │\n│  + Kept short — this runs before the first call                  │\n├─────────────────────────────────────────────────────────────────┤\n│  LOCAL FALLBACK (no zime-mcp)                                    │\n│  ~ Read a calendar or CRM export the user provides               │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## Usage\n\n```\n@daily-briefing [today | this week | date]\n```\n\nIn the ChatGPT desktop app you can also type `/daily-briefing`.\n\nBrief the user for the day or window they asked for, defaulting to today.\n\n## Routing\n\n- Prep for ONE specific upcoming call → `call-prep`. This skill lists the\n  day; that one prepares you for a meeting.\n- Full pipeline health across many deals, or one deal in depth →\n  `review-account`.\n- Everything outstanding regardless of today → `actions-commitments`.\n\n## What I Need From You\n\nNothing. Default to today. Accept \"this week\" or a specific date if given.\n\n## MCP mode (required when zime-mcp is connected)\n\n**Required tool:** `ask_zime`. **Recommended:** `list_meetings` for the\nschedule.\n\nAssembling the briefing from memory or from deals mentioned earlier in the\nchat is a failure of this skill — the point is what changed since the rep last\nlooked, which by definition isn't in the conversation.\n\n### Step 1 (optional) — the actual schedule\n\nFor a concrete list of today's meetings with times, call `list_meetings` with\ntoday's date on both ends:\n\n```json\n{ \"query\": \"\", \"start_date\": \"2026-08-13\", \"end_date\": \"2026-08-13\" }\n```\n\nThis returns both scheduled meetings and recorded calls for the day. Use it\nwhen the rep wants times and attendees; skip it if they only asked what\nchanged.\n\n### Step 2 — delegate the briefing\n\n```json\n{ \"question\": \"Brief me for today: what meetings do I have, what changed on my deals since yesterday, and what needs my attention today. Include the specific deal or account behind each item.\" }\n```\n\n`ask_zime` has no memory of this conversation and no date parameters — put the\nday in the question text. Ask for the deal or account behind each item, or you\nget a list of alerts with nothing to act on.\n\n### Outcomes\n\n- **A briefing** — deliver per Output below.\n- **A quiet day** — \"nothing changed and you have no meetings\" is a valid,\n  useful answer. Don't manufacture items to fill it out.\n- **An error** — `{\"error\": \"<CODE>\", \"message\": \"<sentence>\"}`. Show the\n  user the message. `INTERNAL_ERROR` retry once; `TIMEOUT` narrow the window\n  and retry; `CREDIT_LIMIT` stop and relay the message; `UNAUTHORIZED` /\n  `FORBIDDEN` means reconnect or lack of access. If it fails twice, say so\n  and offer the local fallback. If only `list_meetings` succeeded, deliver\n  the schedule alone and say the change summary was unavailable — a partial\n  briefing labelled as partial is fine.\n\n## Output\n\nSchedule first (a rep reads this between calls), then what changed.\n\n```markdown\n**Briefing — [date]**\n\n### Today's meetings\n| Time | Meeting | Account | Prep |\n|---|---|---|---|\n| [time] | [title] | [account] | [prepped / not prepped] |\n\n### What changed\n[the agent's returned summary, relayed as-is]\n\n### Needs attention today\n[the agent's returned items, relayed as-is]\n\n_Live calendar, CRM, and call data via Zime._\n```\n\nRules:\n\n- Relay the agent's sections **as-is** — don't re-prioritize what needs\n  attention. Ordering is judgment, and reordering it silently overrides that.\n- Keep the account or deal name on every item. An alert without an entity\n  isn't actionable.\n- Keep times exactly as returned, and say which timezone if the tool states\n  one. A briefing with a shifted time is worse than no briefing.\n- If a section came back empty, show it empty. A short honest briefing beats a\n  padded one.\n- Don't fold in items from earlier in the conversation.\n\n## Tips\n\n1. **Run it before your first call** — that's the design point.\n2. **\"This week\" works** — say so in the request and it goes into the question.\n3. **Not prepped?** Chain into `call-prep` for the meeting that matters most.\n4. **Wanting depth, not speed?** That's `review-account`.\n\n## Local mode (only when no zime-mcp server is connected)\n\nIf the user provides a calendar or CRM export, list the day's meetings and\nflag deals with past-due close dates or missing next steps from that file.\nOpen with one line saying the briefing covers only the provided file — so\n\"what changed\" isn't available, since a static export has no change history.\nDon't infer change from a snapshot.\n\n## What this sends where\n\nMCP mode sends a date range and empty query (to `list_meetings`) and the\nquestion text (to `ask_zime`). Local mode reads only the provided file.\nAt the start, the skill calls the Zime connector tool `skill_used`, which\nrecords the skill's id, version and name with your user and session in\nZime's usage log.\n\n## Related Skills\n\n- **call-prep** — prepare for the meeting this briefing surfaced\n- **review-account** — the deeper pipeline or single-deal view\n- **actions-commitments** — everything open, not just today\n"
}