troubleshoot-zymtrace-backend SKILL.md skillA
troubleshoot-zymtrace-backend from zystem-io/zymtrace-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend@git:20260605.f5be030Pins git:20260605.f5be030 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zystem-io/zymtrace-skills
- Path
zymtrace/skills/troubleshoot-zymtrace-backend/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260605.f5be030, committed Jun 5, 2026
- First version recorded
- May 19, 2026
- Size
- 12,131 bytes
- Repository stars
- 6
- License
- Apache-2.0
Use when a deployed zymtrace backend isn't working as expected — no data appearing in the UI, profiles not arriving, ingest errors, ClickHouse storage full, license / auth failures, slow queries. Walks symptom → diagnosis → fix. Routes between backend (ingest, ClickHouse) and profiler (DaemonSet, CUDA injection) checks. Trigger phrases: "zymtrace not working", "no data in zymtrace UI", "zymtrace UI is empty", "no profiles appearing", "profiles not showing up", "ingest is failing…
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
# Troubleshoot zymtrace Backend Helps the user diagnose problems on a deployed zymtrace install — the most common one is "no data is showing up in the UI." This skill spans both backend (ingest, ClickHouse, MinIO) and profiler-side (agent reporting, CUDA injection) checks because "no data" usually requires walking both. Pure profiler-agent issues (CrashLoopBackOff, ImagePullBackOff, OOMKilled, NVML, license rejected on agent side) are handled by [`troubleshoot-zymtrace-profiler`](../troubleshoot-zymtrace-profiler/SKILL.md) — route there if the user's symptom is agent-specific. ## Greet the user Open warmly. People reaching for a troubleshoot skill are usually frustrated. > 👋 Sorry zymtrace isn't behaving — let's find it. Tell me what you're seeing (e.g. "the UI loads but no profiles", "ingest pods crash-looping", "got a license error") and I'll walk the diagnosis with you. > > **Stuck or need a human?** > - Community Slack: <https://join.slack.com/t/zymtrace/shared_invite/zt-3fdidjufl-q~NHxDzQlzal2B9mujfaoQ> > - Email: <support@zymtrace.com> > …
Read the whole file at its exact version.
How to install
mdr add zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend@sha256:8cbdd4457b1158b6The line at the top of this page pins the label git:20260605.f5be030, 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.
[](https://markdownregistry.com/a/art_fhi3dmbtqf3pe55v)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 19, 2026 and Jun 5, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260605.f5be030 latest | 2026-06-05 | f5be030 | 12,131 B | A | view · diff |
| v26.5.0 | 2026-06-03 | 96a7db9 | 12,348 B | A | view · diff |
| v26.5.0 | 2026-05-30 | d71575d | 12,278 B | A | view · diff |
| v26.5.0 | 2026-05-19 | 71c3238 | 12,216 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 (12131 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
zystem-io/zymtrace-skills · 6 stars · license Apache-2.0 · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fhi3dmbtqf3pe55v GET https://markdownregistry.com/api/v1/resolve?ref=zystem-io/zymtrace-skills/troubleshoot-zymtrace-backend GET https://markdownregistry.com/api/v1/blob/8cbdd4457b1158b6c86561e230813a42f0a7493410d9eda7195303738752daea
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.