cnoe-io/oncall-handoff
charts/ai-platform-engineering/data/skills/oncall-handoff/SKILL.md
Generate a comprehensive on-call handoff document by aggregating open incidents, ongoing issues, recent deployments, and systems to watch. Orchestrates PagerDuty, Jira, and ArgoCD agents. Use during on-call rotation changes or shift handoffs.
$ install --global
skillsauthnpx skillsauth add cnoe-io/ai-platform-engineering oncall-handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 4:51 PM3.7s2 files scanned
SKILL.md
- name:
- oncall-handoff
- description:
- Generate a comprehensive on-call handoff document by aggregating open incidents, ongoing issues, recent deployments, and systems to watch. Orchestrates PagerDuty, Jira, and ArgoCD agents. Use during on-call rotation changes or shift handoffs.
On-Call Handoff
Build a structured handoff document for the incoming on-call engineer by collecting data from PagerDuty, Jira, and ArgoCD.
Instructions
Phase 1: Current Incident State (PagerDuty Agent)
- Active incidents - all triggered and acknowledged incidents
- Recently resolved incidents - resolved in the last 24 hours (may recur)
- Current on-call schedule - who is on-call now, who is taking over
- Upcoming maintenance windows - scheduled within the next 48 hours
Phase 2: Ongoing Issues (Jira Agent)
- Open incident tickets - Jira issues labeled `incident`, `outage`, `p0`, `p1`
- Known issues - issues labeled `known-issue` or `workaround`
- Recently closed issues - resolved in last 48 hours that may have follow-ups
- Pending changes - tickets in "Ready for Deploy" or "In Review" status
Phase 3: Environment State (ArgoCD Agent)
- Recent deployments - applications synced in the last 48 hours
- Unhealthy applications - any OutOfSync, Degraded, or Unknown apps
- Pending syncs - applications with pending changes not yet deployed
- Recent rollbacks - any applications that were rolled back
Phase 4: Compile Handoff Document
Organize all data into a structured, scannable document with clear action items.
Output Format
```markdown
On-Call Handoff Document
Date: February 9, 2026 Outgoing: @engineer-a | Incoming: @engineer-b
Active Incidents (Action Required)
| Incident | Service | Urgency | Duration | Status | |----------|---------|---------|----------|--------| | INC-789 | auth-service | High | 2h 15m | Acknowledged |
Systems to Watch
- auth-service - Connection pool issue ongoing
- payment-api - Hotfix deployed yesterday, watch for regression ```
Examples
- "Generate an on-call handoff document"
- "Prepare a shift handoff for the incoming on-call engineer"
- "What should the next on-call person know about?"
- "Summarize the current state of production for handoff"
Guidelines
- Prioritize actionable information - what does the incoming engineer need to DO?
- Include workarounds for known issues so the incoming engineer does not have to search
- Mark items as "action required" vs "monitor" vs "FYI" for clear prioritization
- Always include escalation contacts with team context
- Keep the last 48 hours as the default lookback window for context
- If no active incidents exist, say so explicitly (this is good news)
Related Skills
cnoe-io/streaming-testing
testing
VerifiedTrustedCommunity
Compare A2A streaming behaviour across supervisor versions. Captures SSE events, analyzes metadata flags (is_narration, is_final_answer), and produces side-by-side comparison reports.
345SKILL.mdUpdated Apr 15, 2026
cnoe-io/sprint-progress-report
testing
VerifiedTrustedCommunity
Generate a comprehensive sprint progress report from Jira with velocity metrics, burndown analysis, blocker identification, and team workload distribution. Use when preparing sprint reviews, standups, or tracking sprint health mid-cycle.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/security-vulnerability-report
development
VerifiedTrustedCommunity
Scan GitHub repositories for security vulnerabilities including Dependabot alerts, code scanning results, and secret scanning findings. Use when auditing repository security, preparing compliance reports, or triaging vulnerability alerts.
345SKILL.mdUpdated Apr 4, 2026
cnoe-io/review-specific-pr
development
VerifiedTrustedCommunity
Perform a comprehensive code review of a specific GitHub Pull Request. Analyzes code changes, checks for bugs, security issues, test coverage, and coding standards compliance. Use when a user provides a PR URL or asks to review a specific pull request.
345SKILL.mdUpdated Apr 4, 2026