Official agent skill

Compileiq Search Space

by NVIDIA in NVIDIA/CompileIQ

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

OfficialApache-2.0Auto-check: notes

Install Compileiq Search Space

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

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

GitHub CLI
$ gh skill install NVIDIA/CompileIQ compileiq-search-space --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-search-space .claude/skills/compileiq-search-space && 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-search-space
GitHub stars
138
Token cost
~1.9k tokens
SKILL.md length
485 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Picking the searchspace= argument for Search()
  • SKILL.md covers When, The three provider classes, Variants available today and Air-gapped / offline mirror, plus 5 more sections
  • Calls python and gh
  • PtxasSearchSpace

What it does

Compileiq Search Space is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use when picking the searchspace= argument for Search(). Covers the three provider classes (PtxasSearchSpace, NvccSearchSpace, LocalSearchSpaceBin), how to pin a version/variant/tag, the attention-focused 'att' variant for attention kernels (FlashAttention, GQA, MHA, MLA, FlashInfer Batch Decode), air-gapped mirroring via CIQSEARCHSPACESDIR, and custom user-defined search spaces built from compileiq.searchspaces.base primitives. Triggers on "search space", "PtxasSearchSpace", "NvccSearchSpace", "air-gapped…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with NVIDIA AI Platform. The repository describes itself as: An Optimizer for Nvidia Compilers. The licence is Apache-2.0.

When your agent uses it

  • Picking the searchspace= argument for Search()
  • PtxasSearchSpace
  • NvccSearchSpace
  • Air-gapped compileiq

Example prompts

  • “search space”
  • “PtxasSearchSpace”
  • “NvccSearchSpace”
  • “/compileiq-search-space”

Requirements

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

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

    Shell commands in SKILL.md call:

    • python
    • gh

    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 Search Space loads about 1.9k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~158
When it runs · the whole SKILL.md, loaded when a task matches
~1.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); files beside SKILL.md are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/compileiq-search-space/SKILL.md (or your agent's skills folder).
name
compileiq-search-space
description
Use when picking the search_space= argument for Search(). Covers the three provider classes (PtxasSearchSpace, NvccSearchSpace, LocalSearchSpaceBin), how to pin a version/variant/tag, the attention-focused 'att' variant for attention kernels (FlashAttention, GQA, MHA, MLA, FlashInfer Batch Decode), air-gapped mirroring via CIQ_SEARCH_SPACES_DIR, and custom user-defined search spaces built from compileiq.search_spaces.base primitives. Triggers on "search space", "PtxasSearchSpace", "NvccSearchSpace", "air-gapped compileiq", "offline compileiq", "CIQ_SEARCH_SPACES_DIR", "attention variant", "ptxas att".
allowed-tools
Bash, Read
when_to_use
- About to instantiate Search() and need to pick a search_space. - Network-restricted host that can't reach github.com/releases. - Have a one-off .bin and…
license
Apache-2.0
metadata.version
1.0.0
metadata.author
NVIDIA CompileIQ
metadata.domain
compiler-optimization
paths
**/*.py, **/*.yaml, **/*.yml

compileiq-search-space

CompileIQ ships compiler search spaces as release-backed binary blobs that the providers in compileiq.search_spaces.compilers fetch on demand. This skill covers the three provider classes, the variants they expose today, how to use them offline, and how to define a custom search space for non-compiler tuning.

When

  • Choosing a search space for a new project.
  • Pinning a specific release for a paper or production deployment.
  • Working on an air-gapped or corporate-firewalled host.
  • Stress-testing a one-off .bin you have on hand.

The three provider classes

Reference: compileiq/search_spaces/compilers.py:66-102.

python
from compileiq.search_spaces.compilers import (
    PtxasSearchSpace,
    NvccSearchSpace,
    LocalSearchSpaceBin,
)

# Default — auto-fetch latest PTXAS 13.3 default variant from GitHub releases
ss = PtxasSearchSpace()

# Pinned for reproducibility
ss = PtxasSearchSpace(version="13.3", variant="default", tag="search-spaces-2026.05")

# **Attention** workloads (FlashAttention / GQA / MHA / MLA / FlashInfer Batch Decode)
ss = PtxasSearchSpace(version="13.3", variant="att")

# NVCC variant for full-pipeline tuning
ss = NvccSearchSpace(version="13.3")

# Single .bin you already have on disk — skips manifest + network
ss = LocalSearchSpaceBin("/path/to/ptxas13.3_search_space.bin")

# Pass to Search
from compileiq.ciq import Search
tuner = Search(objective_function=..., search_space=ss, search_config=...)

Variants available today

From release/search-spaces/manifest-source.yaml:

CompilerVersionVariantFileWhen to use
ptxas13.3defaultptxas13.3_search_space.binGeneric PTXAS tuning; the right starting point for most kernels.
ptxas13.3attptxas13.3_att_search_space.binAttention workloads. att is short for attention, not "attribute". This variant is curated for FlashAttention, GQA, MHA, MLA, FlashInfer Batch Decode, and similar attention kernels. Prefer this whenever the kernel is attention-shaped.
nvcc13.3defaultnvcc13.3_search_space.binFull-compiler (front-end + back-end) tuning when you want NVCC-level knobs, not just PTXAS.

To enumerate variants in the latest release at any time:

bash
gh release view --json assets --jq '.assets[].name' -R NVIDIA/CompileIQ <tag>

Air-gapped / offline mirror

Pre-download the manifest plus all .bin files on a connected host, then point CompileIQ at the local mirror via CIQ_SEARCH_SPACES_DIR:

bash
# On a connected host
mkdir -p /shared/ciq-search-spaces
gh release download search-spaces-latest -R NVIDIA/CompileIQ -D /shared/ciq-search-spaces

# Move the directory to the air-gapped host (rsync, scp, sneaker-net, …)

# On the air-gapped host
export CIQ_SEARCH_SPACES_DIR=/shared/ciq-search-spaces
python -c "from compileiq.search_spaces.compilers import PtxasSearchSpace; print(PtxasSearchSpace().retrieve())"

Other env-var knobs:

  • CIQ_SEARCH_SPACES_REPO (default NVIDIA/CompileIQ): override the GitHub repo the resolver queries — useful for staging or forks.
  • CIQ_SS_TAG_PREFIX (default search-spaces-): tag prefix used when resolving tag="latest". Rarely needs changing.

Cache location

Resolved binaries are cached at ~/.cache/compileiq/<tag>/<sha256_prefix>_<filename>. The resolver verifies cached files by sha256; a corrupted entry is re-downloaded on the next call. Safe to wipe — wiping just costs one re-download.

Show full SKILL.md (226 more words)Show less

Custom search spaces (non-compiler tuning)

For hyperparameter tuning, autotuner knobs, or any user-defined space, pass a dict (or list-of-dicts) directly instead of a provider. Primitives live in compileiq/search_spaces/base.py:

python
import compileiq.search_spaces.base as ss

search_space = {
    "block_size":  ss.choice([64, 128, 256, 512]),
    "unroll":      ss.range(start=1, end=8, step=1),
    "use_shmem":   ss.literal(True, knockout_prob=0.5),
    "lr":          ss.log_sampling(start=1e-5, end=1e-1, total=20),
}
PrimitivePurpose
choice([...])Sample uniformly from a discrete list.
range(start, end, step)Range-like sampling (also supports float steps).
literal(value, knockout_prob=...)Constant value; knockout_prob lets the GA disable this parameter.
log_sampling(start, end, total)Logarithmic distribution between start and end with total discrete buckets.

Mixed user + compiler search space (list shape):

python
search_space = [
    {"config_idx": ss.range(0, len(CONFIGS) - 1)},   # user-defined
    PtxasSearchSpace(version="13.3"),                # compiler-side
]

When the search space is a list, the objective receives a list of the same length — see compileiq-author-objective for the unpacking pattern.

Self-test

bash
# Default variant resolves
python -c "
from compileiq.search_spaces.compilers import PtxasSearchSpace
p = PtxasSearchSpace().retrieve()
assert p.exists() and p.stat().st_size > 0, p
print(f'default OK: {p}')
"

# Attention variant resolves
python -c "
from compileiq.search_spaces.compilers import PtxasSearchSpace
p = PtxasSearchSpace(version='13.3', variant='att').retrieve()
assert p.exists() and p.stat().st_size > 0, p
print(f'att OK: {p}')
"

# Misconfigured air-gap mirror produces a clear error
CIQ_SEARCH_SPACES_DIR=/nonexistent python -c "
from compileiq.search_spaces.compilers import PtxasSearchSpace
try:
    PtxasSearchSpace().retrieve()
    print('UNEXPECTED: should have failed')
except Exception as e:
    print(f'expected failure: {type(e).__name__}')
"

Gotchas

  • att is attention, not "attribute". Earlier docs and a test fixture mislabeled the variant as "attribute-based register allocation" — corrected in this same branch. When recommending the variant to a user, say "attention" explicitly.
  • Providers vs Booster Packs are different things. Providers return one binary search space the optimization core consumes during a search; Booster Packs are pre-built .acf candidates to apply outside a search. Don't feed a .acf from a Booster Pack to PtxasSearchSpace(...).
  • LocalSearchSpaceBin doesn't validate .bin contents. It only validates that the file exists. A malformed file will fail downstream when the core tries to parse it; the resulting error message points at the resolver, not the provider.

Next

  • Writing the objective function that consumes the search space: compileiq-author-objective.
  • Running the search: 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

Just SKILL.md in agent-skills/compileiq-search-space of NVIDIA/CompileIQ.

Open the folder on GitHubat commit 743aca4

Compare with similar skills

Compileiq Search Space 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 Search Space compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Compileiq Search Space this skillNVIDIA/CompileIQ138—~1.9kAutomated safety check: NotesApache-2.0
LLM Torch Profiler Analysissgl-project/sglang37k2 repos~6.4kAutomated safety check: PassApache-2.0
Skill InspectorNVIDIA/SkillSpector20k—~1.8kAutomated safety check: PassApache-2.0
Megatron-LM Container and Dependency SetupNVIDIA/Megatron-LM18k—~2.6kAutomated safety check: PassApache-2.0
Embeddings via 9Routerdecolua/9router30k—~604Automated safety check: PassMIT
Megatron-LM Base Image BumpNVIDIA/Megatron-LM18k—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • LLM Torch Profiler Analysis

    sgl-project/sglang

    Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.

    37k GitHub starsUsed in 2 repos~6.4k tokens
    DevelopmentAuto-check passed
  • Skill Inspector

    NVIDIA/SkillSpector

    Official

    Decides whether an agent skill is safe to install by combining a SkillSpector static scan with the agent's own source review, ending in APPROVE, CAUTION or REJECT.

    20k GitHub stars~1.8k tokensUpdated today
    SecurityAuto-check passed
  • Official

    Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.

    18k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Embeddings via 9Router

    decolua/9router

    Generates vector embeddings through the 9Router /v1/embeddings endpoint, using models from providers such as OpenAI, Gemini, Mistral and Voyage for RAG and semantic search.

    30k GitHub stars~604 tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Megatron-LM Base Image Bump

    NVIDIA/Megatron-LM

    Official

    Moves Megatron-LM CI to a newer NVIDIA PyTorch base image, updating both the GitHub and GitLab pins together and handling the CI follow-up.

    18k GitHub stars~2.8k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-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.

    138 GitHub stars~2.1k tokensUpdated 16 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.

    138 GitHub stars~1.3k tokensUpdated 16 days ago
    Auto-check: notes
  • Compileiq Debug

    NVIDIA/CompileIQ

    Official

    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…

    138 GitHub stars~2.9k tokensUpdated 16 days ago
    Auto-check: notes
  • Compileiq Run Search

    NVIDIA/CompileIQ

    Official

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

    138 GitHub stars~2.2k tokensUpdated 16 days ago
    Auto-check: notes
  • Official

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

    138 GitHub stars~2.2k tokensUpdated 16 days ago
    Auto-check: notes
  • Official

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

    138 GitHub stars~2.3k tokensUpdated 16 days ago
    Auto-check: notes

Questions about Compileiq Search Space

What does Compileiq Search Space do?

A skill your agent uses when picking the searchspace= argument for Search(). Compileiq Search Space is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use when picking the searchspace= argument for Search().

When should I use Compileiq Search Space?

Compileiq Search Space fits situations like: picking the searchspace= argument for Search(); ptxasSearchSpace; nvccSearchSpace; air-gapped compileiq.

How do I install Compileiq Search Space in Claude Code?

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

How do I install Compileiq Search Space in Codex?

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

Can I use Compileiq Search Space 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-search-space -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-search-space, .gemini/skills/compileiq-search-space, .github/skills/compileiq-search-space and .opencode/skills/compileiq-search-space in your project.

What does Compileiq Search Space need to run?

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

Does Compileiq Search Space 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 Search Space 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. Review the folder before installing.

What licence does Compileiq Search Space use?

Compileiq Search Space 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 Search Space use?

About 1.9k tokens (SKILL.md is roughly 7.7k 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 Search Space?

Skills that share tags, products or a category with Compileiq Search Space: LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars), Skill Inspector (NVIDIA/SkillSpector, 20k stars), Megatron-LM Container and Dependency Setup (NVIDIA/Megatron-LM, 18k stars) and Embeddings via 9Router (decolua/9router, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Compileiq Search Space?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/CompileIQ, which has 138 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.