Update to Chiho AI

{
  "description": "Use Chiho's hosted OAuth-protected Telegram MCP for chat inspection, search, CRM organization, follow-up work, automation, and guarded Telegram actions. Trigger when a user wants Claude, Codex, or ChatGPT to work with the Telegram account already connected at chiho.ai without copying a personal access token.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 185
    }
  ],
  "name": "chiho-telegram",
  "skill_md_contents": "---\nname: chiho-telegram\ndescription: Use Chiho's hosted OAuth-protected Telegram MCP for chat inspection, search, CRM organization, follow-up work, automation, and guarded Telegram actions. Trigger when a user wants Claude, Codex, or ChatGPT to work with the Telegram account already connected at chiho.ai without copying a personal access token.\n---\n\n# Chiho Telegram\n\nUse the hosted MCP server at `https://api.chiho.ai/mcp`. Let the client discover OAuth and open the Chiho consent page. Never ask an interactive user to create, paste, or expose a Chiho personal access token.\n\n## Connection workflow\n\n1. Ask the user to connect Telegram at `https://chiho.ai` if they have not already.\n2. Authenticate the `chiho-cloud` MCP connection in the browser.\n3. Let the user review the client identity, redirect host, Chiho account or team, and complete permission set before consenting.\n4. Call `auth_status`, then `account_whoami`, then the narrowest relevant tool.\n5. If the user revokes the connection at `https://chiho.ai/profile/agent-access`, stop and ask them to reconnect through OAuth.\n\nOAuth grants all currently supported Chiho capabilities. Continue to respect the client's write prompts and Chiho's server-side approval requirements.\n\n## Operating rules\n\n- Use the `peer` or `peerRef` returned by `dialogs_list` for chat operations.\n- For a personal connection with missing chat metadata, call `sync_peer` for only the required peer before CRM, summary, or nudge tools.\n- `sync_peer` is unavailable to team-scoped connections. Ask the user to refresh the team's selected chats in Chiho when team metadata is missing.\n- Treat tools that can apply AI suggestions as writes even when they can also preview.\n- Preview tools prepare approval state but do not execute the represented Telegram action.\n- Review recipients and content before sends, users and groups before invites, and groups plus history-clearing choices before leaving.\n- For a guarded Telegram action, create the matching preview, call `write_approve_preview` only after the user reviews it, then call the matching executor (`outbox_send_approved`, `members_invite_approved`, or `groups_leave_approved`). Approval records consent but does not execute the action.\n- Treat logout, group leave, deletes, clears, unlinks, and replacements as destructive.\n- If Telegram authentication is stale, direct the user to Chiho's Telegram connection UI.\n\n## Product boundary\n\nThis package is the hosted Chiho product. It must not launch a local Node process or the self-hosted `tgchats` server. Use the separate `tgchats-local` plugin only when the user explicitly wants to operate their own runtime, database, and Telegram credentials.\n"
}