Skip to main content
skill CX Codex

ops-oncall-log — Claude Code skill: on-call log from alerts

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a claude-code
Open on GitHub

What ops-oncall-log 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.

What it helps with

  • 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 for the agent

  • 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

How to install ops-oncall-log

1Skills CLI (Vercel)

npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a claude-code

2Manually: put the files in place

~/.claude/skills/ops-oncall-log/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ops-oncall-log/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about ops-oncall-log

How do I install ops-oncall-log in Claude Code?

Run npx skills add c0x12c/ai-toolkit --skill ops-oncall-log -a claude-code. The skill lands in ~/.claude/skills/ops-oncall-log/SKILL.md.

What does ops-oncall-log do?

It fetches alert events from your monitoring platform, groups them by monitor, and creates an on-call log page on the team wiki with an alert table and a list of active monitors.

What do I need before running it?

Two MCP servers: one for monitoring (Datadog recommended) and one for the wiki, either Confluence or Notion. Without both, the skill stops with an error.

Similar skills

All skills for DevOps and infrastructure →

From the same set11

testing-strategies Gives your coding agent ready test patterns for a Micronaut and Kotlin backend: integration tests, repository tests, test data builders. CX Codex +1 ★ 109repo stars terraform-review Walks Terraform changes through an 8-category checklist and returns a verdict: Approved, Needs Changes or Blocked. Useful before merging an infrastructure PR. CX Codex +1 ★ 109repo stars startup-pipeline Moves a startup idea through four stages: brainstorm, validation, market research and pitch materials. Gates between stages stop weak ideas early. CX Codex +1 ★ 109repo stars python-testing-strategies A skill that tells your coding agent how to test FastAPI apps: pytest-asyncio, httpx AsyncClient, data factories and the checks every endpoint needs. CX Codex +1 ★ 109repo stars kotlin-best-practices A skill that pins down Kotlin conventions: null safety, Either instead of thrown exceptions, coroutines, and Exposed ORM patterns. Useful while writing or reviewing Kotlin. CX Codex +1 ★ 109repo stars investor-materials A skill for producing investor-facing documents: a pitch deck, one-pager, memo and financial model. Useful when the numbers and the story have to line up across every file. CX Codex +1 ★ 109repo stars design-intelligence Bootstraps a design system from scratch: palette, type scale, spacing, radii and a component inventory in three formats. CX Codex +1 ★ 109repo stars database-patterns Hands your agent a fixed set of database rules: column types, UUID keys, soft deletes and migration templates. Useful when it writes tables or repositories. CX Codex +1 ★ 109repo stars

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor