ops-oncall-log
On-Call Log
Pull alerts from your monitoring platform and create a structured on-call log on your team's wiki.
When to Use
- End of your on-call shift — log what happened for the next engineer
- Daily or weekly on-call review meetings
- Building a history of alert patterns over time
Process
1. Verify MCP Server Availability
Two MCP servers are required:
- Monitoring MCP — to fetch alert events and monitor status. Recommended: Datadog MCP.
- Wiki MCP — to create the log page. Supported: Confluence (
mcp__claude_ai_Atlassian__*) or Notion (mcp__claude_ai_Notion__*).
More from spartan-stratos/spartan-ai-toolkit
kotlin-best-practices
Kotlin coding standards including null safety, Either error handling, coroutines, and Exposed ORM patterns. Use when writing Kotlin code, reviewing code quality, or learning project patterns.
11ops-investigate-alert
Investigate a monitoring alert end-to-end. Pulls metrics, logs, traces, and recent code changes to identify root cause. Works with any monitoring MCP.
10startup-pipeline
Coordinates the full startup idea pipeline from brainstorm to investor outreach. Use when the user starts a new idea project, asks for the 'full pipeline', or references stages/gates.
9terraform-service-scaffold
Generate complete service-level Terraform infrastructure with modules, environments, and CI/CD. Use when adding Terraform to a new service or bootstrapping infrastructure from scratch.
8investor-outreach
Draft cold emails, warm intro blurbs, follow-ups, and investor communications. Use when the user needs to write to angels, VCs, or accelerators.
8article-writing
Write blog posts, guides, tutorials, and long-form content. Sounds like a real person, not AI. Use when the user wants polished written content.
8