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

Spanner Basics

Secops Cases

Managed Airflow Migrations

Managed Airflow Dag Troubleshooting

Iam Helper For Privileged Access Management