Handoff

作者 Rootly-AI-Labs65832aa6ff7a無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.

僅含說明DevOps & Cloud Productivity & Workflow

AI 產生的概覽

根據 Rootly 事件與值班資料，產生結構化的事件交接或值班交接文件。

功能: 此技能引導代理為特定事件或值班班次交接產生交接文件。它會依選用的事件 ID 判斷交接類型，透過 Rootly MCP 工具取得事件、告警與值班資料，並將目前狀況、已完成動作、後續步驟、聯絡人、升級路徑、儀表板及即將發生的事項填入 Markdown 範本。產出是一份供接班回應人員或事件指揮官使用的簡明書面交接摘要。
適用情境: 適用於將進行中的事件或值班班次責任移交給其他人或其他團隊時。適合班次交接、事件指揮官交接，以及接班回應人員需要了解目前狀態、後續步驟與升級背景的情境。
執行需求: 需要 Rootly MCP 工具（mcprootly*），以及對相關 Rootly 事件與值班資料的存取權限。此技能僅為指示，不附帶指令碼。模型呼叫已停用，須明確觸發，並接受一個選用的事件 ID 參數。

Incident & On-Call Handoff

You are preparing a handoff document for either incident response or on-call shift transitions.

Workflow

1. Determine Handoff Type

If $ARGUMENTS contains an incident ID:

Incident Handoff: Create handoff for specific incident
Call mcp__rootly__getIncident with the provided ID
Call mcp__rootly__listIncidentAlerts for associated alerts

If no incident ID provided:

On-Call Handoff: Create general shift handoff
Call mcp__rootly__get_oncall_handoff_summary or relevant on-call endpoints
Call mcp__rootly__search_incidents filtered to recent active incidents

2. Generate Incident Handoff

For incident-specific handoffs:

markdown

# Incident Handoff: [incident-title]
**Handoff Time**: [current-time]  **Incident ID**: [short-id]  **Severity**: [severity]  **Current Status**: [status]  **Started**: [started-at] ([duration] ago)
## Current Situation[Brief summary of what's happening now]
## What's Been Done- [action 1]- [action 2]- [action 3]
## Immediate Next Steps1. [priority action]2. [next action]3. [monitoring action]
## Key Contacts- **Incident Commander**: [if assigned]- **On-Call**: [current on-call person]- **Escalation Path**: [relevant escalation details]
## Important Notes[Any critical context, gotchas, or special considerations]
## Monitoring- [key dashboards/alerts to watch]- [specific metrics to monitor]

# Incident Handoff: [incident-title]
**Handoff Time**: [current-time]  **Incident ID**: [short-id]  **Severity**: [severity]  **Current Status**: [status]  **Started**: [started-at] ([duration] ago)
## Current Situation[Brief summary of what's happening now]
## What's Been Done- [action 1]- [action 2]- [action 3]
## Immediate Next Steps1. [priority action]2. [next action]3. [monitoring action]
## Key Contacts- **Incident Commander**: [if assigned]- **On-Call**: [current on-call person]- **Escalation Path**: [relevant escalation details]
## Important Notes[Any critical context, gotchas, or special considerations]
## Monitoring- [key dashboards/alerts to watch]- [specific metrics to monitor]

3. Generate On-Call Handoff

For general on-call handoffs:

markdown

# On-Call Handoff
**Handoff Time**: [current-time]  **Previous On-Call**: [if determinable]  **Incoming On-Call**: [current/next on-call]
## Active Incidents[List current active incidents with brief status]
## Recent Activity (Last 24h)- [incident summaries]- [any resolved issues]
## Ongoing Concerns- [items requiring monitoring]- [scheduled maintenance]- [known issues]
## Escalation Paths[Current escalation contacts and procedures]
## Key Dashboards[Important monitoring dashboards to check]
## Upcoming Events[Deployments, maintenance, or other scheduled activities]

# On-Call Handoff
**Handoff Time**: [current-time]  **Previous On-Call**: [if determinable]  **Incoming On-Call**: [current/next on-call]
## Active Incidents[List current active incidents with brief status]
## Recent Activity (Last 24h)- [incident summaries]- [any resolved issues]
## Ongoing Concerns- [items requiring monitoring]- [scheduled maintenance]- [known issues]
## Escalation Paths[Current escalation contacts and procedures]
## Key Dashboards[Important monitoring dashboards to check]
## Upcoming Events[Deployments, maintenance, or other scheduled activities]

4. Formatting Notes

Keep handoffs concise but comprehensive
Include actionable next steps
Highlight any time-sensitive items
Provide context for complex situations
Include relevant links/IDs for quick access

來源與署名

來源：Rootly-AI-Labs/rootly-claude-plugin位於skills/handoff提交65832aa

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Handoff

Incident & On-Call Handoff

Workflow

1. Determine Handoff Type

2. Generate Incident Handoff

3. Generate On-Call Handoff

4. Formatting Notes

來源與署名

更多來自 Rootly-AI-Labs/rootly-claude-plugin 的技能

Trend

Test

Swap

Status

Retro

Respond

更多DevOps & Cloud技能

M5 Onboard

Runbook

Incident Response

Deploy Checklist

Spanner Basics

Secops Cases