Official agent skill

Compileiq Debug

by NVIDIA in NVIDIA/CompileIQ

A skill your agent uses when something is wrong: Search() hangs, all evaluations return INVALIDSCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is…

OfficialApache-2.0Auto-check: notesAI & LLM Engineering

Install Compileiq Debug

skills CLI
$ npx skills add NVIDIA/CompileIQ --skill compileiq-debug -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NVIDIA/CompileIQ compileiq-debug --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/compileiq-debug .claude/skills/compileiq-debug && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
compileiq-debug
GitHub stars
137
Token cost
~2.9k tokens
SKILL.md length
1,038 words
Files
2 (incl. scripts)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when something is wrong: Search() hangs, all evaluations return INVALIDSCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is…

  • Works in 3 steps: CIQ_SOCKET_TIMEOUT too low. Default is… → Release-backed search-space fetch is… → forkserver is unsupported on the host.…
  • Something is wrong: Search() hangs
  • SKILL.md covers Symptom table, Details, CIQ_KEEP_CACHE for post-mortem and Diagnose from the dump_results…, plus 4 more sections
  • Runs Python scripts from its folder; calls python, gh and bash

What it does

Compileiq Debug is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use when something is wrong: Search() hangs, all evaluations return INVALIDSCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is too high, or a winning ACF candidate needs NCU profiling to explain. Symptom-indexed table on top. Triggers on "compileiq hang", "socket timeout", "INVALIDSCORE", "not converging", "every score is the same", "TypeError fromhex", "ncu profile", "register spill", "ptxas error", "not in expected format", "high cv".

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/diagnose_csv.py`).

It sits in AI & LLM Engineering. It works with NVIDIA AI Platform and CUDA. The repository describes itself as: An Optimizer for Nvidia Compilers. The licence is Apache-2.0.

When your agent uses it

  • Something is wrong: Search() hangs
  • All evaluations return INVALIDSCORE
  • Scores arent improving
  • Every config returns the same number

Example prompts

  • “compileiq hang”
  • “socket timeout”
  • “INVALIDSCORE”
  • “/compileiq-debug”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Bash, Read

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. CIQ_SOCKET_TIMEOUT too low. Default is 20 seconds, which is fine for
  2. Release-backed search-space fetch is slow or blocked. First call to
  3. forkserver is unsupported on the host. Set CIQ_PROCESS_MODE=spawn.

What it can do on your machine

Read from SKILL.md and the folder at commit 743aca4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • gh
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Compileiq Debug loads about 2.9k tokens when it runs. Until then it costs about 128 tokens; SKILL.md has 1,038 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~128
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from NVIDIA/CompileIQ at commit 743aca4, republished under its Apache-2.0 licence (© NVIDIA). 1,038 words, ~2,877 tokens.

Download SKILL.mdSave it as .claude/skills/compileiq-debug/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
compileiq-debug
description
Use when something is wrong: Search() hangs, all evaluations return INVALID_SCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is too high, or a winning ACF candidate needs NCU profiling to explain. Symptom-indexed table on top. Triggers on "compileiq hang", "socket timeout", "INVALID_SCORE", "not converging", "every score is the same", "TypeError fromhex", "ncu profile", "register spill", "ptxas error", "not in expected format", "high cv".
allowed-tools
Bash, Read
when_to_use
- User reports any unexpected behavior from Search() or its results. - User wants to NCU-profile a winning ACF to understand WHY it helps. - High CV% on…
license
Apache-2.0
metadata.version
1.0.0
metadata.author
NVIDIA CompileIQ
metadata.domain
compiler-optimization
paths
**/*.py, **/*.csv, **/*.ptx, **/*.acf

compileiq-debug

A symptom-indexed cheat sheet. Find the row that matches what the user is seeing, follow the first action, then dig into the matching detail section.

Symptom table

SymptomMost-likely causeFirst action
Search hangs on first eval; socket timeoutSearch space too large for default CIQ_SOCKET_TIMEOUT=20; OR release fetch slow/blocked; OR forkserver issueRaise CIQ_SOCKET_TIMEOUT=120; if still hangs, CIQ_SEARCH_SPACES_DIR=<local mirror>; if still hangs, CIQ_PROCESS_MODE=spawn. Do NOT symlink BLAS — that fix is obsolete
Every eval returns INVALID_SCOREReturn-type mismatch (tuple vs scalar) / correctness gate / task_timeout too tightSearch.sample(1) + call objective by hand; check num_objectives vs return shape; raise task_timeout
Every eval returns the same scoreACF not reaching the compiler — framework cache is hiding itApply Debug-pack O0 ACF by hand; if the score doesn't regress, fix cache-bust (TRITON_ALWAYS_COMPILE=1, HELION_SKIP_CACHE=1, fresh TRITON_CACHE_DIR, drop FlashInfer cubin packages)
TypeError: fromhex() … not dictLegacy bytes.fromhex(config_blob) in objectiveReplace with save_compiler_config(acf_path, config) — see compileiq-author-objective
"not in expected format"Objective returned wrong shapenum_objectives must equal len(return_tuple); scalar return only when num_objectives=1
Convergence stalled (best score flat)Pool too small for space; mutate_rate too low; or kernel near-optimalRaise pool_size; raise mutate_rate; sample diversity with Search.sample(20)
Increasing invalid rate over generationsMutation arm spreading; compiler version drift mid-runCIQ_KEEP_CACHE=1, re-run, inspect failing configs offline
CV% > 10% on validationUnlocked clocks / thermal throttling / GPU contentionLock GPU + memory clocks; pin CUDA_VISIBLE_DEVICES; watch nvidia-smi dmon for thermals
Need to know why a winning ACF helpsProfile with NCUSee NCU section below

Details

Socket timeout / hang on first eval

Not BLAS. Do not send users to symlink libblas.so.

Current shipped binaries link only libm/libc/libstdc++/libgcc_s and do not require BLAS/LAPACK.

Real causes today, in order of frequency:

  1. CIQ_SOCKET_TIMEOUT too low. Default is 20 seconds, which is fine for small search spaces but fails on big ones. Raise to 120 first; raise to 300+ for very large spaces.
  2. Release-backed search-space fetch is slow or blocked. First call to PtxasSearchSpace().retrieve() downloads from github.com. On a corporate firewall this can stall. Pre-stage the mirror:
    bash
    gh release download search-spaces-latest -R NVIDIA/CompileIQ -D /shared/mirror
    export CIQ_SEARCH_SPACES_DIR=/shared/mirror
  3. forkserver is unsupported on the host. Set CIQ_PROCESS_MODE=spawn. IsoMultiProcessWorker already uses fork by default.
Every eval returns INVALID_SCORE

Sanity-check the shape before assuming the worst:

python
sample = tuner.sample(1)[0]
score = objective(sample)
print(type(score), score)

Common shape mismatches:

  • num_objectives=1 but objective returns a tuple (latency,). Drop the trailing comma.
  • num_objectives=2 but objective returns a scalar.
  • Correctness gate is rejecting everything because the reference call itself is wrong.
  • task_timeout is shorter than a clean compile takes; raise it.
Every eval returns the SAME score

Almost always a framework cache serving a stale binary. Run the O0/O3 canary from the Debug pack to confirm — see compileiq-booster-pack for the exact test. If O0 doesn't regress vs baseline, the ACF is not reaching PTXAS. Fix:

FrameworkCache-bust
TritonTRITON_ALWAYS_COMPILE=1 + unique TRITON_CACHE_DIR per eval
HelionHELION_SKIP_CACHE=1
FlashInferConfirm flashinfer_cubin and flashinfer_jit_cache packages are absent (docs/flashinfer_booster.md:56-64)
Raw nvccClean the build dir between candidates
TypeError around fromhex

Legacy pattern from the pre-2026 skill set:

python
# OLD — DO NOT USE
def objective(config_blob):
    with open(tmp_path, "wb") as f:
        f.write(bytes.fromhex(config_blob))
    ...

Replace with:

python
from compileiq.utils.helpers import save_compiler_config

def objective(config: str):
    save_compiler_config(tmp_path, config)
    ...

save_compiler_config does the bytes.fromhex internally. See compileiq-author-objective for the full pattern.

"Not in expected format"

The objective returned a shape CompileIQ's core doesn't expect. Rules:

  • num_objectives=1: objective must return a single scalar (int | float). Not a 1-tuple, not a list.
  • num_objectives>=2: objective must return a tuple or list of that length.
python
result = objective(sample)
assert (
    (search_config.num_objectives == 1 and isinstance(result, (int, float)))
    or (search_config.num_objectives  > 1 and len(result) == search_config.num_objectives)
), f"shape mismatch: {result!r} vs num_objectives={search_config.num_objectives}"
Convergence stalled

Three causes, in order:

  1. Pool too small for the space. pool_size = max(2 * num_objectives + 1, 32) is the auto-derived floor — for spaces with >1k design points, raise to 64-128.
  2. Mutation rate too low. Default mutate_rate=0.25. Raise to 0.3-0.5 if the search is converging on the first generation.
  3. The kernel is genuinely near-optimal. Verify by running Search.sample(20) and timing each sample by hand — if the spread is <5%, the search space is shallow.
Show full SKILL.md (425 more words)Show less
Increasing invalid rate

Probably a mutation arm spreading a structurally-bad config across the population. Re-run with CIQ_KEEP_CACHE=1 so the failing configs are preserved at ~/.cache/compileiq/, then replay them by hand to identify the common factor.

High CV% on validation

If cv = std/mean > 10%, validation can't tell the signal from the noise.

Fixes, in order:

  1. Lock GPU and memory clocks (see compileiq-run-search for the nvidia-smi --lock-*-clocks snippet).
  2. Pin CUDA_VISIBLE_DEVICES=<gpu> so the validation has the GPU to itself.
  3. Watch nvidia-smi dmon -i <gpu> -s pucvm for thermal throttling events.
  4. Raise warmup count (50 → 100) and trial count (100 → 200).
  5. Switch from cudaEvent to NVBench (entropy-based stopping criterion, cold-cache between samples).

CIQ_KEEP_CACHE for post-mortem

When a search misbehaves, re-run with:

bash
export CIQ_KEEP_CACHE=1

The cache at ~/.cache/compileiq/ is preserved after the run. You can:

  • Inspect each generation's serialized configs.
  • Replay a specific config without paying for a whole new search.
  • Compare two runs by diffing their cache directories.

Diagnose from the dump_results CSV

Quick pandas snippet:

python
import pandas as pd
df = pd.read_csv("results.csv")
df["score_numeric"] = pd.to_numeric(df["score_1"], errors="coerce")

gen_summary = df.groupby("generation").agg(
    n=("score_numeric", "size"),
    invalid=("score_numeric", lambda s: s.isna().sum() + (s > 1e10).sum()),
    best=("score_numeric", "min"),
)
print(gen_summary)

If invalid doesn't decrease across generations, your search is structurally broken — try the O0/O3 canary in compileiq-author-objective.

For an automated version: python scripts/diagnose_csv.py results.csv.

NCU section (replaces old /compileiq-profile)

Profile only after a validated ACF candidate exists. Don't profile every config — it's slow.

Two-shot pattern
bash
# Baseline (no ACF)
ncu --set full -o baseline -f --kernel-name my_kernel python bench.py

# ACF-applied — match the injection your objective uses
# Raw PTXAS:
ncu --set full -o opt -f --kernel-name my_kernel \
    bash -c 'PTXAS_OPTIONS="--apply-controls=best.acf" python bench.py'
# NVCC build:
nvcc -Xptxas --apply-controls=best.acf bench.cu -o bench && \
    ncu --set full -o opt -f --kernel-name my_kernel ./bench

# Diff
ncu --import baseline.ncu-rep --import opt.ncu-rep --csv --page raw > diff.csv
Five metrics that explain most CompileIQ wins
MetricWhat it means
sm__throughput.avg.pct_of_peak_sustained_elapsedCompute throughput
gpu__compute_memory_throughput.avg.pct_of_peak_sustained_elapsedMemory throughput
sm__warps_active.avg.pct_of_peak_sustained_activeAchieved occupancy
launch__registers_per_threadRegister pressure
l2__throughput.avg.pct_of_peak_sustained_elapsedL2 pressure

If the ACF moved any of these meaningfully, that's the mechanism. If none of them moved but the win is real, look at lower-level metrics (warp stalls, issue slot utilization) — those are harder to interpret but often the answer.

Register-spill check (no NCU needed)
bash
ptxas -v -arch=sm_100 --apply-controls best.acf kernel.ptx 2>&1 \
    | grep -E "registers|spill|stack"

Reports Used N registers, X bytes stack frame, Y bytes spill stores, Z bytes spill loads. If Y + Z goes up vs baseline, the ACF traded register pressure for memory traffic — sometimes a real win, sometimes not. Investigate before shipping.

Self-test

bash
python scripts/diagnose_csv.py --self-test

Synthesizes a small results.csv covering each pathology (clean convergence, rising invalid rate, stalled best-score) and asserts the heuristic classifications match.

Explicitly dropped from this skill (vs old /compileiq-debug + /compileiq-profile)

  • BLAS symlink section — obsolete; current binaries don't link BLAS (verified by ldd). Carrying it forward sends users on a wild goose chase.
  • Verbose COMMON_PTXAS_ERRORS dict mapping individual ptxas error strings to fixes — users get INVALID_SCORE instead, no need to recognize specific messages.
  • Duplicate CUDA 13.3+ check — lives in compileiq-bootstrap.
  • validate_objective_function introspection helper — replaced by Search.sample(1) + the Debug-pack O0/O3 canary.

Next

  • For the canary itself: compileiq-booster-pack or compileiq-author-objective.
  • For environment issues: compileiq-bootstrap.
  • After fixing: re-run compileiq-run-search.

© NVIDIA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in agent-skills/compileiq-debug of NVIDIA/CompileIQ.

  • SKILL.md
  • scripts/diagnose_csv.py

Open the folder on GitHubat commit 743aca4

Compare with similar skills

Compileiq Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Compileiq Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compileiq Debug this skillNVIDIA/CompileIQ137—~2.9kAutomated safety check: NotesApache-2.0
Graphsignalgraphsignal/graphsignal257—~6.2kAutomated safety check: PassApache-2.0
LLM Torch Profiler Trace AnalysisBBuf/AI-Infra-Auto-Driven-SKILLS900—~2.8kAutomated safety check: PassNone
Optimize OpCVCUDA/CV-CUDA2.7k—~834Automated safety check: PassCustom licence
Cutlass SkillslowlyC/agent-gpu-skills169—~1.3kAutomated safety check: PassMIT
Setup Workshop Nemoclawbrevdev/workshop-build-an-agent143—~5.2kAutomated safety check: PassApache-2.0

Similar skills

  • Graphsignal

    graphsignal/graphsignal

    Profile AI inference workloads (vLLM, SGLang, TensorRT-LLM, PyTorch, any GPU application) with the Graphsignal profiler and read the results from its local /signals JSON endpoint.

    257 GitHub stars~6.2k tokensUpdated 9 days ago
    AI & LLM EngineeringAuto-check passed
  • LLM Torch Profiler Trace Analysis

    BBuf/AI-Infra-Auto-Driven-SKILLS

    Analyzes Torch Profiler traces from SGLang, vLLM and TensorRT-LLM servers into kernel attribution, overlap and fusion tables.

    900 GitHub stars~2.8k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • Optimize Op

    CVCUDA/CV-CUDA

    Drive a single-operator optimization campaign per .agents/guidance/OPTIMIZATIONGUIDELINES.md, with a deterministically enforced definition-of-done and versioned MR summary.

    2.7k GitHub stars~834 tokensUpdated 20 days ago
    AI & LLM EngineeringAuto-check passed
  • Cutlass Skill

    slowlyC/agent-gpu-skills

    Write, debug, and optimize CUTLASS, CuTe, and CuTeDSL GPU kernels from local upstream source, examples, and headers.

    169 GitHub stars~1.3k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed
  • Setup Workshop Nemoclaw

    brevdev/workshop-build-an-agent

    Set up the NVIDIA "Build an Agent" DevX workshop as a working JupyterLab environment from INSIDE a locked-down OpenShell/NemoClaw sandbox, and hand the user the token URL + access commands.

    143 GitHub stars~5.2k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Llama Cpp

    Orchestra-Research/AI-Research-SKILLs

    Runs LLM inference on CPU, Apple Silicon, and consumer GPUs without NVIDIA hardware.

    13k GitHub starsUsed in 4 repos~1.5k tokens
    AI & LLM EngineeringAuto-check passed

More from NVIDIA/CompileIQ

  • Compileiq Booster Pack

    NVIDIA/CompileIQ

    Official

    Use BEFORE running a full CompileIQ search. An agent skill from NVIDIA/CompileIQ.

    137 GitHub stars~2.1k tokensUpdated 14 days ago
    Auto-check: notes
  • Compileiq Bootstrap

    NVIDIA/CompileIQ

    Official

    A skill your agent uses when starting a fresh CompileIQ project, hitting a socket timeout, or before running any other compileiq- skill.

    137 GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check: notes
  • Compileiq Run Search

    NVIDIA/CompileIQ

    Official

    A skill your agent uses when composing the Search(...) call and calling .start().

    137 GitHub stars~2.2k tokensUpdated 14 days ago
    Auto-check: notes
  • Official

    Use AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF.

    137 GitHub stars~2.2k tokensUpdated 14 days ago
    Auto-check: notes
  • Official

    A skill your agent uses when writing the objectivefunction= passed to Search().

    137 GitHub stars~2.3k tokensUpdated 14 days ago
    Auto-check: notes
  • Compileiq Search Space

    NVIDIA/CompileIQ

    Official

    A skill your agent uses when picking the searchspace= argument for Search().

    137 GitHub stars~1.9k tokensUpdated 14 days ago
    Auto-check: notes

Questions about Compileiq Debug

What does Compileiq Debug do?

A skill your agent uses when something is wrong: Search() hangs, all evaluations return INVALIDSCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is…. Compileiq Debug is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use when something is wrong: Search() hangs, all evaluations return INVALIDSCORE, scores aren't improving, every config returns the same number, ptxas errors fill the log, CV% is too high, or a winning ACF candidate needs NCU profiling to explain.

When should I use Compileiq Debug?

Compileiq Debug fits situations like: something is wrong: Search() hangs; all evaluations return INVALIDSCORE; scores arent improving; every config returns the same number.

How do I install Compileiq Debug in Claude Code?

Run `npx skills add NVIDIA/CompileIQ --skill compileiq-debug -a claude-code`. Or copy the skill folder (agent-skills/compileiq-debug in NVIDIA/CompileIQ) into .claude/skills/compileiq-debug in your project. Claude Code loads it when a task matches its description.

How do I install Compileiq Debug in Codex?

Run `npx skills add NVIDIA/CompileIQ --skill compileiq-debug -a codex`. Or copy the skill folder (agent-skills/compileiq-debug in NVIDIA/CompileIQ) into .agents/skills/compileiq-debug in your project. Codex loads it when a task matches its description.

Can I use Compileiq Debug in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/CompileIQ --skill compileiq-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/compileiq-debug, .gemini/skills/compileiq-debug, .github/skills/compileiq-debug and .opencode/skills/compileiq-debug in your project.

What does Compileiq Debug need to run?

Going by SKILL.md and its folder, Compileiq Debug needs Python for the scripts in its folder and the command-line tools its instructions call (python, gh and bash). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read.

Does Compileiq Debug access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Compileiq Debug safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Compileiq Debug use?

Compileiq Debug is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Compileiq Debug use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Compileiq Debug?

Skills that share tags, products or a category with Compileiq Debug: Graphsignal (graphsignal/graphsignal, 257 stars), LLM Torch Profiler Trace Analysis (BBuf/AI-Infra-Auto-Driven-SKILLS, 900 stars), Optimize Op (CVCUDA/CV-CUDA, 2.7k stars) and Cutlass Skill (slowlyC/agent-gpu-skills, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compileiq Debug?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/CompileIQ, which has 137 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 23, 2026.

Source: NVIDIA/CompileIQ on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.