Update to Kenso

{
  "description": "Review a member's Today queue - what needs them now, grouped by kind and urgency - then draft, rewrite, grade, snooze or skip the touches they flag, clear rows they are done with, and hand every approval back to them.",
  "included_files": [],
  "name": "today-review",
  "skill_md_contents": "---\nname: today-review\ndescription: Review a member's Today queue - what needs them now, grouped by kind and urgency - then draft, rewrite, grade, snooze or skip the touches they flag, clear rows they are done with, and hand every approval back to them.\n---\n\n# Today review\n\nToday in Kenso is one member's queue for the day: touches waiting for approval or failed, tasks due, meetings, replies waiting, signals, new leads, paused account plans and setup steps. The member sees it at `https://app.ken.so/<workspace id>/today`.\n\nTrigger on \"what needs me today?\", \"clear my queue\", \"go through my Today\", or the start of a member's day.\n\nToday, touches, approvals and the questions Kenso asks have no tool in this app: you cannot read the queue, or draft, approve, snooze, skip or clear a row here. What you can do: read the parts of the day the tools here reach (replies waiting, today's calendar and meetings, notifications), write, rewrite and grade a touch the member pastes, and send them to Today for every action on a row.\n\n## The rule: the member approves every send\n\nYou draft, rewrite and grade. The member approves, edits, snoozes, skips and clears, in Today. Never say a touch was sent or approved because you wrote it.\n\n- A touch with a body waits as `awaiting_approval` until the person clicks Approve in Today. Say it waits for their approval, and when it is due.\n- Retrying a failed send is the member's Retry in Today too.\n- Every write in this skill happens only on the member's request, one row at a time unless they ask for a batch.\n\nEvery tool here takes `workspace_id`. Send it on every call when the user can see more than one workspace (`list_workspaces()` lists them).\n\n## Step 0 - Check what is on\n\nToday and touches are in beta, on per workspace. The tools here reach these parts of the day:\n\n| Part | Tools |\n|---|---|\n| Replies waiting | `get_inbox_counts()`, `list_inbox_threads()` |\n| Today's calendar | `list_calendar_events()` |\n| Recorded meetings and their notes | `list_meetings()` |\n| Notifications | `list_my_notifications()` |\n| Grading a touch the member pastes | `grade_email_copy()`, `check_email_copy()` |\n\n- If https://app.ken.so/<workspace id>/today shows no queue for the member, Today is not on for this workspace: say so in one sentence, and work only the parts above.\n- A part whose tool is missing or refuses: skip it, say which, and carry on.\n\n## Step 1 - Read Today\n\nAsk the member's time zone first, or say the day is UTC. Never guess a zone from a name or a company. Then read:\n\n- `get_inbox_counts(tab=\"to_reply\")`: replies waiting, with the unread and to-reply badges.\n- `list_inbox_threads(tab=\"to_reply\", sort=\"oldest_waiting\", limit=10)`: the replies that waited longest, each with `waitingSince` and its `interest`.\n- `list_calendar_events(from_time=\"2026-10-31T00:00:00Z\", to_time=\"2026-11-01T00:00:00Z\")`: today's calendar, from the member's midnight to the next.\n- `list_meetings(from_time=\"2026-10-30T00:00:00Z\", to_time=\"2026-11-01T00:00:00Z\")`: meetings recorded since yesterday, to spot one that ended with no notes.\n- `list_my_notifications()`: the member's unread notifications.\n\nThe rest of Today (touches waiting for approval or failed, tasks, calls, opportunities, new leads, account plans, signals, setup steps and questions) is only in the app. When the member wants help with it, ask them to open https://app.ken.so/<workspace id>/today and tell you or paste what is there.\n\n## Step 2 - Group and present\n\nOpen with one line: how many replies wait, the next meeting, and how many notifications are unread. Then the groups that have rows, most urgent first:\n\n| Group | From | What the member does |\n|---|---|---|\n| Replies waiting | `to_reply` threads | answer them (the `reply-handling` skill) |\n| Meetings | today's calendar and recent recorded meetings | prep (the `meeting-prep-and-followup` skill), or add notes |\n| Notifications | unread notifications | open each in Kenso |\n| The rest of Today | what the member tells you from https://app.ken.so/<workspace id>/today | approve, edit, snooze or skip touches, do tasks and calls, resume or end plans, finish setup steps, all in Today |\n\n- Give each group a count and its top 3 rows with title, person or account, and due time. Ask which ones to work; do not walk the whole list unasked.\n- A reply thread whose `interest` is `out_of_office` is not a reply and nobody is waiting on it: list it apart, and never count it in \"replies waiting\". Count replies by distinct person.\n- Never report opens.\n\n## Step 3 - Work the touches the member flags\n\nThe member pastes the touch from Today: its channel (email, LinkedIn connect or message, call), the person and account, why it is planned, and its text, or says it has no text yet.\n\n| The member wants | Do |\n|---|---|\n| it written | write a draft from what the member tells you about the person, the account and the reason for the touch. Ask for any fact you lack |\n| it shorter, warmer, more specific, or in their voice | rewrite it and show the result |\n| a grade | `grade_email_copy(subject_key=\"touch-9001\", copy=\"...\", channel=\"email\")`: a score and what to improve. Use `channel=\"linkedin_connection\"` or `\"linkedin_message\"` for LinkedIn. For an email, `check_email_copy(subject=\"...\", body=\"...\")` also checks it against the copy rules in code |\n| their edit saved | they open the row in Today, click Edit, replace the text with the version they accepted and save it. The touch then waits for their approval |\n\n- Show the full text, and let the member choose what goes into Today.\n- Never invent a price, a meeting time, a discount or an offer. When the touch needs one the member has not given, leave it out and ask.\n- Name only an event (funding, a hire, a launch) that the account's signals or research state, as the member reports them: Today will not save a touch that names one with no source.\n- Funding is not a buying event by itself. Do not make a round the reason for the message unless the account's research ties it to a need the member's offer meets.\n- A structural change to the message (new angle, new offer, new call to action) is a new draft the member reviews from scratch, not a small edit.\n- A grade answers 429 `quota_exceeded` past 20 a minute or 500 a day: wait and grade again later.\n\n## Step 4 - Snooze, skip and clear\n\nSnoozing, skipping and clearing happen in Today: a touch waiting for approval has Approve, Edit and Skip, a failed send has Retry and Skip, and other rows have Snooze and Done.\n\n- A snooze that breaks a Contact limits rule is refused.\n- Some rows change more than the queue. Say so before the member clears them:\n  - `done` on a reply row archives the thread, marks it read and clears its reminder: it leaves To Reply.\n  - `done` on a `merge_suggestion` row means \"not a duplicate\" for the whole workspace, and needs Accounts edit.\n  - `done` on an opportunity, new lead, merge suggestion, meeting notes or signal row dismisses it for good.\n- Undoing a snooze, a skip or an approval is the member's own button in Today.\n\n## Step 5 - Questions waiting for an answer\n\nThe questions Kenso asks the member have no tool here. They answer them in the app or in Slack, with a button or a reply. Do not pick an option for them.\n\n## Step 6 - Hand the approvals back\n\nLink Today: https://app.ken.so/<workspace id>/today. Everything that waits on the member (touches, replies, calendar changes, LinkedIn notes, agent proposals and campaign batches) is approved there, by their own click.\n\nReport back: what waits for the member (by group, with counts), each draft or rewrite you gave them, and what still needs them in Today.\n\n## What this skill cannot do yet\n\n- Read Today, or draft, approve, retry, snooze, skip or clear a row: Today and touches have no tool here.\n- Answer a question Kenso asked: that stays with the person, on purpose.\n- Act on a reply, a meeting or an account plan from here: use the `reply-handling`, `meeting-prep-and-followup` and `accounts` skills.\n\n"
}