AI Agent Skills & perf engineer subagents
zymtrace AI Agent Skills teach your AI coding assistant how to operate zymtrace — installing the backend and profiler, exposing the gateway, troubleshooting, and analyzing CPU/GPU flamegraphs through the MCP. Describe what you want in plain English and the assistant runs the right workflow, confirming each change with you.
The skills install from a single source into Claude Code, OpenAI Codex, and Cursor. Source and issues: github.com/zystem-io/zymtrace-skills.
Available skills
| Skill | What it does |
|---|---|
install-zymtrace-backend | Install the backend on Kubernetes (Helm) or Docker Compose. Handles license, databases, and air-gapped registries. |
upgrade-zymtrace-backend | Bump image tags, chart versions, or both — with built-in rollback and verification. |
expose-zymtrace-backend | Expose the gateway via NodePort, AWS ALB, NGINX Ingress, or cloud LoadBalancer, TLS included. |
install-zymtrace-profiler | Install the profiler on Kubernetes, Docker, or bare-metal. CPU + CUDA GPU profiling (CUDA 12.x+). |
troubleshoot-zymtrace-backend | Diagnose "no data appearing", license errors, ingest crashes, slow queries, and storage issues. |
troubleshoot-zymtrace-profiler | Diagnose agent-side failures — CrashLoopBackOff, OOMKilled, NVML missing, PC sampling, license rejected. |
configure-zymtrace-mcp | Connect your assistant to the zymtrace MCP server so you can analyze profiles with natural-language queries. |
analyze-zymtrace-workload | Investigate a GPU or CPU workload through the MCP — query metrics for context, pull GPU + matching CPU flamegraphs, and recommend a fix. It it finds a GitHub MCP, it locates the hot trace in your repo and offers to open a pull request. |
Available subagents
Subagents are currently only supported on Claude Code.
| Subagent | What it does |
|---|---|
zymtrace-perf-engineer | Autonomous, hands-off performance investigation. Identifies the entity (Python script, container, host, or Kubernetes pod/deployment), pulls its metrics, then the CPU flamegraph — and the GPU flamegraph for GPU workloads — and returns a finished recap without stopping to confirm each step. Run several in parallel to triage multiple workloads at once. |
Install the plugin
- Claude Code
- OpenAI Codex
- Cursor
claude plugin marketplace add zystem-io/zymtrace-skills
claude plugin install zymtrace@zymtrace-skills
Skills become available as /zymtrace:install-zymtrace-backend, /zymtrace:analyze-zymtrace-workload, and so on. Run /skills (and /agents for the subagent) to see what loaded.
codex plugin marketplace add zystem-io/zymtrace-skills
Then run /plugins in Codex and install zymtrace from the marketplace. The skills load on your next thread.
- Open Dashboard → Settings → Plugins.
- Under Team Marketplaces, click Import.
- Paste the repository URL
https://github.com/zystem-io/zymtrace-skillsand continue. - Review the parsed zymtrace plugin, set access as you like, and save.
Other tools
The plugin ships in the Claude Code plugin format, which several other assistants also read. The same marketplace works with them:
| Tool | Install |
|---|---|
| Augment (Auggie CLI) | auggie plugin marketplace add zystem-io/zymtrace-skills → auggie plugin install zymtrace@zymtrace-skills |
| GitHub Copilot CLI | copilot plugin install zystem-io/zymtrace-skills:zymtrace |
For any other MCP-capable assistant (Claude Desktop, Cline, Windsurf, Amazon Q Developer, VS Code + Copilot), you don't need the plugin to analyze profiles — connect the MCP endpoint directly. If the tool supports skills or rules, you can also copy the Markdown skill files from the repo's zymtrace/skills/ into its skills/rules directory.
Connecting to zymtrace
The analysis skills (analyze-zymtrace-workload, configure-zymtrace-mcp) and the zymtrace-perf-engineer subagent query live profiles through the zymtrace MCP server. The configure-zymtrace-mcp skill automates the connection; this section is the reference.
MCP endpoint
Your MCP endpoint is your zymtrace gateway URL + /mcp:
https://zymtrace.your-company.com/mcp
zymtrace is self-hosted, so this URL is specific to your deployment. See Configure MCP for the per-tool setup (Claude Code, Codex, Cursor).
Authentication
| Deployment | What's needed |
|---|---|
| Service-token auth off (default) | Nothing — the connection is open within any network that can reach the gateway. |
| Service-token auth on | A zymtrace service token, passed as a Bearer header. Generate one in the zymtrace UI (Settings → Service Tokens) — see Service Tokens. |
The token is always referenced from an environment variable (e.g. $ZYMTRACE_MCP_TOKEN, or ${env:ZYMTRACE_MCP_TOKEN} in Cursor's mcp.json); it is never written to disk in plaintext or pasted into the conversation. For production exposures behind an ALB / Ingress, service-token auth is recommended.