prod-debug SKILL.md skillA

prod-debug from josephfung/trimkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add josephfung/trimkit/prod-debug@git:20260919.010ef8a

Pins git:20260919.010ef8a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
josephfung/trimkit
Path
skills/prod-debug/SKILL.md
Versions recorded
5
Latest version
git:20260919.010ef8a, committed Sep 19, 2026
First version recorded
Apr 9, 2026
Size
7,830 bytes
Repository stars
3
License
MIT

Production debugging skill. Pre-loads DB schema, container registry, and prod environment facts from .claude/prod-debug/ in the current project root. Use when the user invokes /prod-debug or /prod-debug bootstrap.

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

# prod-debug

## Invocation

Two modes:

- `/prod-debug` — load context and enter debugging mode
- `/prod-debug bootstrap` — (re)build schema.md and containers.md from source files

---

## On `/prod-debug`

### Step 1: Find project root

Determine the project root — use the current working directory, or if inside a git repo, use `git rev-parse --show-toplevel`.

### Step 2: Check for data directory

Check whether `.claude/prod-debug/config.json` exists at the project root.

- If **missing**: tell the user that prod-debug is not set up for this project yet, and suggest running `/prod-debug bootstrap` after creating `.claude/prod-debug/config.json`.
- If **present**: continue to Step 3.

### Step 3: Load context files

Read all three data files using the Read tool:

1. `{project_root}/.claude/prod-debug/schema.md`
2. `{project_root}/.claude/prod-debug/containers.md`
3. `{project_root}/.claude/prod-debug/prod-env.md`

If any file is missing, note it and proceed with what's available.

### Step 4: Check schema staleness

Run:

```bash
~/.trimkit/bin/trimkit-prod-debug-staleness {project_root}
```
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add josephfung/trimkit/prod-debug@sha256:d964d3b81484c6bf

The line at the top of this page pins the label git:20260919.010ef8a, 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_e7epq2mjsjuhanyv.svg)](https://markdownregistry.com/a/art_e7epq2mjsjuhanyv)

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

Versions

The registry has recorded 5 versions of this file, between Apr 9, 2026 and Sep 19, 2026, about one every 41 days.

versioncommittedcommitsizeaudit
git:20260919.010ef8a latest2026-09-19 010ef8a 7,830 BA view · diff
git:20260918.6214a8c2026-09-18 6214a8c 7,714 BA view · diff
git:20260918.cf98f622026-09-18 cf98f62 7,414 BA view · diff
git:20260918.4c820242026-09-18 4c82024 7,390 BA view · diff
git:20260409.72830ea2026-04-09 72830ea 5,800 BA view

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 (7830 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

josephfung/trimkit · 3 stars · license MIT · pushed 2026-09-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_e7epq2mjsjuhanyv
GET https://markdownregistry.com/api/v1/resolve?ref=josephfung/trimkit/prod-debug
GET https://markdownregistry.com/api/v1/blob/d964d3b81484c6bfd523a36aaba55584a5260d57ffa7f0f186bcd10934af2ee5

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 josephfung/trimkit

sysops SKILL.md skill
josephfung/trimkit · skills/sysops/SKILL.md · Invoke the sysops subagent for VPS maintenance. Use when the user runs /sysops with an optional argument like "status"…
git:20260512.79d251a · audit A · 3 stars

Every file in josephfung/trimkit

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