Update to Resolve AI

{
  "name": "chats",
  "description": "List recent Resolve chats. Use when the user asks \"show me my chats\", \"what chats are in flight\", \"any chats running\", \"chats from last week\", or wants a focused chat list (separate from a full overview snapshot).",
  "included_files": [],
  "skill_md_contents": "---\n# Copyright 2026 Resolve AI, Inc.\n# SPDX-License-Identifier: Apache-2.0\nname: chats\ndescription: List recent Resolve chats. Use when the user asks \"show me my chats\", \"what chats are in flight\", \"any chats running\", \"chats from last week\", or wants a focused chat list (separate from a full overview snapshot).\nversion: 0.1.0\nargument-hint: <optional time range, e.g. \"last 7 days\">\nlicense: Apache-2.0\n---\n\n# List Resolve Chats\n\nWraps `list_chats`.\n\n## Arguments\n\nIf `$ARGUMENTS` is non-empty, parse it into filter intent. Empty → call with defaults.\n\n`list_chats` has no server-side `status` filter. When the user asks for \"running\" / \"in flight\" / \"errored\", fetch and post-filter on `status`.\n\n## Output\n\n- Count + time range covered.\n- Status breakdown when informative; surface `running` first — the agent is still working.\n- Per-chat one-liner: `name`, `status`, `updated_at`, canvas URL (`<your-resolve-host>/chat/<chat_id>`).\n- Preserve `[label](path)` citations verbatim.\n\n## Handoffs\n\n- Read what Resolve said on a chat → `get_chat` with the `chat_id`.\n- Send a new message in a chat → `resolve-ai:ask` with the `chat_id`.\n- Investigations view → `resolve-ai:investigations`.\n- Alerts view → `resolve-ai:alerts`.\n"
}