weekly-production-review

Generates weekly production reviews from incident.io, Linear, and Datadog sources.

34.0k|3.7k|Updated May 18, 2023
One-click install
npx skills add https://github.com/langfuse/langfuse --skill weekly-production-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-production-review
Source: https://github.com/langfuse/langfuse/tree/main/.agents/skills/weekly-production-review
Command: npx skills add https://github.com/langfuse/langfuse --skill weekly-production-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compiling a weekly production health review requires manually pulling incidents, pager load, bug tickets, alerts, and error logs from multiple observability and ticketing systems, then cross-referencing them into a consistent report.

Core Features & Use Cases

  • Multi-Source Aggregation: Gathers incident.io incidents and alert load, Linear bug tickets, Datadog alert clusters, and Datadog error log patterns for a defined weekly window.
  • Structured Output Contract: Produces exactly five source tables (incident.io, incident.io Alert Load, Linear Bugs, Datadog Alerts, Datadog Logs) with defined column schemas and classification rules.
  • Cross-Source Linking: Deduplicates against Linear and links Datadog evidence to incidents and bugs so repeated issues are not reported as new.
  • Use Case: An on-call lead asks "what broke last week" and receives a read-only, table-first review covering prod-us, prod-eu, prod-hipaa, and prod-jp with per-engineer pager load and deep-dived alert clusters.

Quick Start

Use the weekly-production-review skill to prepare a production review of last week's incidents, pager load, Linear bugs, Datadog alerts, and error log patterns.

Frequently Asked Questions about weekly-production-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly production review from Datadog and incident.io?

Invoke the skill with a request like "what broke last week" and it queries incident.io incidents and alert load, Linear bug tickets, Datadog alert clusters, and error log patterns for the previous Monday-to-Sunday window, returning five structured tables.

What data sources does the weekly production review use?

It uses incident.io for incidents and pager/alert load, Linear for bug-labeled tickets, and Datadog for monitor alerts, APM traces, spans, and error log patterns across production environments.

Does the skill create or update Linear issues or incidents?

No. The first pass is strictly read-only. It never creates or updates Linear issues, incident.io records, Datadog monitors, or Slack messages unless the user explicitly approves a write-back after reviewing findings.

How is on-call pager load broken down by engineer?

Alert load is grouped per paged engineer into incident.io UTC time-of-day buckets: working hours (09:00-18:00 weekdays), late evening (18:00-23:00 plus weekend daytime), and overnight (23:00-09:00), with totals and share percentages.

What happens when a Datadog signal cannot be measured?

The skill writes "No measurements found" for any signal that cannot be queried, and classifies unclear rows as "unclear" or "unknown/no measurements" instead of dropping them from the tables.