weekly-production-review SKILL.md skillA

weekly-production-review from langfuse/langfuse is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add langfuse/langfuse/weekly-production-review@git:20261119.d535d56

Pins git:20261119.d535d56 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
langfuse/langfuse
Path
.agents/skills/weekly-production-review/SKILL.md
Versions recorded
6
Latest version
git:20261119.d535d56, committed Nov 19, 2026
First version recorded
Jun 15, 2026
Size
16,452 bytes
Repository stars
37,634
License
a license file GitHub does not identify

Prepare Langfuse weekly production reviews covering failures, fixes, open issues, and tracking gaps. Use for "what broke last week," production bugs, Datadog alerts or error patterns, incident.io activity, or pager load.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Weekly Production Review

Use this skill to produce a source-grounded production review across Datadog,
incident.io, and Linear. Keep the output factual, table-first, and easy to
audit from the linked source rows.

## Scope

- Default "last week" to the previous Monday through Sunday in the user's
  timezone. State both local and UTC query windows in one short scope line.
- Cover all production environments unless the user narrows scope:
  `prod-us`, `prod-eu`, `prod-hipaa`, and `prod-jp`.
- The review itself changes nothing outside the tracker. Do not touch incident.io
  records, follow-ups, alerts, monitors, files, Slack messages, or production
  systems unless the user explicitly asks after reviewing the findings.
- Linear is the exception: evidence comments on existing issues and new
  parentless filings both need a propose-then-write yes — show the set, take
  one go-ahead, then write and label. [`linear-agent-writes`](../linear-agent-writes/SKILL.md)
  is the authority; [`linear-bug-triage`](../linear-bug-triage/SKILL.md) applies
  it to measured findings.
- For chat-only reviews, avoid creating report artifacts or local analysis
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_522bhtboxyv2a7ky/94fd54aa59eb64faadbc1f267792aba978687daef63970e2eaa5e23ec562f940.json

Then /plugin install weekly-production-review@markdownregistry-522bhtboxyv2a7ky in Claude Code. It installs git:20261119.d535d56, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add langfuse/langfuse/weekly-production-review@sha256:94fd54aa59eb64fa

The line at the top of this page pins the label git:20261119.d535d56, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_522bhtboxyv2a7ky.svg)](https://markdownregistry.com/a/art_522bhtboxyv2a7ky)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in langfuse/langfuse/weekly-production-review since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of weekly-production-review from somewhere else? Ask it: where did my weekly-production-review come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 6 versions of this file, between Jun 15, 2026 and Nov 19, 2026, about one every 31 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261119.d535d56 latest2026-11-19 d535d56 16,452 BA view · diff
git:20260911.a85d3ec2026-09-11 a85d3ec 16,241 BA view · diff
git:20260904.0b8d7eb2026-09-04 0b8d7eb 16,303 BA view · diff
git:20260729.6d2988f2026-07-29 6d2988f 15,860 BA view · diff
git:20260716.50269e72026-07-16 50269e7 16,156 BA view · diff
git:20260615.95be2232026-06-15 95be223 15,607 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (16452 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

langfuse/langfuse · 37,634 stars · license a license file GitHub does not identify · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_522bhtboxyv2a7ky
GET https://markdownregistry.com/api/v1/resolve?ref=langfuse/langfuse/weekly-production-review
GET https://markdownregistry.com/api/v1/blob/94fd54aa59eb64faadbc1f267792aba978687daef63970e2eaa5e23ec562f940

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from langfuse/langfuse

AGENTS.md@.agents AGENTS.md file
langfuse/langfuse · .agents/AGENTS.md
git:20261105.a869249 · audit A · 37,634 stars
add-model-price SKILL.md skill
langfuse/langfuse · .agents/skills/add-model-price/SKILL.md · Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing…
git:20261006.39cb678 · audit A · 37,634 stars
add-to-dependabot-csv SKILL.md skill
langfuse/langfuse · .agents/skills/add-to-dependabot-csv/SKILL.md · Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after verifying their API…
git:20261002.3b02ae4 · audit A · 37,634 stars
agent-setup-maintenance SKILL.md skill
langfuse/langfuse · .agents/skills/agent-setup-maintenance/SKILL.md · Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared…
git:20260921.1357013 · audit A · 37,634 stars
analyze-cloud-costs SKILL.md skill
langfuse/langfuse · .agents/skills/analyze-cloud-costs/SKILL.md · Analyze Langfuse Cloud infrastructure cost structure using Metabase cost marts. Use when asked about cloud spend, AWS…
git:20260511.5e5ed8a · audit A · 37,634 stars
backend-dev-guidelines SKILL.md skill
langfuse/langfuse · .agents/skills/backend-dev-guidelines/SKILL.md · Build or review Langfuse backend code. Use for tRPC routers, public REST APIs, BullMQ processors, services, middleware…
git:20261105.4fa3d2e · audit B · 37,634 stars
changelog-writing SKILL.md skill
langfuse/langfuse · .agents/skills/changelog-writing/SKILL.md · Shared workflow for writing Langfuse changelog entries after a feature is complete. Use when a branch is ready for…
git:20260811.7617df6 · audit A · 37,634 stars
clickhouse-best-practices SKILL.md skill
langfuse/langfuse · .agents/skills/clickhouse-best-practices/SKILL.md · MUST USE when reviewing ClickHouse schemas, queries, or configurations. Contains 28 rules that MUST be checked before…
v0.3.0 · audit A · 37,634 stars
code-review SKILL.md skill
langfuse/langfuse · .agents/skills/code-review/SKILL.md · Review Langfuse code changes for correctness, regressions, and best practices.
git:20261004.c37160d · audit A · 37,634 stars
create-repo-agent SKILL.md skill
langfuse/langfuse · .agents/skills/create-repo-agent/SKILL.md · Design, implement, review, or harden Langfuse repo-owned autonomous agents. Use for LLM-powered GitHub Actions…
git:20260729.6d2988f · audit A · 37,634 stars
cursor-agents-workflow SKILL.md skill
langfuse/langfuse · .agents/skills/cursor-agents-workflow/SKILL.md · Human handoff, Linear branch names, reviewable (non-draft) PRs, the `cursor` GitHub label, Claude, Greptile, and Codex…
git:20261105.a869249 · audit A · 37,634 stars
datadog-query-recipes SKILL.md skill
langfuse/langfuse · .agents/skills/datadog-query-recipes/SKILL.md · Research Langfuse production telemetry with reusable Datadog queries. Use for tenant or project activity, API usage…
git:20261119.d535d56 · audit A · 37,634 stars

Every file in langfuse/langfuse

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.