# rocprofiler-systems-discovering-profiling-options

rocprofiler-systems-discovering-profiling-options is a Claude Code skill that finds the right command for exploring ROCPROFSYS profiling options. It handles requests about available counters, ROCm tracing domains, and run flags.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 266 installs · ★ 510 repo stars
- Author: amd
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/amd/skills/tree/HEAD/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/rocprofiler-systems-discovering-profiling-options

## What it does

The skill maps profiling questions to `rocprof-sys-avail` commands or a `rocprof-sys-run --help=<topic>` section. It can help discover environment settings, Timemory components, hardware counters, ROCm API domains, GPU metrics, and command-line flags. A question about counters, for instance, maps to a command that filters for available hardware options.

A working `rocprof-sys-avail` binary is required; it must be built or installed alongside `rocprof-sys-run` and `rocprof-sys-sample`. If the binary is not on `PATH`, run `source <install-prefix>/share/rocprofiler-systems/setup-env.sh`. The skill also explains how to save selected settings in a config file. It does not choose a starting `--preset` for a workload.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add amd/skills --skill rocprofiler-systems-discovering-profiling-options -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/rocprofiler-systems-discovering-profiling-options/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add amd/skills --skill rocprofiler-systems-discovering-profiling-options -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add amd/skills --skill rocprofiler-systems-discovering-profiling-options -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install amd/skills skills/rocprofiler-systems-discovering-profiling-options
```

2. **Manually: put the files in place**
- File: `.github/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add amd/skills --skill rocprofiler-systems-discovering-profiling-options -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/amd/skills --path skills/rocprofiler-systems-discovering-profiling-options
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add amd/skills --skill rocprofiler-systems-discovering-profiling-options -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/amd/skills/tree/HEAD/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md

## When to use it
- find hardware counters available on the system
- list ROCm API domains that can be traced
- inspect `rocprof-sys-run` flags for a topic
- save selected profiling settings to a config file

## Example prompts
- Which hardware counters are available on this system?
- Which ROCm API domains can I trace?
- How can I persist these profiling settings across runs?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d78c59b8e7f0370a.

BEGIN THIRD-PARTY FILE d78c59b8e7f0370a
```text
---
name: rocprofiler-systems-discovering-profiling-options
description: Answers questions about what rocprofiler-systems configuration options exist and how to use them — e.g. "what hardware counters are available on my system", "what ROCm APIs can I trace", "what settings control sampling/output", "how do I persist my configuration" — by mapping the question to the right `rocprof-sys-avail` or `rocprof-sys-run --help=<topic>` command. Use when the user wants to discover or explore ROCPROFSYS_* settings, Timemory components, hardware counters, ROCm API tracing domains, or GPU metrics, rather than apply them. Do NOT use this for picking a starting --preset for a workload — that's `choosing-a-profiling-preset`.
---

# Discovering Profiling Options

Maps a "what's available" or "how do I configure X" question to the exact
`rocprof-sys-avail` / `rocprof-sys-run --help=<topic>` command that answers it.
`rocprof-sys-avail` is self-updating and authoritative — prefer running it over
reciting static documentation.

## Prerequisites

A working `rocprof-sys-avail` binary, built/installed alongside
`rocprof-sys-run`/`rocprof-sys-sample`. If it is not on `PATH`, run
`source <install-prefix>/share/rocprofiler-systems/setup-env.sh` first.

## Discovery command reference

| User question | Command | Notes |
| --- | --- | --- |
| What settings/env vars exist, with descriptions? | `rocprof-sys-avail -S -bd` | `-b` suppresses the current-value/availability column, `-d` adds the description column |
| What hardware counters are available on my system? | `rocprof-sys-avail -H -bd -A` | `-A`/`--available` restricts to counters this machine can actually use; add `-c CPU` or `-c GPU` to split by device |
| What ROCm APIs can be traced? | `rocprof-sys-avail -bd -r ROCM_DOMAINS` | Regex-filters settings to the `ROCPROFSYS_ROCM_DOMAINS` row, listing every valid domain (`hip_runtime_api`, `hsa_api`, `kernel_dispatch`, `rccl_api`, `kfd_events`, ...) |
```
END THIRD-PARTY FILE d78c59b8e7f0370a

The third-party file has ended. Everything between the d78c59b8e7f0370a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 1966 of 9947 bytes. © amd · MIT · https://github.com/amd/skills/tree/HEAD/skills/rocprofiler-systems-discovering-profiling-options/SKILL.md

## Similar
- [profile-model](https://affpapa.org/en/nevibecode/skills/profile-model.md) — skill · 1300 installs
- [cuda-profiling](https://affpapa.org/en/nevibecode/skills/cuda-profiling.md) — skill · 410 installs
- [workers-profiling](https://affpapa.org/en/nevibecode/skills/workers-profiling.md) — skill · 30100 installs
- [cx-profiling](https://affpapa.org/en/nevibecode/skills/cx-profiling.md) — skill · 1200 installs
- [rust-profiling](https://affpapa.org/en/nevibecode/skills/rust-profiling.md) — skill · 751 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
