optimize-cpu-workloads SKILL.md skillA
optimize-cpu-workloads 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/optimize-cpu-workloads@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/optimize-cpu-workloads/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.524bf2c, committed Oct 27, 2026
- First version recorded
- Jun 8, 2026
- Size
- 17,076 bytes
- Repository stars
- 6
- License
- Apache-2.0
Analyze CPU performance with zymtrace on CPU-only deployments (no GPUs) — rank the top CPU consumers (which process/function/container/host/pod is hottest), find what's eating CPU, pick the biggest-ROI app to optimize, or read a CPU flamegraph. The zymtrace MCP pulls the data (rankings, host metrics, flamegraphs); YOU analyze — name the hot stacks, identify the pattern (lock contention, allocation churn, serialization, GC, syscall-heavy), then recommend AND apply the fix in the user's source…
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
# Optimize CPU Workloads > The MCP fetches the data — hot traces, flamegraphs, host metrics, top functions, top entities; **you** analyze: name the hot stacks, identify the pattern, recommend and apply the fix. **For CPU-only deployments.** This skill stays entirely on the CPU side — no GPU view, no GPU metrics, no inference-server (vLLM/SGLang/Triton) framing. A CPU-only customer never needs any of that. **Running GPU workloads?** Use [`optimize-gpu-workloads`](../optimize-gpu-workloads/SKILL.md) instead — there, cross-checking the GPU and CPU sides together is the load-bearing step. The common discipline — data-source policy, pre-flight, rank-first vs. drill-down, scope-to-own-code/ROI, the always-recommend-and-apply-the-fix rule, the output-template skeleton, severity sizing, and security — lives in [`shared/analysis-conventions.md`](../../shared/analysis-conventions.md). **Read it.** This skill adds the CPU-specific profiles and call-tree rendering on top. Connection setup lives in [`configure-zymtrace-mcp`](../configure-zymtrace-mcp/SKILL.md); this skill assumes the MCP is connected. ## Standard starter prompts (for users who don't know what to ask) …
Read the whole file at its exact version.
How to install
mdr add zystem-io/zymtrace-skills/optimize-cpu-workloads@sha256:e9febce84904d02cThe 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_jbqvgix537zhdzga)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 8, 2026 and Oct 27, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.524bf2c latest | 2026-10-27 | 524bf2c | 17,076 B | A | view · diff |
| git:20260715.fbd20f5 | 2026-07-15 | fbd20f5 | 14,479 B | A | view · diff |
| git:20260608.3b7bfd1 | 2026-06-08 | 3b7bfd1 | 14,486 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 (17076 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_jbqvgix537zhdzga GET https://markdownregistry.com/api/v1/resolve?ref=zystem-io/zymtrace-skills/optimize-cpu-workloads GET https://markdownregistry.com/api/v1/blob/e9febce84904d02c49609cf95e7a89c904580921780be14fe4bd5d236ce8c0ae
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.