Update to OpenWhispr

{
  "description": "Review a week, or any date range, of the user's OpenWhispr notes and meetings, covering what happened, the decisions made and the action items and loose ends still open, grouped by folder, and optionally save the review back to OpenWhispr as a note. Use this for \"weekly review\", \"what did I get done this week?\", \"summarize my meetings since Monday\", \"end-of-week recap\", \"what's still open from last week's calls?\", monthly look-backs, or a Friday review routine. It looks back over what was captured. It is not for planning the week ahead from scratch, unless the user wants last week's open items carried forward.",
  "included_files": [],
  "name": "weekly-review",
  "skill_md_contents": "---\nname: weekly-review\ndescription: Review a week, or any date range, of the user's OpenWhispr notes and meetings, covering what happened, the decisions made and the action items and loose ends still open, grouped by folder, and optionally save the review back to OpenWhispr as a note. Use this for \"weekly review\", \"what did I get done this week?\", \"summarize my meetings since Monday\", \"end-of-week recap\", \"what's still open from last week's calls?\", monthly look-backs, or a Friday review routine. It looks back over what was captured. It is not for planning the week ahead from scratch, unless the user wants last week's open items carried forward.\nargument-hint: \"[date range, e.g. 'last week' or '1–15 Nov']\"\n---\n\n# Weekly review\n\nTurn a stretch of the user's OpenWhispr notes and meetings into a short review they can act on: what happened, what was decided, and what is still open.\n\nThe OpenWhispr connector provides the tools used here (`list_notes`, `list_folders`, `get_note_transcript`, `create_note`, `create_folder`). If they aren't available, ask the user to connect OpenWhispr in their assistant's plugin or connection settings. Complete sign-in through the secure connection flow; never ask for a password, login code or API key in the conversation.\n\n## 1. Settle the window\n\nUse the user's range if they give one. Otherwise:\n\n- **\"This week\":** Monday to today.\n- **\"Last week\":** the previous Monday to Sunday.\n- **No range given:** the last 7 days.\n\nTimestamps are in UTC. Use the user's local dates if you know their timezone. State the window at the top of the review, so a wrong guess is easy to spot.\n\n## 2. Collect the notes\n\n1. Call `list_folders` once and map folder IDs to names.\n2. Page through `list_notes` with `limit` 20, passing `cursor` from each response. Notes come back newest first by creation date. Stop when a page reaches notes created before the window starts, or when `has_more` is false. Keep the page size small, because each item carries the full note text and transcript.\n3. Keep the notes created inside the window. Notes created earlier but edited this week fall outside a creation-date scan. If the user wants those too, include any note whose `updated_at` is in the window and say so.\n4. Skip empty notes, ones with no content and no transcript, which are often \"Untitled\" leftovers. Mention how many you skipped.\n\nFor each note, read the best available text:\n\n- `enhanced_content`, the AI notes, when present;\n- otherwise `content`;\n- for meetings with neither, the `transcript` already in the list item. Call `get_note_transcript` only if that's missing.\n\nIn transcripts, `source: \"mic\"` is the user and `source: \"system\"` is the other people on the call. Ignore one-word fragments and background chatter.\n\n## 3. Write the review\n\nKeep it scannable. One line per item, real names and dates, nothing invented. If an owner or due date wasn't stated, write \"owner not stated\" rather than guessing.\n\n```markdown\n# Week of 3–9 Nov 2026\n\n## Highlights\n- 3–5 bullets: the most important outcomes of the week\n\n## Meetings\n- Mon 3 Nov — *Design standup*: agreed the Q1 priorities\n- …\n\n## Decisions\n- …\n\n## Open action items\n- [ ] Owner — task — due date (from *note title*)\n\n## Loose ends\n- Questions raised but not answered, and things promised without a date\n\n## By folder\n- Work (4 notes), Clients (2), Ideas (3)\n```\n\nFor a big window, more than about 40 notes, summarize folder by folder and keep **Highlights** to the top five. Say if anything was left out.\n\n## 4. Offer to save it\n\nShow the review first, then offer to save it as a note titled like \"Weekly review — 3–9 Nov 2026\":\n\n- **Where:** the folder the user names. Otherwise use a \"Weekly reviews\" folder if one exists, or failing that their default **Personal** folder, and mention they can ask for a dedicated \"Weekly reviews\" folder (create it with `create_folder` only when they say yes).\n- **How:** call `create_note` with a `title`, always (the desktop app can't import a note without one, and its syncing stalls), the review as `content`, and the folder's `folder_id`. Use the default `note_type`. The app shows notes in a Markdown editor: keep to `##`/`###` headings, bullets and `- [ ]` checkboxes, with a blank line between paragraphs.\n- **Once saved:** confirm the title and folder. Don't paste the API response.\n\nSave without asking only when the user already asked for it (\"…and save it to my notes\"). Save once: a note created through the connector doesn't update cleanly in the desktop app yet, so if the user wants changes, finish them in the chat before saving. Never edit or delete the notes being reviewed.\n"
}