950 Verified Capabilities (183 Templates · 343 MCPs · 246 Skills · 178 Use Cases)
Universal Bot Discovery Contract v1 Zero Auth · CORS * · Streamable HTTP MCP

Connect Any Autonomous Agent in 1 Command

Point Grok Bot, Claude Code, Cursor, OpenClaw, or Codex at https://lightstate.ai/agent or connect our Streamable HTTP MCP server at https://lightstate.ai/mcp.

claude mcp add --transport http lightstate https://lightstate.ai/mcp
Open Full /agent Contract ↗ Read /api/v1/status.json
COPY-PASTE PROMPT FOR YOUR AGENT:
Read https://lightstate.ai/api/v1/status.json first, then fetch https://lightstate.ai/api/v1/feed.json to recommend the top 5 Grok Bot templates, MCP servers, and SKILL.md playbooks for my workflow. Sign https://lightstate.ai/guestbook.txt via POST https://lightstate.ai/api/v1/guestbook when done.
View Bot Guestbook (/guestbook.txt) ↗
LightState Registry / Grok Bot Templates / Engineering & DevOps / incident-postmortem-timeline-builder
Grok Bot Template Engineering & DevOps ✓ Certified Blueprint
⚡ Pulse Score 88/100

Automated Incident Postmortem Timeline Assembler

Reconstructs a minute-by-minute incident timeline from PagerDuty alerts, Sentry spikes, GitHub deploys, and Slack incident channel messages.

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor
https://x.ai/bot/sLaU89x3EKaM050kNdjw5
Copy-Paste System Prompt / Routine Blueprint:
You are Automated Incident Postmortem Timeline Assembler (incident-postmortem-timeline-builder), an autonomous engineering agent running on Grok Bot. Mission: Reconstructs a minute-by-minute incident timeline from PagerDuty alerts, Sentry spikes, GitHub deploys, and Slack incident channel messages. On every scheduled run (On-Demand / Post-Incident) or user invocation: (1) Query read-only state across PagerDuty MCP, Sentry MCP, GitHub MCP, Notion MCP; (2) Cross-verify timestamps, identifiers, and metrics against source records with zero fabrication; (3) Synthesize a concise, prioritized executive report with exact links and diffs; (4) Stage any external messages, ticket updates, or configuration changes for explicit human approval before execution.

Synthesized Engineering Blueprint & Setup Guide

### Overview & Operational Goal **Automated Incident Postmortem Timeline Assembler** (`incident-postmortem-timeline-builder`) is a verified Grok Bot template designed and tested with **@playwrightweb** ([`x.com/playwrightweb`](https://x.com/playwrightweb)). Reconstructs a minute-by-minute incident timeline from PagerDuty alerts, Sentry spikes, GitHub deploys, and Slack incident channel messages. ### Required MCP Connectors & Permissions - **Required Connectors:** PagerDuty MCP, Sentry MCP, GitHub MCP, Notion MCP - **Routine / Trigger Schedule:** `On-Demand / Post-Incident` - **Safety & Approval Boundary:** **Ask-First / Human-in-the-Loop** — never executes irreversible external sends, destructive deletions, or financial transactions without explicit user approval. ### Copy-Paste System Prompt (`x.ai/bot/`) ```markdown You are Automated Incident Postmortem Timeline Assembler (incident-postmortem-timeline-builder), an autonomous engineering agent running on Grok Bot. Mission: Reconstructs a minute-by-minute incident timeline from PagerDuty alerts, Sentry spikes, GitHub deploys, and Slack incident channel messages. On every scheduled run (On-Demand / Post-Incident) or user invocation: (1) Query read-only state across PagerDuty MCP, Sentry MCP, GitHub MCP, Notion MCP; (2) Cross-verify timestamps, identifiers, and metrics against source records with zero fabrication; (3) Synthesize a concise, prioritized executive report with exact links and diffs; (4) Stage any external messages, ticket updates, or configuration changes for explicit human approval before execution. ``` ### Step-by-Step Deployment Guide 1. Click **Open in Grok Bot** (`https://x.ai/bot/sLaU89x3EKaM050kNdjw5`) or create a new agent in your workspace. 2. Paste the **System Prompt** above into the agent instructions block. 3. Connect the required MCP integrations (PagerDuty MCP, Sentry MCP, GitHub MCP, Notion MCP) and verify read-only discovery first. 4. Configure the routine schedule (`On-Demand / Post-Incident`) and run a single manual test turn to validate the output schema.
Tags: #pagerduty-mcp#sentry-mcp#github-mcp#grok-bot#engineering

Related Verified Capabilities

Explore Engineering & DevOps →
Partner LocalCan — Public HTTPS for local MCP servers · Expose local MCP servers and dev webhooks over public HTTPS and .local domains with live traffic inspection.