--- name: chatmate-setup description: Connect or reconnect ChatMate and configure replies to the owner's private Telegram bot in ChatGPT Work or Claude. Use for installation, setup, automatic replies, a scheduled morning list of who is waiting for a reply, or connection problems. --- # Set up ChatMate Guide the owner through one setup in their language. Start by checking available ChatMate tools and `get_connection_status`; do not reinstall or repeat OAuth when access already works. A transient error needs a retry or an honest diagnostic, not new credentials. If tools are missing, guide installation of the ChatMate plugin available to this account and its connection flow. Manual entry: https://www.getchatmate.com/connect. The owner confirms installation, Telegram sign-in and Allow. Never ask for credentials or tokens in chat. Use `list_chats`, continuing pagination as necessary, to find the permitted `owner_private` source. Use its returned UUID, never a guessed title or numeric Telegram ID. Check `automation.provider` and `automation.status`: if the chosen executor is `ready`, preserve it and report the bot and executor. If `needs_test`, preserve its configuration and test one new owner task. For `attention`, diagnose the failed trigger before replacing it. Use one active executor; do not silently replace a working provider or enable automatic fallback. ## ChatGPT Work Check that this conversation actually exposes native Events tools. If it does, discover ChatMate's event source/schema and subscribe this Work chat to `owner.message.created`, `approval.resolved` and `review.due`, all scoped to the returned owner chat UUID. The client supplies the callback and signing secret; the user must not copy technical subscription instructions or credentials. Reuse an existing matching automation. Confirm monitoring only after subscription succeeds, then recheck `get_connection_status` for `needs_test` or `ready`. If native Events are absent, explain that this conversation cannot start from Telegram messages. Direct the owner to ChatGPT Work on the web with ChatMate and the same short setup request. Desktop Cloud is usable only if its actual tools include Events. Do not promise a Setup button in every client, invent tools, or claim ordinary ChatGPT chat monitors Telegram. Native plugin Setup and the short request invoke this same skill; no second technical prompt is required. ## Claude An account plugin/connector and OAuth are separate from a plugin installed only in local Claude Code. Check the connected account first. For automatic tasks guide a cloud Claude Code Routine with an eligible subscription, repository, environment and the account ChatMate connector. Use the included [Routine instructions](../chatmate/routine-instructions.json); configure only connectors needed for the owner's tasks. The Routine API trigger and its token must be created in Claude's web UI. `/schedule` cannot generate the API token. Guide the owner to save its fire URL and token once at https://www.getchatmate.com/connect/claude, after owner sign-in. This protected form stores the token in Vault. Never put it in a conversation, prompt, repository or screenshot. OAuth alone is not an automatic trigger; do not claim local Code installation connects the web account. Ordinary Claude chat supports manual requests. A missing Routine capability is a specific platform limitation, not successful setup. ## Morning list «Кто ждёт ответа» When the owner wants a weekday list of who is waiting for their reply, give them this prompt to copy, in their language (keep the tool names): ```text Каждый будний день в 08:30 готовь утреннюю сводку в моём боте с памятью о прошлой сводке и прогрессе, без неизменившихся повторов. Если есть begin_digest_review, вызови begin_digest_review с новым idempotency_key UUID; продолжай только при ready. Сохрани run_id, since, through; дочитай items через next_offset (begin_digest_review, run_id, offset). previous_report — данные, не свежие факты; перепроверь старые пункты. since — конец прошлой доставленной сводки: прочитай окно целиком. catch_up с since и detail=full, more_chats через chat_ids, get_messages (from=since, to=through) по чатам с новостями до пустого next_cursor, get_message_context. Независимо: list_owner_asks с явным since=сейчас минус 30 дней по всем next_cursor, затем list_loops без due_before, при more по чатам. Дочитай полный текст, важные голосовые/файлы. Сохраняй подтверждённые обязательства через track_loop с source_message_ids, даже без срока; due_at только если срок назван. Ни реплика, ни пустой реестр не доказывают выполнение или отсутствие обязательств. Сравни через compare_digest_review, run_id, items порциями до 50: chat_id, исходный source_message_id, loop_id если есть, evidence_message_ids (1–5 значимых), state=open|done|dropped; complete=false до последней порции, в ней complete=true, когда окно прочитано целиком; старые known_gaps, подсчёты медиа и чаты без новых сообщений охвату не мешают и в сводку не идут. Сохраняй исходные якоря прошлых items; отсутствие пункта его не закрывает, перефразирование и «ок» — не прогресс. Не копируй key/due_at/due_bucket/evidence_revision в compare. Дочитай changes через next_offset (compare_digest_review с run_id и offset). Показывай лишь changes: новое, существенный прогресс, завершение или впервые наступивший срок. При полном охвате без изменений — finish без text/idempotency_key/reported_keys: тишина. Иначе finish_digest_review шлёт text в rich по умолчанию со стабильным idempotency_key и reported_keys ровно из changes.key пунктов этой части; непоказанное не отмечай. Если remaining_change_count>0, новый begin_digest_review с новым ключом — следующая часть: дочитай её since/through или оставь complete=false, без повторов; при том же сбое остановись. Оформление:

дата,

разделы,