Rocprofiler Systems Choosing a Profiling Preset

Recommends which rocprofiler-systems runtime profiling preset (balanced, trace-gpu, trace-hpc, sys-trace, workload-trace, etc.) to pass to `rocprof-sys-run --preset=<name>` or `rocprof-sys-sample --preset=<name>` based on the user's workload and profiling goal, and returns the ready-to-run command. Use when the user asks "which preset should I use", describes a workload (GPU kernel, MPI, OpenMP, AI/ML training, production overview) and wants profiling guidance, or invokes `rocprof-sys-run`/`rocprof-sys-sample` without picking a preset. Do NOT use for CMake build presets (`cmake --preset debug|

500 stars 47 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add amd/skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add amd/skills --skill rocprofiler-systems-choosing-a-profiling-preset
Manual install
git clone --depth 1 https://github.com/amd/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/rocprofiler-systems-choosing-a-profiling-preset ~/.claude/skills/rocprofiler-systems-choosing-a-profiling-preset

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Choosing a Profiling Preset

Recommends one of rocprofiler-systems' built-in runtime profiling presets for a
described workload, and returns the exact command to run it.

## Prerequisites

None to make a first recommendation from the table below. To confirm what a preset
sets (see "Confirm with `--explain`"), and to run the command, `rocprof-sys-run` or
`rocprof-sys-sample` must be installed or built.

## Version check

Presets need ROCm Systems Profiler **1.6.0 or newer** (ROCm 7.13.0). Check with
`rocprof-sys-run --version`, whose first line reads `rocprof-sys-run v<major>.<minor>.<patch> ...`.

| Installed version | What to tell the user |
| --- | --- |
| 1.6.0 or newer | `--preset=<name>`, `--list-presets` and `--explain=<name>` all work. |
| 1.5.x (ROCm 7.12.0) | Presets exist only as `--<name>` flags (for example `--balanced`), with no `--preset=`, `--list-presets` or `--explain`. Give that form and suggest upgrading. |
| Older than 1.5.0 | No presets. Suggest upgrading, or configure settings by hand. |

A newer preset name may be missing from an older build, so `--list-presets` is the list
of what the installed version supports. If the version cannot be checked, give the
`--preset=` command and say it needs 1.6.0 or newer.

## Terminology

"Trace" and "tracing" mean two different things here. Keep them apart in every answer.

| Term | Meaning | Setting |
| --- | --- | --- |
| Perfetto trace output | Writes a timeline file in Perfetto format | `ROCPROFSYS_TRACE` |
Read the full skill on GitHub

Details

Skill name
rocprofiler-systems-choosing-a-profiling-preset
Repository
amd/skills
Path
skills/rocprofiler-systems-choosing-a-profiling-preset/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Rocprofiler Systems Choosing a Profiling Preset skill do?

Recommends which rocprofiler-systems runtime profiling preset (balanced, trace-gpu, trace-hpc, sys-trace, workload-trace, etc.) to pass to `rocprof-sys-run --preset=<name>` or `rocprof-sys-sample --preset=<name>` based on the user's workload and profiling goal, and returns the ready-to-run command. Use when the user asks "which preset should I use", describes a workload (GPU kernel, MPI, OpenMP, AI/ML training, production overview) and wants profiling guidance, or invokes `rocprof-sys-run`/`rocprof-sys-sample` without picking a preset. Do NOT use for CMake build presets (`cmake --preset debug|

How do I install the Rocprofiler Systems Choosing a Profiling Preset skill?

Claude Code plugin: /plugin marketplace add amd/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Rocprofiler Systems Choosing a Profiling Preset popular?

It lives in amd/skills, which has 500 GitHub stars and 47 forks.

Related skills

Apu Memory Tuner

500

amd/skills

Inspects and tunes the shared-vs-dedicated memory split on AMD Ryzen APUs with unified memory (UMA) so larger LLMs and image-gen models fit on the iGPU, or so reserved GPU memory is returned to the CPU. Use when the user mentions Ryzen AI, Strix Halo / Strix Point / Krackan / Phoenix / Hawk Point, Ryzen AI Max, gfx1150 / gfx1151 / gfx1152, integrated Radeon, iGPU memory, UMA Frame Buffer Size, AMD Variable Graphics Memory, VGM, GTT, GART, TTM, pages_limit, amd-ttm, amd-debug-tools, "shared GPU memory", "dedicated GPU memory", carve-out, "not enough VRAM", "out of VRAM", "GPU OOM", llama.cpp on

Productivity & Notes47

Eaiapps Guided Install

500

amd/skills

Guides a user through installing the AI Workbench (AIWB) onto a Kubernetes cluster end-to-end — preflight cluster readiness (access, StorageClass, GPU operator, required operators/CRDs), install the Helm charts in the correct order, and verify the deployment is healthy with plain-language failure triage. Use when a user wants to install, deploy, or stand up AIWB / the AI Workbench / the enterprise AI stack on a K8s cluster, or asks why their install failed partway. Use PROACTIVELY when a user is following helm/INSTALL.md by hand. Do NOT activate for onboarding models to AIM, general kubectl/he

DevOps & Cloud47

Flydsl Kernel Authoring

500

amd/skills

Comprehensive reference for authoring FlyDSL GPU kernels on AMD GPUs. Covers the layout algebra, tiled copy/MMA, buffer ops, loop-carried range loops, SharedAllocator (LDS), autotuning, and common patterns. Use when writing, reviewing, or understanding FlyDSL kernel code.

Writing & Content47

Serving Llms on Epyc

500

amd/skills

Serves an LLM on a supported AMD EPYC server CPU using vLLM with zentorch, in Docker, Podman, or conda. Use for "vLLM on CPU", "zentorch serving", or an EPYC CPU endpoint, including on a host that also has AMD Instinct GPUs. Detects the EPYC generation, validates the runtime, checks model support and RAM fit, sizes threads/KV/NUMA, confirms the plan, launches, and verifies the endpoint. Runs one instance on one socket and its memory. Reports and stops on failure; does not retry or debug. Use serving-llms-on-instinct when the endpoint should run on a GPU. Excludes multi-node, EPYC 4000, and pre

AI, LLMs & Agents47

Quark Torch LLM Ptq

500

amd/skills

Runs an end-to-end AMD Quark post-training quantization workflow for PyTorch / Hugging Face LLMs: inspect a Hub or local model, choose a quantization plan, create reproducible artifacts, request execution approval, and produce a quantized model. Applies to Llama, Qwen, Mistral, and similar transformer LLM requests involving FP8, INT4, or another Quark scheme. Does not handle .onnx model inputs or ONNX PTQ.

AI, LLMs & Agents47

Serving Llms on Instinct

500

amd/skills

Serves AI models on AMD Instinct GPU hardware using vLLM. Use this skill whenever the user wants to run, serve, deploy, start, host, or launch a language model on an AMD GPU, AMD Instinct, MI300X, MI325X, MI350X, or MI355X. Also use when the user mentions vLLM on ROCm, vLLM on AMD, serving on HBM, or asks how to get a model running on AMD data center hardware. Use when the user asks "run Qwen3", "serve DeepSeek", "start a vLLM endpoint", "get a model running on my AMD machine", or any similar phrasing. Handles the full flow: GPU detection, environment validation, vLLM configuration, launch, an

AI, LLMs & Agents47

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.