handoff
Prepare an incident or on-call handoff document. Creates structured summary for shift changes or incident commander transitions.
What this skill does
# 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.