Skip to content
Back to skills

Source 6fc41d87363a9c98296a1fa0

ASecurity

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

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
devopsgo

Works with

  • mcp

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add gutsofpratik/OpenClaude-Skills --skill source-6fc41d87363a9c98296a1fa0 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Source 6fc41d87363a9c98296a1fa0?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Source 6fc41d87363a9c98296a1fa0
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gutsofpratik-source-6fc41d87363a9c98296a1fa0/badge)](https://www.skillsdirectory.com/skills/gutsofpratik-source-6fc41d87363a9c98296a1fa0)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff
description: Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.
argument-hint: [incident-id]
disable-model-invocation: true
allowed-tools:
  - mcp__rootly__*
---

# 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 Steps
1. [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]
```

### 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

Files in this skill

  • PROVENANCE.json221 B
  • SKILL.md2.5 KB
  • UPSTREAM-LICENSE.txt10.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.