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 / Verified X Builder Use Cases / Engineering & DevOps / data-json-schema-registry-and-event-contract-gate
Verified X Builder Use Case Engineering & DevOps ✓ Certified Blueprint
⚡ Pulse Score 84/100

Analytics Event Schema Contract & Breaking-Change CI Gate

Validate PostHog and Segment tracking calls in PR diffs against a central JSON Schema registry so analytics pipelines never break.

⚡ 1-Click Agent & Developer Install

Zero Auth · Ready for Grok Bot, Claude Code & Cursor
npx lightstate inspect data-json-schema-registry-and-event-contract-gate
Copy-Paste System Prompt / Routine Blueprint:
Execute the 'Analytics Event Schema Contract & Breaking-Change CI Gate' (data-json-schema-registry-and-event-contract-gate) blueprint with PostHog MCP, GitHub MCP, Slack MCP. Goal: Validate PostHog and Segment tracking calls in PR diffs against a central JSON Schema registry so analytics pipelines never break. First inspect live state in read-only mode, validate all identifiers and metrics, and output a concrete action plan with verification commands before making any changes.

Synthesized Engineering Blueprint & Setup Guide

### 1. Problem & Operational Bottleneck Validate PostHog and Segment tracking calls in PR diffs against a central JSON Schema registry so analytics pipelines never break. Built and battle-tested in production workflows by **@kentcdodds** (Kent C. Dodds (@kentcdodds)). ### 2. Target Architecture & Required Stack - **PostHog MCP** - **GitHub MCP** - **Slack MCP** ### 3. Step-by-Step Implementation Blueprint 1. Connect PostHog MCP, GitHub MCP, Slack MCP and verify read-only access to the target workspace. 2. Run the discovery query for 'Analytics Event Schema Contract & Breaking-Change CI Gate' to establish baseline metrics and identify anomalies. 3. Generate a structured remediation or execution artifact with full source citations and diffs. 4. Stage any mutating actions behind an explicit human approval gate and verify final state. ### 4. Copy-Paste Agent Execution Prompt ```markdown Execute the 'Analytics Event Schema Contract & Breaking-Change CI Gate' (data-json-schema-registry-and-event-contract-gate) blueprint with PostHog MCP, GitHub MCP, Slack MCP. Goal: Validate PostHog and Segment tracking calls in PR diffs against a central JSON Schema registry so analytics pipelines never break. First inspect live state in read-only mode, validate all identifiers and metrics, and output a concrete action plan with verification commands before making any changes. ``` ### 5. Verification & Safety Guardrails - **Human-in-the-Loop Gate:** All external communications, production database mutations, and billing actions stage an explicit review diff before execution. - **Deterministic Telemetry:** Every run logs structured JSON output, latency metrics, and source citations so operators can audit every decision.
Tags: #posthog-mcp#github-mcp#slack-mcp#blueprint#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.