troubleshoot-zymtrace-profiler SKILL.md skillA
troubleshoot-zymtrace-profiler 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-profiler@git:20261027.524bf2cPins git:20261027.524bf2c 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-profiler/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261027.524bf2c, committed Oct 27, 2026
- First version recorded
- May 19, 2026
- Size
- 18,869 bytes
- Repository stars
- 6
- License
- Apache-2.0
Use when the zymtrace profiler agent is misbehaving — pods crash-looping, image pull errors, OOMKilled, CPU profiles working but no GPU profiles, NVML library not found, PC sampling not producing SASS-level data, or license errors on the profiler side. Walks symptom → diagnosis → fix. Focused on the agent itself; for "no data anywhere" use troubleshoot-zymtrace-backend. Trigger phrases: "profiler not working", "profiler pods crashing", "profiler CrashLoopBackOff", "profiler ImagePullBackOff…
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 Profiler Helps the user diagnose problems with the **profiler agent** — the DaemonSet (or Docker / binary) that ships profiles to the backend. Backend / ClickHouse / ingest problems live in [`troubleshoot-zymtrace-backend`](../troubleshoot-zymtrace-backend/SKILL.md). If the customer's symptom is "the UI is empty" without a clearer signal, route there instead — it covers the cross-cutting "no data" diagnostic across both sides. ## Greet the user Open warmly. Diagnostic conversations start frustrated. > 👋 Sorry the profiler isn't behaving — let's track it down. Tell me what you're seeing (e.g. "agent pods CrashLoopBackOff", "CPU profiles arrive but no GPU traces", "OOMKilled every 5 min", "license rejected") and I'll walk the diagnosis with you. > > **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-profiler@sha256:8ab7ff14a3ad2b7dThe line at the top of this page pins the label git:20261027.524bf2c, 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_dpzzudfczpq5btbs)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 19, 2026 and Oct 27, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.524bf2c latest | 2026-10-27 | 524bf2c | 18,869 B | A | view · diff |
| git:20260605.f5be030 | 2026-06-05 | f5be030 | 16,765 B | A | view · diff |
| v26.5.0 | 2026-06-03 | 96a7db9 | 16,991 B | A | view · diff |
| v26.5.0 | 2026-05-30 | d71575d | 16,882 B | A | view · diff |
| v26.5.0 | 2026-05-19 | 71c3238 | 16,819 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 (18869 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_dpzzudfczpq5btbs GET https://markdownregistry.com/api/v1/resolve?ref=zystem-io/zymtrace-skills/troubleshoot-zymtrace-profiler GET https://markdownregistry.com/api/v1/blob/8ab7ff14a3ad2b7d108138da2cd022e4eaeb6e9cd5de64474813615cf8e2db1d
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.