Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Master on-call shift handoffs with context transfer, escalation procedures, and documentation.
Install On Call Handoff Patterns
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wshobson/agents on-call-handoff-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .claude/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .claude/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wshobson/agents on-call-handoff-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .agents/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .agents/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wshobson/agents on-call-handoff-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .cursor/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .cursor/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wshobson/agents.git --path plugins/incident-response/skills/on-call-handoff-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wshobson/agents on-call-handoff-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .gemini/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .gemini/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wshobson/agents on-call-handoff-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .github/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .github/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill on-call-handoff-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wshobson/agents on-call-handoff-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/incident-response/skills/on-call-handoff-patterns .opencode/skills/on-call-handoff-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "on-call-handoff-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/incident-response/skills/on-call-handoff-patterns into .opencode/skills/on-call-handoff-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "on-call-handoff-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
on-call-handoff-patterns- GitHub stars
- 40k
- Token cost
- ~917 tokens
- SKILL.md length
- 329 words
- Files
- 2 (incl. references)
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
Master on-call shift handoffs with context transfer, escalation procedures, and documentation.
- Works in 2 steps: Handoff Components → Handoff Timing
- Transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness
- SKILL.md covers When to Use This Skill, Core Concepts, Templates and detailed worked… and Troubleshooting, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
On Call Handoff Patterns is an agent skill from wshobson/agents. Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation…
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/details.md`).
It sits in DevOps & Cloud, covering Incident response. The repository describes itself as: Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi. The licence is MIT.
When your agent uses it
- Transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness
- Writing a shift summary that captures active incidents
- Ongoing investigations
- Handing off mid-incident so a fresh engineer can take over the incident commander role without losing context
Example prompts
- “/on-call-handoff-patterns”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
On Call Handoff Patterns loads about 917 tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 162 tokens; SKILL.md has 329 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 329 words, ~917 tokens.
Download SKILL.mdSave it as
.claude/skills/on-call-handoff-patterns/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- on-call-handoff-patterns
- description
- Master on-call shift handoffs with context transfer, escalation procedures, and documentation. Use this skill when transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness, when writing a shift summary that captures active incidents, ongoing investigations, and recent changes, when handing off mid-incident so a fresh engineer can take over the incident commander role without losing context, when onboarding a new engineer to the on-call rotation for the first time, or when auditing and improving the quality of existing handoff processes across teams.
On-Call Handoff Patterns
Effective patterns for on-call shift transitions, ensuring continuity, context transfer, and reliable incident response across shifts.
When to Use This Skill
- Transitioning on-call responsibilities
- Writing shift handoff summaries
- Documenting ongoing investigations
- Establishing on-call rotation procedures
- Improving handoff quality
- Onboarding new on-call engineers
Core Concepts
1. Handoff Components
| Component | Purpose |
|---|---|
| Active Incidents | What's currently broken |
| Ongoing Investigations | Issues being debugged |
| Recent Changes | Deployments, configs |
| Known Issues | Workarounds in place |
| Upcoming Events | Maintenance, releases |
2. Handoff Timing
Recommended: 30 min overlap between shifts
Outgoing:
├── 15 min: Write handoff document
└── 15 min: Sync call with incoming
Incoming:
├── 15 min: Review handoff document
├── 15 min: Sync call with outgoing
└── 5 min: Verify alerting setupTemplates and detailed worked examples
Full template library and detailed worked examples live in references/details.md. Read that file when you need the concrete templates.
Troubleshooting
Incoming engineer misses a critical issue because the handoff document was incomplete. Use the outgoing checklist as a gate: do not mark handoff complete until every section has at least one entry (or an explicit "none"). Make incomplete handoffs a blameless postmortem action item.
A 30-minute sync call is not possible due to timezone gaps. Fall back to the async quick handoff template (Template 2). Supplement with a short Loom or voice memo walking through the watch list. Ensure the incoming engineer has a direct contact method if they have follow-up questions.
The incoming engineer inherits a mid-incident and is immediately overwhelmed. Use the incident handoff template (Template 3) specifically. The outgoing engineer should remain available on Slack for 15 minutes after handoff, even if off-call, to answer clarifying questions.
On-call handoff documents are inconsistently formatted across teams. Adopt the shift handoff template organization-wide and store completed handoffs in a shared location (wiki, Notion, Confluence). Link each handoff from the on-call schedule entry in PagerDuty.
Incoming engineer cannot verify their alerting is working before the outgoing engineer logs off. Add a standard step: outgoing engineer fires a test alert and confirms incoming engineer receives it in PagerDuty and Slack before ending the overlap window.
Related Skills
- incident-runbook-templates — Runbooks for the incidents that are handed over mid-response
- postmortem-writing — Turn resolved incidents from the shift into structured postmortems
© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/incident-response/skills/on-call-handoff-patterns of wshobson/agents.
- SKILL.md
- references/details.md
Open the folder on GitHubat commit 46891e7
Compare with similar skills
On Call Handoff Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| On Call Handoff Patterns this skillwshobson/agents | 40k | — | ~917 | Automated safety check: Pass | MIT | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 | |
| UModel Root Cause Analysisalibaba/UnifiedModel | 415 | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Learningskortix-ai/suna | 20k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Oncallpigweed-project/pigweed | 548 | — | ~992 | Automated safety check: Pass | Apache-2.0 | |
| Loop Triage Reportcobusgreyling/loop-engineering | 11k | — | ~500 | Automated safety check: Pass | MIT |
Similar skills
UModel Root Cause Analysis
alibaba/UnifiedModel
Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.
Learnings
kortix-ai/suna
The project's episodic memory: a timestamped ledger of rules paid for with real outages and near-misses, one entry per incident.
Oncall
pigweed-project/pigweed
Pigweed oncall rotation runbooks and maintenance workflows (such as rolling CIPD client tools for b/315378787).
Loop Triage Report
cobusgreyling/loop-engineering
Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.
Axiom SRE Investigator
openclaw/clawhub
Investigates incidents and production problems with hypothesis-driven debugging, queries Axiom observability data when available, and keeps secrets out of commands and output.
More from wshobson/agents
All 142 skills in this repoCloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Billing Automation
wshobson/agents
Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.
Python Performance Optimization
wshobson/agents
Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.
Bats Shell Testing Patterns
wshobson/agents
Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.
Distributed Tracing
wshobson/agents
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.
Prompt Engineering Patterns
wshobson/agents
Reference for designing and tuning production LLM prompts: few-shot examples, chain-of-thought, structured outputs, templates and system prompts.
Related
Categories
Questions about On Call Handoff Patterns
What does On Call Handoff Patterns do?
Master on-call shift handoffs with context transfer, escalation procedures, and documentation. On Call Handoff Patterns is an agent skill from wshobson/agents. Master on-call shift handoffs with context transfer, escalation procedures, and documentation.
When should I use On Call Handoff Patterns?
On Call Handoff Patterns fits situations like: transitioning on-call responsibilities between engineers and ensuring the incoming responder has full situational awareness; writing a shift summary that captures active incidents; ongoing investigations; handing off mid-incident so a fresh engineer can take over the incident commander role without losing context.
How do I install On Call Handoff Patterns in Claude Code?
Run `npx skills add wshobson/agents --skill on-call-handoff-patterns -a claude-code`. Or copy the skill folder (plugins/incident-response/skills/on-call-handoff-patterns in wshobson/agents) into .claude/skills/on-call-handoff-patterns in your project. Claude Code loads it when a task matches its description.
How do I install On Call Handoff Patterns in Codex?
Run `npx skills add wshobson/agents --skill on-call-handoff-patterns -a codex`. Or copy the skill folder (plugins/incident-response/skills/on-call-handoff-patterns in wshobson/agents) into .agents/skills/on-call-handoff-patterns in your project. Codex loads it when a task matches its description.
Can I use On Call Handoff Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill on-call-handoff-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/on-call-handoff-patterns, .gemini/skills/on-call-handoff-patterns, .github/skills/on-call-handoff-patterns and .opencode/skills/on-call-handoff-patterns in your project.
What does On Call Handoff Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: On Call Handoff Patterns is instructions for the agent only.
Does On Call Handoff Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is On Call Handoff Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does On Call Handoff Patterns use?
On Call Handoff Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does On Call Handoff Patterns use?
About 917 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
What are the alternatives to On Call Handoff Patterns?
Skills that share tags, products or a category with On Call Handoff Patterns: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 415 stars), Learnings (kortix-ai/suna, 20k stars) and Oncall (pigweed-project/pigweed, 548 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains On Call Handoff Patterns?
wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,305 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.
Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.