Update to Solibo Home

{
  "description": "Work through the conversations (henvendelser, meldinger) of a housing community in Solibo Home: how many are open, which need an answer first, what a thread says, replying, internal notes, moving threads to folders, closing, reopening or flagging many at once. Use when the user asks about unanswered or open conversations, their inbox for a company, what residents are writing about, or wants to answer, file or close conversations.",
  "included_files": [
    {
      "relative_path": "references/tool-notes.md",
      "size_in_bytes": 4999
    }
  ],
  "name": "conversation-triage",
  "skill_md_contents": "---\nname: conversation-triage\ndescription: \"Work through the conversations (henvendelser, meldinger) of a housing community in Solibo Home: how many are open, which need an answer first, what a thread says, replying, internal notes, moving threads to folders, closing, reopening or flagging many at once. Use when the user asks about unanswered or open conversations, their inbox for a company, what residents are writing about, or wants to answer, file or close conversations.\"\n---\n\n# Conversation triage\n\nCount first, read a sample second, open full threads last, and change many conversations with one bulk\ntool and one confirmation.\n\n## Counts and sample\n\n1. Resolve the company (`search_companies`) and, for a session about one company, `set_working_company`.\n2. `get_conversation_meta` gives exact counts: `counts.new`, `counts.inProgress`, `counts.done`,\n   `counts.draft` (`counts.total` includes trashed threads). It also lists `folders[]` and `categories[]`,\n   the source of every `folderId` and `categoryId`. \"Open\" means NEW plus IN_PROGRESS; read or unread is a\n   separate signal (`readByCurrentUser`).\n3. `search_conversations` for the list. `status` takes one value per call, so open threads are two calls,\n   NEW and then IN_PROGRESS (DONE is an alias of COMPLETE; omitting `status` includes TRASHED). Add\n   `search` for words, `createdSince` (a bare date is the\n   start of that Oslo day), `folderId`, `categoryIds`, `count` (default 25). Follow `paging.next` only as\n   far as the question needs; do not page through thousands of threads to answer \"what is going on\".\n4. Across all of the user's companies, `get_my_conversations` groups by company; pass `unread` true for\n   new mail and keep the same value while paging.\n\n## Reading a thread\n\n- `get_conversation` with `companyId` and `conversationId` returns the newest messages (oldest first, up to\n  `messageLimit`, default 20) with each message cut to 100 characters, plus `status`, `folderId`,\n  `categoryId`, `relatedIssueIds` and `participants`. This is enough to say what a thread is about and\n  who wrote last.\n- Open a few threads, not all of them. For \"summarise every conversation this month\", summarise from titles\n  and the truncated previews and offer to read selected threads in full.\n- `reveal_conversation_full_content` returns full message text and is logged as personal-data access. Use\n  it only when the user asks for the content of a named thread, or asks you to answer it; one thread per\n  call, never as a loop over a list.\n- Contact fields appear only when asked for (`includeFields`).\n\n## Answering\n\n- `reply_to_conversation` writes a message the resident sees; `content` is required, documents go in\n  `attachments`, `inlineDocuments` or `files`. It is a preview; after the user approves the text, call\n  `confirm_pending_communication` with `previewId` and `confirmed` true. There is no draft or\n  scheduling for replies: confirming sends the message to the resident at once, and an unconfirmed preview is\n  temporary and saved nowhere, so make clear which of the two the user is choosing.\n- `create_internal_note` is visible to staff and board only; `documentIds` may name existing documents.\n  Confirm with `confirm_pending_write`.\n- New threads: `create_conversation` with `title` and `participants` (each `participantId` from\n  `search_persons`, `search_residents` or `search_organizations`, with `participantType`); or\n  `create_conversation_inquiry` with a `categoryId` from the meta call. Both confirm through\n  `confirm_pending_communication`. A DRAFT thread becomes visible with `publish_conversation`.\n- `update_conversation_details` changes `title` or `categoryId`; its `content` only while the thread is\n  DRAFT. `update_conversation` sets `status` DONE or IN_PROGRESS for one thread.\n\n## Changing many threads at once\n\nUse the bulk tools with `conversationIds` (up to 100 per call) and one confirmation, never a loop of\nsingle-thread calls:\n\n| Intent | Tool | Extra argument |\n|---|---|---|\n| File threads in a folder | `move_conversations_to_folder` | `folderId`, or `topLevel` true |\n| Mark read or unread | `mark_conversations_read` | `read` true or false |\n| Flag or unflag | `flag_conversations` | `flagged` |\n| Close, reopen | `close_conversations`, `reopen_conversations` | none |\n| Trash, restore | `trash_conversations`, `restore_conversations` | none |\n\n`move_conversation_to_folder` and `mark_conversation_read` exist for a single thread; with two or more\nids use the bulk tool. `delete_conversations` is a soft delete; prefer trash when the user may want the\nthreads back. A new folder comes from `create_conversation_folder` (`name`, optional `parentId`).\n\nEach bulk call returns a preview listing the ids and the action. Show the count and the folder or status,\nget the user's approval, then `confirm_pending_write` with `previewId` and `confirmed` true. A result whose\n`pendingAction.status` is DRY_RUN changed nothing.\n\n## Answer shape\n\nCounts first (new, in progress, done), then the threads that need a reply with title, started date and who\nwrote last, then the suggested action per thread. Say when the list is a sample and when a thread was\nsummarised from truncated previews.\n\n`references/tool-notes.md` lists the arguments and result fields of every tool named here.\n"
}