[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70K58K0DS39WB8DC7HGD5KS":3,"skill-same:01M70K58K0DS39WB8DC7HGD5KS":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M70K58K0DS39WB8DC7HGD5KS","on-call-handoff-patterns",null,"Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fwshobson-agents\u002Fplugins\u002Fincident-response\u002Fskills\u002Fon-call-handoff-patterns\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"on call handoff patterns","patterns","handoff","call","when","documentation","master","context","escalation","use","context transfer","with","summaries","processes","transfer","2026-11-10 10:12:30",false,"---\nname: on-call-handoff-patterns\ndescription: Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use when transitioning on-call responsibilities, documenting shift summaries, or improving on-call processes.\n---\n\n# On-Call Handoff Patterns\n\nEffective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.\n\n## When to Use This Skill\n\n- Transitioning on-call responsibilities\n- Writing shift handoff summaries\n- Documenting ongoing investigations\n- Establishing on-call rotation procedures\n- Improving handoff quality\n- Onboarding new on-call engineers\n\n## Core Concepts\n\n### 1. Handoff Components\n\n| Component | Purpose |\n|-----------|---------|\n| **Active Incidents** | What's currently broken |\n| **Ongoing Investigations** | Issues being debugged |\n| **Recent Changes** | Deployments, configs |\n| **Known Issues** | Workarounds in place |\n| **Upcoming Events** | Maintenance, releases |\n\n### 2. Handoff Timing\n\n```\nRecommended: 30 min overlap between shifts\n\nOutgoing:\n├── 15 min: Write handoff document\n└── 15 min: Sync call with incoming\n\nIncoming:\n├── 15 min: Review handoff document\n├── 15 min: Sync call with outgoing\n└── 5 min: Verify alerting setup\n```\n\n## Templates\n\n### Template 1: Shift Handoff Document\n\n```markdown\n# On-Call Handoff: Platform Team\n\n**Outgoing**: @alice (2024-01-15 to 2024-01-22)\n**Incoming**: @bob (2024-01-22 to 2024-01-29)\n**Handoff Time**: 2024-01-22 09:00 UTC\n\n---\n\n## 🔴 Active Incidents\n\n### None currently active\nNo active incidents at handoff time.\n\n---\n\n## 🟡 Ongoing Investigations\n\n### 1. Intermittent API Timeouts (ENG-1234)\n**Status**: Investigating\n**Started**: 2024-01-20\n**Impact**: ~0.1% of requests timing out\n\n**Context**:\n- Timeouts correlate with database backup window (02:00-03:00 UTC)\n- Suspect backup process causing lock contention\n- Added extra logging in PR #567 (deployed 01\u002F21)\n\n**Next Steps**:\n- [ ] Review new logs after tonight's backup\n- [ ] Consider moving backup window if confirmed\n\n**Resources**:\n- Dashboard: [API Latency](https:\u002F\u002Fgrafana\u002Fd\u002Fapi-latency)\n- Thread: #platform-eng (01\u002F20, 14:32)\n\n---\n\n### 2. Memory Growth in Auth Service (ENG-1235)\n**Status**: Monitoring\n**Started**: 2024-01-18\n**Impact**: None yet (proactive)\n\n**Context**:\n- Memory usage growing ~5% per day\n- No memory leak found in profiling\n- Suspect connection pool not releasing properly\n\n**Next Steps**:\n- [ ] Review heap dump from 01\u002F21\n- [ ] Consider restart if usage > 80%\n\n**Resources**:\n- Dashboard: [Auth Service Memory](https:\u002F\u002Fgrafana\u002Fd\u002Fauth-memory)\n- Analysis doc: [Memory Investigation](https:\u002F\u002Fdocs\u002Feng-1235)\n\n---\n\n## 🟢 Resolved This Shift\n\n### Payment Service Outage (2024-01-19)\n- **Duration**: 23 minutes\n- **Root Cause**: Database connection exhaustion\n- **Resolution**: Rolled back v2.3.4, increased pool size\n- **Postmortem**: [POSTMORTEM-89](https:\u002F\u002Fdocs\u002Fpostmortem-89)\n- **Follow-up tickets**: ENG-1230, ENG-1231\n\n---\n\n## 📋 Recent Changes\n\n### Deployments\n| Service | Version | Time | Notes |\n|---------|---------|------|-------|\n| api-gateway | v3.2.1 | 01\u002F21 14:00 | Bug fix for header parsing |\n| user-service | v2.8.0 | 01\u002F20 10:00 | New profile features |\n| auth-service | v4.1.2 | 01\u002F19 16:00 | Security patch |\n\n### Configuration Changes\n- 01\u002F21: Increased API rate limit from 1000 to 1500 RPS\n- 01\u002F20: Updated database connection pool max from 50 to 75\n\n### Infrastructure\n- 01\u002F20: Added 2 nodes to Kubernetes cluster\n- 01\u002F19: Upgraded Redis from 6.2 to 7.0\n\n---\n\n## ⚠️ Known Issues & Workarounds\n\n### 1. Slow Dashboard Loading\n**Issue**: Grafana dashboards slow on Monday mornings\n**Workaround**: Wait 5 min after 08:00 UTC for cache warm-up\n**Ticket**: OPS-456 (P3)\n\n### 2. Flaky Integration Test\n**Issue**: `test_payment_flow` fails intermittently in CI\n**Workaround**: Re-run failed job (usually passes on retry)\n**Ticket**: ENG-1200 (P2)\n\n---\n\n## 📅 Upcoming Events\n\n| Date | Event | Impact | Contact |\n|------|-------|--------|---------|\n| 01\u002F23 02:00 | Database maintenance | 5 min read-only | @dba-team |\n| 01\u002F24 14:00 | Major release v5.0 | Monitor closely | @release-team |\n| 01\u002F25 | Marketing campaign | 2x traffic expected | @platform |\n\n---\n\n## 📞 Escalation Reminders\n\n| Issue Type | First Escalation | Second Escalation |\n|------------|------------------|-------------------|\n| Payment issues | @payments-oncall | @payments-manager |\n| Auth issues | @auth-oncall | @security-team |\n| Database issues | @dba-team | @infra-manager |\n| Unknown\u002Fsevere | @engineering-manager | @vp-engineering |\n\n---\n\n## 🔧 Quick Reference\n\n### Common Commands\n```bash\n# Check service health\nkubectl get pods -A | grep -v Running\n\n# Recent deployments\nkubectl get events --sort-by='.lastTimestamp' | tail -20\n\n# Database connections\npsql -c \"SELECT count(*) FROM pg_stat_activity;\"\n\n# Clear cache (emergency only)\nredis-cli FLUSHDB\n```\n\n### Important Links\n- [Runbooks](https:\u002F\u002Fwiki\u002Frunbooks)\n- [Service Catalog](https:\u002F\u002Fwiki\u002Fservices)\n- [Incident Slack](https:\u002F\u002Fslack.com\u002Fincidents)\n- [PagerDuty](https:\u002F\u002Fpagerduty.com\u002Fschedules)\n\n---\n\n## Handoff Checklist\n\n### Outgoing Engineer\n- [x] Document active incidents\n- [x] Document ongoing investigations\n- [x] List recent changes\n- [x] Note known issues\n- [x] Add upcoming events\n- [x] Sync with incoming engineer\n\n### Incoming Engineer\n- [ ] Read this document\n- [ ] Join sync call\n- [ ] Verify PagerDuty is routing to you\n- [ ] Verify Slack notifications working\n- [ ] Check VPN\u002Faccess working\n- [ ] Review critical dashboards\n```\n\n### Template 2: Quick Handoff (Async)\n\n```markdown\n# Quick Handoff: @alice → @bob\n\n## TL;DR\n- No active incidents\n- 1 investigation ongoing (API timeouts, see ENG-1234)\n- Major release tomorrow (01\u002F24) - be ready for issues\n\n## Watch List\n1. API latency around 02:00-03:00 UTC (backup window)\n2. Auth service memory (restart if > 80%)\n\n## Recent\n- Deployed api-gateway v3.2.1 yesterday (stable)\n- Increased rate limits to 1500 RPS\n\n## Coming Up\n- 01\u002F23 02:00 - DB maintenance (5 min read-only)\n- 01\u002F24 14:00 - v5.0 release\n\n## Questions?\nI'll be available on Slack until 17:00 today.\n```\n\n### Template 3: Incident Handoff (Mid-Incident)\n\n```markdown\n# INCIDENT HANDOFF: Payment Service Degradation\n\n**Incident Start**: 2024-01-22 08:15 UTC\n**Current Status**: Mitigating\n**Severity**: SEV2\n\n---\n\n## Current State\n- Error rate: 15% (down from 40%)\n- Mitigation in progress: scaling up pods\n- ETA to resolution: ~30 min\n\n## What We Know\n1. Root cause: Memory pressure on payment-service pods\n2. Triggered by: Unusual traffic spike (3x normal)\n3. Contributing: Inefficient query in checkout flow\n\n## What We've Done\n- Scaled payment-service from 5 → 15 pods\n- Enabled rate limiting on checkout endpoint\n- Disabled non-critical features\n\n## What Needs to Happen\n1. Monitor error rate - should reach \u003C1% in ~15 min\n2. If not improving, escalate to @payments-manager\n3. Once stable, begin root cause investigation\n\n## Key People\n- Incident Commander: @alice (handing off)\n- Comms Lead: @charlie\n- Technical Lead: @bob (incoming)\n\n## Communication\n- Status page: Updated at 08:45\n- Customer support: Notified\n- Exec team: Aware\n\n## Resources\n- Incident channel: #inc-20240122-payment\n- Dashboard: [Payment Service](https:\u002F\u002Fgrafana\u002Fd\u002Fpayments)\n- Runbook: [Payment Degradation](https:\u002F\u002Fwiki\u002Frunbooks\u002Fpayments)\n\n---\n\n**Incoming on-call (@bob) - Please confirm you have:**\n- [ ] Joined #inc-20240122-payment\n- [ ] Access to dashboards\n- [ ] Understand current state\n- [ ] Know escalation path\n```\n\n## Handoff Sync Meeting\n\n### Agenda (15 minutes)\n\n```markdown\n## Handoff Sync: @alice → @bob\n\n1. **Active Issues** (5 min)\n   - Walk through any ongoing incidents\n   - Discuss investigation status\n   - Transfer context and theories\n\n2. **Recent Changes** (3 min)\n   - Deployments to watch\n   - Config changes\n   - Known regressions\n\n3. **Upcoming Events** (3 min)\n   - Maintenance windows\n   - Expected traffic changes\n   - Releases planned\n\n4. **Questions** (4 min)\n   - Clarify anything unclear\n   - Confirm access and alerting\n   - Exchange contact info\n```\n\n## On-Call Best Practices\n\n### Before Your Shift\n\n```markdown\n## Pre-Shift Checklist\n\n### Access Verification\n- [ ] VPN working\n- [ ] kubectl access to all clusters\n- [ ] Database read access\n- [ ] Log aggregator access (Splunk\u002FDatadog)\n- [ ] PagerDuty app installed and logged in\n\n### Alerting Setup\n- [ ] PagerDuty schedule shows you as primary\n- [ ] Phone notifications enabled\n- [ ] Slack notifications for incident channels\n- [ ] Test alert received and acknowledged\n\n### Knowledge Refresh\n- [ ] Review recent incidents (past 2 weeks)\n- [ ] Check service changelog\n- [ ] Skim critical runbooks\n- [ ] Know escalation contacts\n\n### Environment Ready\n- [ ] Laptop charged and accessible\n- [ ] Phone charged\n- [ ] Quiet space available for calls\n- [ ] Secondary contact identified (if traveling)\n```\n\n### During Your Shift\n\n```markdown\n## Daily On-Call Routine\n\n### Morning (start of day)\n- [ ] Check overnight alerts\n- [ ] Review dashboards for anomalies\n- [ ] Check for any P0\u002FP1 tickets created\n- [ ] Skim incident channels for context\n\n### Throughout Day\n- [ ] Respond to alerts within SLA\n- [ ] Document investigation progress\n- [ ] Update team on significant issues\n- [ ] Triage incoming pages\n\n### End of Day\n- [ ] Hand off any active issues\n- [ ] Update investigation docs\n- [ ] Note anything for next shift\n```\n\n### After Your Shift\n\n```markdown\n## Post-Shift Checklist\n\n- [ ] Complete handoff document\n- [ ] Sync with incoming on-call\n- [ ] Verify PagerDuty routing changed\n- [ ] Close\u002Fupdate investigation tickets\n- [ ] File postmortems for any incidents\n- [ ] Take time off if shift was stressful\n```\n\n## Escalation Guidelines\n\n### When to Escalate\n\n```markdown\n## Escalation Triggers\n\n### Immediate Escalation\n- SEV1 incident declared\n- Data breach suspected\n- Unable to diagnose within 30 min\n- Customer or legal escalation received\n\n### Consider Escalation\n- Issue spans multiple teams\n- Requires expertise you don't have\n- Business impact exceeds threshold\n- You're uncertain about next steps\n\n### How to Escalate\n1. Page the appropriate escalation path\n2. Provide brief context in Slack\n3. Stay engaged until escalation acknowledges\n4. Hand off cleanly, don't just disappear\n```\n\n## Best Practices\n\n### Do's\n- **Document everything** - Future you will thank you\n- **Escalate early** - Better safe than sorry\n- **Take breaks** - Alert fatigue is real\n- **Keep handoffs synchronous** - Async loses context\n- **Test your setup** - Before incidents, not during\n\n### Don'ts\n- **Don't skip handoffs** - Context loss causes incidents\n- **Don't hero** - Escalate when needed\n- **Don't ignore alerts** - Even if they seem minor\n- **Don't work sick** - Swap shifts instead\n- **Don't disappear** - Stay reachable during shift\n\n## Resources\n\n- [Google SRE - Being On-Call](https:\u002F\u002Fsre.google\u002Fsre-book\u002Fbeing-on-call\u002F)\n- [PagerDuty On-Call Guide](https:\u002F\u002Fwww.pagerduty.com\u002Fresources\u002Flearn\u002Fon-call-management\u002F)\n- [Increment On-Call Issue](https:\u002F\u002Fincrement.com\u002Fon-call\u002F)\n","# On-Call Handoff Patterns\n\nEffective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.\n\n## When to Use This Skill\n\n- Transitioning on-call responsibilities\n- Writing shift handoff summaries\n- Documenting ongoing investigations\n- Establishing on-call rotation procedures\n- Improving handoff quality\n- Onboarding new on-call engineers\n\n## Core Concepts\n\n### 1. Handoff Components\n\n| Component | Purpose |\n|-----------|---------|\n| **Active Incidents** | What's currently broken |\n| **Ongoing Investigations** | Issues being debugged |\n| **Recent Changes** | Deployments, configs |\n| **Known Issues** | Workarounds in place |\n| **Upcoming Events** | Maintenance, releases |\n\n### 2. Handoff Timing\n\n```\nRecommended: 30 min overlap between shifts\n\nOutgoing:\n├── 15 min: Write handoff document\n└── 15 min: Sync call with incoming\n\nIncoming:\n├── 15 min: Review handoff document\n├── 15 min: Sync call with outgoing\n└── 5 min: Verify alerting setup\n```\n\n## Templates\n\n### Template 1: Shift Handoff Document\n\n```markdown\n# On-Call Handoff: Platform Team\n\n**Outgoing**: @alice (2024-01-15 to 2024-01-22)\n**Incoming**: @bob (2024-01-22 to 2024-01-29)\n**Handoff Time**: 2024-01-22 09:00 UTC\n\n---\n\n## 🔴 Active Incidents\n\n### None currently active\nNo active incidents at handoff time.\n\n---\n\n## 🟡 Ongoing Investigations\n\n### 1. Intermittent API Timeouts (ENG-1234)\n**Status**: Investigating\n**Started**: 2024-01-20\n**Impact**: ~0.1% of requests timing out\n\n**Context**:\n- Timeouts correlate with database backup window (02:00-03:00 UTC)\n- Suspect backup process causing lock contention\n- Added extra logging in PR #567 (deployed 01\u002F21)\n\n**Next Steps**:\n- [ ] Review new logs after tonight's backup\n- [ ] Consider moving backup window if confirmed\n\n**Resources**:\n- Dashboard: [API Latency](https:\u002F\u002Fgrafana\u002Fd\u002Fapi-latency)\n- Thread: #platform-eng (01\u002F20, 14:32)\n\n---\n\n### 2. Memory Growth in Auth Service (ENG-1235)\n**Status**: Monitoring\n**Started**: 2024-01-18\n**Impact**: None yet (proactive)\n\n**Context**:\n- Memory usage growing ~5% per day\n- No memory leak found in profiling\n- Suspect connection pool not releasing properly\n\n**Next Steps**:\n- [ ] Review heap dump from 01\u002F21\n- [ ] Consider restart if usage > 80%\n\n**Resources**:\n- Dashboard: [Auth Service Memory](https:\u002F\u002Fgrafana\u002Fd\u002Fauth-memory)\n- Analysis doc: [Memory Investigation](https:\u002F\u002Fdocs\u002Feng-1235)\n\n---\n\n## 🟢 Resolved This Shift\n\n### Payment Service Outage (2024-01-19)\n- **Duration**: 23 minutes\n- **Root Cause**: Database connection exhaustion\n- **Resolution**: Rolled back v2.3.4, increased pool size\n- **Postmortem**: [POSTMORTEM-89](https:\u002F\u002Fdocs\u002Fpostmortem-89)\n- **Follow-up tickets**: ENG-1230, ENG-1231\n\n---\n\n## 📋 Recent Changes\n\n### Deployments\n| Service | Version | Time | Notes |\n|---------|---------|------|-------|\n| api-gateway | v3.2.1 | 01\u002F21 14:00 | Bug fix for header parsing |\n| user-service | v2.8.0 | 01\u002F20 10:00 | New profile features |\n| auth-service | v4.1.2 | 01\u002F19 16:00 | Security patch |\n\n### Configuration Changes\n- 01\u002F21: Increased API rate limit from 1000 to 1500 RPS\n- 01\u002F20: Updated database connection pool max from 50 to 75\n\n### Infrastructure\n- 01\u002F20: Added 2 nodes to Kubernetes cluster\n- 01\u002F19: Upgraded Redis from 6.2 to 7.0\n\n---\n\n## ⚠️ Known Issues & Workarounds\n\n### 1. Slow Dashboard Loading\n**Issue**: Grafana dashboards slow on Monday mornings\n**Workaround**: Wait 5 min after 08:00 UTC for cache warm-up\n**Ticket**: OPS-456 (P3)\n\n### 2. Flaky Integration Test\n**Issue**: `test_payment_flow` fails intermittently in CI\n**Workaround**: Re-run failed job (usually passes on retry)\n**Ticket**: ENG-1200 (P2)\n\n---\n\n## 📅 Upcoming Events\n\n| Date | Event | Impact | Contact |\n|------|-------|--------|---------|\n| 01\u002F23 02:00 | Database maintenance | 5 min read-only | @dba-team |\n| 01\u002F24 14:00 | Major release v5.0 | Monitor closely | @release-team |\n| 01\u002F25 | Marketing campaign | 2x traffic expected | @platform |\n\n---\n\n## 📞 Escalation Reminders\n\n| Issue Type | First Escalation | Second Escalation |\n|------------|------------------|-------------------|\n| Payment issues | @payments-oncall | @payments-manager |\n| Auth issues | @auth-oncall | @security-team |\n| Database issues | @dba-team | @infra-manager |\n| Unknown\u002Fsevere | @engineering-manager | @vp-engineering |\n\n---\n\n## 🔧 Quick Reference\n\n### Common Commands\n```bash\n# Check service health\nkubectl get pods -A | grep -v Running\n\n# Recent deployments\nkubectl get events --sort-by='.lastTimestamp' | tail -20\n\n# Database connections\npsql -c \"SELECT count(*) FROM pg_stat_activity;\"\n\n# Clear cache (emergency only)\nredis-cli FLUSHDB\n```\n\n### Important Links\n- [Runbooks](https:\u002F\u002Fwiki\u002Frunbooks)\n- [Service Catalog](https:\u002F\u002Fwiki\u002Fservices)\n- [Incident Slack](https:\u002F\u002Fslack.com\u002Fincidents)\n- [PagerDuty](https:\u002F\u002Fpagerduty.com\u002Fschedules)\n\n---\n\n## Handoff Checklist\n\n### Outgoing Engineer\n- [x] Document active incidents\n- [x] Document ongoing investigations\n- [x] List recent changes\n- [x] Note known issues\n- [x] Add upcoming events\n- [x] Sync with incoming engineer\n\n### Incoming Engineer\n- [ ] Read this document\n- [ ] Join sync call\n- [ ] Verify PagerDuty is routing to you\n- [ ] Verify Slack notifications working\n- [ ] Check VPN\u002Faccess working\n- [ ] Review critical dashboards\n```\n\n### Template 2: Quick Handoff (Async)\n\n```markdown\n# Quick Handoff: @alice → @bob\n\n## TL;DR\n- No active incidents\n- 1 investigation ongoing (API timeouts, see ENG-1234)\n- Major release tomorrow (01\u002F24) - be ready for issues\n\n## Watch List\n1. API latency around 02:00-03:00 UTC (backup window)\n2. Auth service memory (restart if > 80%)\n\n## Recent\n- Deployed api-gateway v3.2.1 yesterday (stable)\n- Increased rate limits to 1500 RPS\n\n## Coming Up\n- 01\u002F23 02:00 - DB maintenance (5 min read-only)\n- 01\u002F24 14:00 - v5.0 release\n\n## Questions?\nI'll be available on Slack until 17:00 today.\n```\n\n### Template 3: Incident Handoff (Mid-Incident)\n\n```markdown\n# INCIDENT HANDOFF: Payment Service Degradation\n\n**Incident Start**: 2024-01-22 08:15 UTC\n**Current Status**: Mitigating\n**Severity**: SEV2\n\n---\n\n## Current State\n- Error rate: 15% (down from 40%)\n- Mitigation in progress: scaling up pods\n- ETA to resolution: ~30 min\n\n## What We Know\n1. Root cause: Memory pressure on payment-service pods\n2. Triggered by: Unusual traffic spike (3x normal)\n3. Contributing: Inefficient query in checkout flow\n\n## What We've Done\n- Scaled payment-service from 5 → 15 pods\n- Enabled rate limiting on checkout endpoint\n- Disabled non-critical features\n\n## What Needs to Happen\n1. Monitor error rate - should reach \u003C1% in ~15 min\n2. If not improving, escalate to @payments-manager\n3. Once stable, begin root cause investigation\n\n## Key People\n- Incident Commander: @alice (handing off)\n- Comms Lead: @charlie\n- Technical Lead: @bob (incoming)\n\n## Communication\n- Status page: Updated at 08:45\n- Customer support: Notified\n- Exec team: Aware\n\n## Resources\n- Incident channel: #inc-20240122-payment\n- Dashboard: [Payment Service](https:\u002F\u002Fgrafana\u002Fd\u002Fpayments)\n- Runbook: [Payment Degradation](https:\u002F\u002Fwiki\u002Frunbooks\u002Fpayments)\n\n---\n\n**Incoming on-call (@bob) - Please confirm you have:**\n- [ ] Joined #inc-20240122-payment\n- [ ] Access to dashboards\n- [ ] Understand current state\n- [ ] Know escalation path\n```\n\n## Handoff Sync Meeting\n\n### Agenda (15 minutes)\n\n```markdown\n## Handoff Sync: @alice → @bob\n\n1. **Active Issues** (5 min)\n   - Walk through any ongoing incidents\n   - Discuss investigation status\n   - Transfer context and theories\n\n2. **Recent Changes** (3 min)\n   - Deployments to watch\n   - Config changes\n   - Known regressions\n\n3. **Upcoming Events** (3 min)\n   - Maintenance windows\n   - Expected traffic changes\n   - Releases planned\n\n4. **Questions** (4 min)\n   - Clarify anything unclear\n   - Confirm access and alerting\n   - Exchange contact info\n```\n\n## On-Call Best Practices\n\n### Before Your Shift\n\n```markdown\n## Pre-Shift Checklist\n\n### Access Verification\n- [ ] VPN working\n- [ ] kubectl access to all clusters\n- [ ] Database read access\n- [ ] Log aggregator access (Splunk\u002FDatadog)\n- [ ] PagerDuty app installed and logged in\n\n### Alerting Setup\n- [ ] PagerDuty schedule shows you as primary\n- [ ] Phone notifications enabled\n- [ ] Slack notifications for incident channels\n- [ ] Test alert received and acknowledged\n\n### Knowledge Refresh\n- [ ] Review recent incidents (past 2 weeks)\n- [ ] Check service changelog\n- [ ] Skim critical runbooks\n- [ ] Know escalation contacts\n\n### Environment Ready\n- [ ] Laptop charged and accessible\n- [ ] Phone charged\n- [ ] Quiet space available for calls\n- [ ] Secondary contact identified (if traveling)\n```\n\n### During Your Shift\n\n```markdown\n## Daily On-Call Routine\n\n### Morning (start of day)\n- [ ] Check overnight alerts\n- [ ] Review dashboards for anomalies\n- [ ] Check for any P0\u002FP1 tickets created\n- [ ] Skim incident channels for context\n\n### Throughout Day\n- [ ] Respond to alerts within SLA\n- [ ] Document investigation progress\n- [ ] Update team on significant issues\n- [ ] Triage incoming pages\n\n### End of Day\n- [ ] Hand off any active issues\n- [ ] Update investigation docs\n- [ ] Note anything for next shift\n```\n\n### After Your Shift\n\n```markdown\n## Post-Shift Checklist\n\n- [ ] Complete handoff document\n- [ ] Sync with incoming on-call\n- [ ] Verify PagerDuty routing changed\n- [ ] Close\u002Fupdate investigation tickets\n- [ ] File postmortems for any incidents\n- [ ] Take time off if shift was stressful\n```\n\n## Escalation Guidelines\n\n### When to Escalate\n\n```markdown\n## Escalation Triggers\n\n### Immediate Escalation\n- SEV1 incident declared\n- Data breach suspected\n- Unable to diagnose within 30 min\n- Customer or legal escalation received\n\n### Consider Escalation\n- Issue spans multiple teams\n- Requires expertise you don't have\n- Business impact exceeds threshold\n- You're uncertain about next steps\n\n### How to Escalate\n1. Page the appropriate escalation path\n2. Provide brief context in Slack\n3. Stay engaged until escalation acknowledges\n4. Hand off cleanly, don't just disappear\n```\n\n## Best Practices\n\n### Do's\n- **Document everything** - Future you will thank you\n- **Escalate early** - Better safe than sorry\n- **Take breaks** - Alert fatigue is real\n- **Keep handoffs synchronous** - Async loses context\n- **Test your setup** - Before incidents, not during\n\n### Don'ts\n- **Don't skip handoffs** - Context loss causes incidents\n- **Don't hero** - Escalate when needed\n- **Don't ignore alerts** - Even if they seem minor\n- **Don't work sick** - Swap shifts instead\n- **Don't disappear** - Stay reachable during shift\n\n## Resources\n\n- [Google SRE - Being On-Call](https:\u002F\u002Fsre.google\u002Fsre-book\u002Fbeing-on-call\u002F)\n- [PagerDuty On-Call Guide](https:\u002F\u002Fwww.pagerduty.com\u002Fresources\u002Flearn\u002Fon-call-management\u002F)\n- [Increment On-Call Issue](https:\u002F\u002Fincrement.com\u002Fon-call\u002F)\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fwshobson-agents\u002Fplugins\u002Fincident-response\u002Fskills\u002Fon-call-handoff-patterns",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill on-call-handoff-patterns",{"tool":55,"command":56},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill on-call-handoff-patterns",{"tool":58,"command":59},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill on-call-handoff-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fwshobson-agents\u002Fplugins\u002Fincident-response\u002Fskills\u002Fon-call-handoff-patterns\u002FSKILL.md",true,[],[64,83,116,141,163,183],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":34},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[76,77,78,79,80,81,82],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":97,"publishedAt":34},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[89,92],{"categoryNo":90,"categoryName":91,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[85,98,99,100,101,102,103,104,105,106,107,108,109,24,110,111,112,113,114,115],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","project wiki","disk","architecture","code","unknown","generated",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":126,"publishedAt":34},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[122,123],{"categoryNo":90,"categoryName":91,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000036","内容创作者",[118,127,128,129,130,131,132,133,106,134,135,136,23,28,137,138,139,140],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":34},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[147],{"categoryNo":90,"categoryName":91,"taxonomyType":73,"taxonomyTypeDesc":74},[149,150,118,151,152,139,153,154,155,156,157,158,159,160,104,161,23,28,98,162],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":34},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[169,170,171,172],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":90,"categoryName":91,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},[174,81,175,176,177,178,113,23,28,179,180,181,182],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":191,"publishedAt":34},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[189,190],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":124,"categoryName":125,"taxonomyType":95,"taxonomyTypeDesc":96},[192,81,193,102,194,180,23,175,178,28,181],"Rules","writing rules","project rules"]