# ops-oncall-log

Pulls alerts from your monitoring platform and writes a structured on-call log to the team wiki. Useful at the end of a shift or during a review.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 109
- Author: c0x12c
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/c0x12c/ai-toolkit/tree/HEAD/toolkit/skills/ops-oncall-log/SKILL.md
- Updated: 2026-06-18
- HTML: https://affpapa.org/en/nevibecode/skills/ops-oncall-log

## What it does

The skill walks through a fixed sequence. First it checks that two MCP servers are connected, then asks about log frequency (daily or weekly), the rotation start day, which environments to include, and where the page should live. It recommends Datadog MCP for monitoring; Confluence (`mcp__claude_ai_Atlassian__*`) and Notion (`mcp__claude_ai_Notion__*`) are the supported wiki options. If either server is absent, the skill stops with an error and writes nothing.

Alert events get grouped by base monitor name: how many times each fired, the timestamps, and the current status. Recovery events are dropped, so only triggered and warn entries count. Pages follow the hierarchy `On-call Logs/On-call <YYYY>/On-call <MM>/<YYYY>/[On-call] <Start Date> - <End Date>`, and the alert table carries Cause and Resolution columns. Cause is deliberately left blank for the engineer to fill in after the fact. Monitors still firing get “Still active” in Resolution.

When a page for the period already exists, the skill asks whether to update it or start a new one. On update it uses the last timestamp on the page as the starting point, so alerts already logged are not fetched again. Settings from earlier runs are reused, for instance from `.spartan/config.yaml`, and you confirm them before anything is pulled. The date range is always confirmed with you first.

## Requirements
- Works with: Datadog, Confluence, Notion

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/ops-oncall-log/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/ops-oncall-log/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/ops-oncall-log/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/ops-oncall-log/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install c0x12c/ai-toolkit ops-oncall-log
```

2. **Manually: put the files in place**
- File: `.github/skills/ops-oncall-log/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/c0x12c/ai-toolkit --path toolkit/skills/ops-oncall-log
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/ops-oncall-log/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/c0x12c/ai-toolkit/tree/HEAD/toolkit/skills/ops-oncall-log/SKILL.md

## When to use it
- build an on-call log from monitoring alerts
- hand off a shift with a written incident history
- prepare a summary for the weekly on-call review
- spot which monitors fire most often
- flag active alerts the next engineer should pick up

## Example prompts
- Build the on-call log for this week from Datadog alerts and put it in Confluence
- Update the log page for the current period with alerts since the last update
- Create a daily log for prod only and flag monitors still in Alert status

## Similar
- [wizard](https://affpapa.org/en/nevibecode/skills/wizard.md) — skill · 553369 installs
- [hyperframes-cli](https://affpapa.org/en/nevibecode/skills/heygen-com-hyperframes-cli.md) — skill · 1300000 installs
- [setup-pre-commit](https://affpapa.org/en/nevibecode/skills/setup-pre-commit.md) — skill · 489289 installs
- [using-git-worktrees](https://affpapa.org/en/nevibecode/skills/using-git-worktrees.md) — skill · 217153 installs
- [finishing-a-development-branch](https://affpapa.org/en/nevibecode/skills/finishing-a-development-branch.md) — skill · 214439 installs
- [orca-cli](https://affpapa.org/en/nevibecode/skills/orca-cli.md) — skill · 354000 installs

From the same set: [c0x12c/ai-toolkit](https://affpapa.org/en/nevibecode/by/c0x12c/ai-toolkit.md) — 11 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md