swap
Request someone to cover one of your upcoming on-call shifts. Lists your shifts, helps identify a candidate based on availability, and creates an override after explicit confirmation. Write action - never executes without confirming.
What this skill does
# Shift Swap Request
You are helping the user offload one of their on-call shifts to someone else. This is a **write action**: you must show the proposed change and get explicit user confirmation before calling `mcp__rootly__createOverrideShift`.
## Workflow
### 1. Identify the user
Call `mcp__rootly__getCurrentUser`. Capture `user_id`.
### 2. List the user's shifts
Call `mcp__rootly__listShifts` (or `list_shifts`) scoped to:
- The current user
- Next 14 days
If the MCP doesn't expose user-level filtering, call the broader `listShifts` and filter client-side by `user_id`.
### 3. Pick the target shift
- If `$ARGUMENTS` is empty: show the next 5 shifts and ask "Which shift do you want covered?"
- If `$ARGUMENTS` is `next`: pick the soonest upcoming shift.
- If `$ARGUMENTS` is a date or shift identifier: try to match.
If no match, list options and ask.
### 4. Find candidate coverers
For the shift's schedule and time window:
1. Call `mcp__rootly__create_override_recommendation` if it accepts the shift parameters — this is the cleanest path; it returns suggested coverers.
2. Otherwise, fall back to `mcp__rootly__check_responder_availability` against the relevant team/schedule and propose users with `available=true` and no conflicting shifts.
3. Present up to 3 candidates with reasoning (workload, recent shifts, conflicts).
If no candidates are available, surface that and stop.
### 5. Show the proposal
```
**Proposed shift swap:**
- **Shift**: [Schedule name] [start] → [end] ([duration])
- **Currently assigned**: you ([your name])
- **Proposed coverer**: [candidate name]
- **Why**: [reason — e.g. "no shifts this week, on team rotation"]
**Alternatives**:
- [other candidate] — [reason]
- [other candidate] — [reason]
Confirm to create the override? (yes / no / pick another)
```
### 6. Wait for confirmation
- **`yes`** → call `mcp__rootly__createOverrideShift` with this shape:
```json
{
"schedule_id": "[schedule_id]",
"data": {
"type": "shifts",
"attributes": {
"starts_at": "[shift start ISO8601]",
"ends_at": "[shift end ISO8601]",
"user_id": [coverer user id]
}
}
}
```
Echo the resulting override ID and a confirmation line.
- **`pick another`** or naming a different candidate → revise the proposal and re-confirm. Do not execute on the first reply if the user is changing the candidate.
- **`no`** or any other answer → acknowledge and stop. Do not call the create tool.
### 7. After the override is created
Output:
```
✅ Override created.
- ID: [uuid]
- Coverer: [name]
- Window: [start] → [end]
Recommended next steps:
- Notify the coverer in Slack / your team channel.
- The original on-call schedule will route alerts to the coverer for this window.
```
### 8. Guidelines
- **Never** call `createOverrideShift` without confirmation. The "yes" must come from the user, not be inferred.
- If `create_override_recommendation` is unavailable, lean on `check_responder_availability` rather than guessing. Don't propose a coverer you can't verify is available.
- If the user's shift is in the past or already started, refuse with a helpful message — overrides for the present moment are usually a different operation.
- Show timezone explicitly in the proposal. Ambiguous times cause mistakes.
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.