configure-zymtrace-mcp SKILL.md skillA
configure-zymtrace-mcp 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/configure-zymtrace-mcp@git:20260715.fbd20f5Pins git:20260715.fbd20f5 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/configure-zymtrace-mcp/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260715.fbd20f5, committed Jul 15, 2026
- First version recorded
- May 19, 2026
- Size
- 13,780 bytes
- Repository stars
- 6
- License
- Apache-2.0
Use when connecting a coding agent — Claude Code, OpenAI Codex, or Cursor — to the zymtrace MCP server so the user can analyze CPU and GPU flamegraphs through natural-language queries. Walks through finding the gateway URL, generating an auth token (if service-token auth is on), adding the server with the right command for the user's client, and verifying the connection. This skill is plumbing only — the analytical workflow lives in `optimize-cpu-workloads` and…
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
# Configure zymtrace MCP
Helps the user connect their coding agent — **Claude Code, OpenAI Codex, or Cursor** — to their zymtrace backend's MCP server. Once connected, the user can analyze their CPU and GPU flamegraphs with natural-language queries — see [`optimize-cpu-workloads`](../optimize-cpu-workloads/SKILL.md) (CPU-only) or [`optimize-gpu-workloads`](../optimize-gpu-workloads/SKILL.md) (GPU) for the analytical workflow.
> The MCP server is part of the zymtrace backend itself — it lives at `<gateway-host>/mcp`. If the backend isn't installed and reachable yet, route to `install-zymtrace-backend` and `expose-zymtrace-backend` first.
**Which client?** The URL, token, and reachability steps are identical for every client; only the *add-the-server* command differs (Step 3–4). Detect the client from context — which agent is running this, or what the user says ("connect Codex", "Cursor") — and use that client's block. If unsure, ask: *"Claude Code, Codex, or Cursor?"*
## Greet the user
…Read the whole file at its exact version.
How to install
mdr add zystem-io/zymtrace-skills/configure-zymtrace-mcp@sha256:2194ba07bd3e2846The line at the top of this page pins the label git:20260715.fbd20f5, 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_7ho3onkqvuef6bxm)
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 Jul 15, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260715.fbd20f5 latest | 2026-07-15 | fbd20f5 | 13,780 B | A | view · diff |
| git:20260608.3b7bfd1 | 2026-06-08 | 3b7bfd1 | 12,246 B | A | view · diff |
| git:20260605.f5be030 | 2026-06-05 | f5be030 | 11,768 B | A | view · diff |
| v26.5.0 | 2026-06-03 | 96a7db9 | 11,976 B | A | view · diff |
| v26.5.0 | 2026-05-19 | 71c3238 | 9,696 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 (13780 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_7ho3onkqvuef6bxm GET https://markdownregistry.com/api/v1/resolve?ref=zystem-io/zymtrace-skills/configure-zymtrace-mcp GET https://markdownregistry.com/api/v1/blob/2194ba07bd3e284665466bab8ed0d39fba55e148ca054249191ff79b99a2a3f0
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.