prod-debug skillA
prod-debug is agent-read markdown (skill) from josephfung/trimkit: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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
mdr add josephfung/trimkit/prod-debug@git:20260919.010ef8amdr add josephfung/trimkit/prod-debug@sha256:d964d3b81484c6bfPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_e7epq2mjsjuhanyv)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.010ef8a latest | 2026-09-19 | 010ef8a | 7,830 B | A | view · diff |
| git:20260918.6214a8c | 2026-09-18 | 6214a8c | 7,714 B | A | view · diff |
| git:20260918.cf98f62 | 2026-09-18 | cf98f62 | 7,414 B | A | view · diff |
| git:20260918.4c82024 | 2026-09-18 | 4c82024 | 7,390 B | A | view · diff |
| git:20260409.72830ea | 2026-04-09 | 72830ea | 5,800 B | A | view |
Audit of the latest version
- 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
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 agent 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.