Update to Resolve AI

{
  "name": "alerts",
  "description": "List and filter alerts in Resolve. Use when the user asks \"show me alerts\", \"any new alerts\", \"alerts on <team>\", \"find the alert matching <pattern>\", \"alerts that auto-investigated\", \"alerts where <label> is critical/missing\", or wants a focused alerts view (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: alerts\ndescription: List and filter alerts in Resolve. Use when the user asks \"show me alerts\", \"any new alerts\", \"alerts on <team>\", \"find the alert matching <pattern>\", \"alerts that auto-investigated\", \"alerts where <label> is critical/missing\", or wants a focused alerts view (separate from a full overview snapshot).\nversion: 0.1.0\nargument-hint: <optional filter description>\nlicense: Apache-2.0\n---\n\n# List Resolve Alerts\n\nUse for focused alert listings and alert drill-downs.\n\n## Arguments\n\nIf `$ARGUMENTS` is non-empty, translate it into `list_alerts` filters.\n\nIf `$ARGUMENTS` is empty, call `list_alerts` with the tool defaults. Only ask the user to narrow if the result set is overwhelming.\n\n## Filter Intent\n\nMap common phrasings to the right filter family:\n\n- **Time** — \"today\", \"last week\", \"since deploy\", explicit date ranges.\n- **Ownership** — team, alert rule, alert ID, or entity.\n- **Investigation state** — auto-investigated alerts, alerts with or without linked investigations.\n- **Labels** — severity, service, environment, team, missing labels, or substring matches.\n\nExamples:\n\n- \"critical alerts in the last hour\" → time filter + severity label.\n- \"alerts where `service` is missing\" → missing-label filter.\n- \"alerts containing 'timeout'\" → substring label filter on the best matching message/description label.\n- \"alerts for High CPU rule\" → rule key if known, otherwise filter by rule/title labels.\n\nFor unsupported inverse filters, fetch a reasonable recent set and post-filter locally.\n\n## Output\n\nSummarize compactly:\n\n- Count + the time range covered.\n- Severity / action breakdown when it's informative.\n- Per-alert one-liner: `time`, `title`, `severity`, `action`, `is_auto_investigated`, `entity_key`.\n- Surface investigation links only when the result includes an `investigation_id`; never fabricate one.\n- Preserve any `[label](path)` citations verbatim.\n\nIf the list is long, group by `alert_rule_key` or a salient label and offer to narrow further.\n\n## Handoffs\n\n- \"Show me everything happening in Resolve\" — broader than just alerts → `resolve-ai:overview`.\n- \"Open the investigation for this alert\" — use the alert's `investigation_id` directly → `resolve-ai:investigate <investigation_id>`.\n- \"Tell Resolve about this alert\" — promote a finding into that investigation → `resolve-ai:steer`.\n"
}