메뉴
Coordinates Incident Management (IcM) and DRI/on-call MCP access for a project. Use when investigating a live or recent incident, checking on-call/DRI status, or deciding whether an incident finding should become a remediation, exception, or documentation update.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
统一错误处理系统。在添加 API 端点、修改错误处理、添加前端 API 调用、编写错误相关测试时使用。
Greeting-triggered self-check — recognise greetings, check Edition version against the upstream tag, scan AI-Memory announcements, and report inside the greeting reply
LLM Agent 多语言注入规范。在修改 Agent 提示词、添加新的 Agent 端点、处理用户可见的后端消息（message_code）时使用。
Coordinates generic project Agency CLI, MCP authorization, M365 consent boundaries, Azure tooling, and Microsoft internal plugin adoption. Use when setting up or auditing Agency profiles, MCP servers, WorkIQ/M365 access, or curated plugins for a project.
Guides on-need adoption of an Agency MCP or Microsoft Foundry capability from the starter's capability catalog. Use when a project asks 'can we use X', 'should we adopt X', or needs to pull a specific tool/profile/Foundry capability without loading the whole surface.
Coordinates Microsoft Fabric MCP access, agents, skills, and curated marketplace plugins for a Fabric-heavy project. Use when setting up or auditing Fabric profiles, notebook-generation plugins, semantic-model review, or Fabric data-security checks.
| name | project-incident-response |
| description | Coordinates Incident Management (IcM) and DRI/on-call MCP access for a project. Use when investigating a live or recent incident, checking on-call/DRI status, or deciding whether an incident finding should become a remediation, exception, or documentation update. |
| lastReviewed | "2026-07-03T00:00:00.000Z" |
Use this skill when a project depends on the Incident Management (icm) or
smart-dri MCPs for incident investigation, on-call/DRI lookup, or incident
follow-up work.
| Request | Default route |
|---|---|
| Live or historical incident lookup, discussion, severity, or ownership | project-incidents (icm) |
| On-call/DRI identification, rotation, or DRI productivity help | project-incidents (smart-dri) |
| Incident finding needs a remediation, exception, or owner-route decision | project-remediation-router for the route, then azure-remediate or service360-breeze only after the route is justified |
| Deployment/security posture context around the incident | project-safety |
| Post-incident status reporting or rollup | project-status-reporter with parent-supplied IcM summary |
| Change/rollout correlation for the incident window | azure-remediate (change-ledger) |
icm as write-capable: it can add discussion, change severity, or
update incident state. Default to read-only investigation; only mutate an
incident with explicit user request and named incident ID.icm/smart-dri as a substitute for security-context,
safefly, or change-ledger investigative context; use those MCPs directly
for posture, deployment, or change-history questions.agency copilot --profile-only project-incidents for narrow
incident tasks so ambient workspace MCP sources are not loaded alongside it.project-remediation-router before escalating to
a write-capable remediation profile or plugin.Run:
agency copilot --profile-only project-incidents --prompt "List MCP servers and exit. Do not call tools."
agency copilot --mcp icm --prompt "Call only a non-mutating capability check such as listing your assigned or recent incidents. Do not update severity, state, or discussion."
agency copilot --mcp smart-dri --prompt "Call only a non-mutating capability check such as looking up current on-call/DRI status. Do not modify rotations or assignments."
Record successful checks in project docs so the next session does not have to re-discover auth state.
Revisit by 2026-09-30. Revise or delete this skill if it fails to prevent an unapproved incident mutation, or if two projects using the starter need a substantially different incident-routing model.