菜单
Send Resolve your feedback — on an investigation's root cause, a chat answer, or the Resolve experience itself. Use when you've resolved or mitigated your issue, an investigation or chat wraps up, or you want to rate or comment on Resolve.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Edit a Resolve satellite's Helm values.yaml — add or modify integrations on the satellite, configure networking, set environment variables. Use when the user mentions editing satellite config — phrases like "edit satellite values.yaml", "add Tempo to my satellite", "configure satellite networking", "satellite chart values", "satellite helm config", or "wire up a satellite integration".
Send Resolve a question or a request to investigate — continuing an existing chat or investigation, or starting a fresh one. Use when the user wants to send a message to Resolve — phrases like "ask Resolve about X", "follow up with Resolve", "what does Resolve think about Y", "have Resolve check Z", or wants Resolve to clarify a finding.
Run a guided, self-paced tour of Resolve using the connected org's live data — surface the environment, resume a chat, fire several in parallel, drill a real RCA with its evidence and a live thread, then investigate something from scratch. Use when someone wants to demo Resolve, give a tour, or show a new user what it can do — phrases like "demo Resolve", "give me a tour", "walk them through Resolve", "show me what Resolve can do", "demo this to <person>".
Write or tune a skill for the Resolve plugin — encoding workflow guidance, not tool API details.
Run a guided, self-paced tour of Resolve using the connected org's live data — surface the environment, resume a chat, fire several in parallel, drill a real RCA with its evidence and a live thread, then investigate something from scratch. Use when someone wants to demo Resolve, give a tour, or show a new user what it can do — phrases like "demo Resolve", "give me a tour", "walk them through Resolve", "show me what Resolve can do", "demo this to <person>".
Run a guided, self-paced tour of Resolve using the connected org's live data — surface the environment, resume a chat, fire several in parallel, drill a real RCA with its evidence and a live thread, then investigate something from scratch. Use when someone wants to demo Resolve, give a tour, or show a new user what it can do — phrases like "demo Resolve", "give me a tour", "walk them through Resolve", "show me what Resolve can do", "demo this to <person>".
| name | feedback |
| description | Send Resolve your feedback — on an investigation's root cause, a chat answer, or the Resolve experience itself. Use when you've resolved or mitigated your issue, an investigation or chat wraps up, or you want to rate or comment on Resolve. |
| version | 0.1.0 |
| argument-hint | <optional feedback text> |
| license | Apache-2.0 |
Wraps submit_feedback. Engage when work wraps up — the user fixed or mitigated the issue, or an investigation or chat concluded — or whenever they explicitly want to rate or comment on Resolve. Offer once; if they pass, drop it.
Route to what they're judging: an investigation's root cause, a chat answer, or the product / MCP experience itself. If their intent spans more than one, send a separate call per target. Use only IDs returned by Resolve tools.
Two parts, handled differently:
$ARGUMENTS is non-empty, use it as the note.So: with session context, draft the note and ask only for the verdict in one turn. With none, ask briefly what they want to say and what it's about. Then submit, and tell the user in one line what you sent and where.