Data Table Manager
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
Use AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF.
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-result --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/compileiq-validate-result .claude/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.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/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .claude/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-resultType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-result --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agent-skills/compileiq-validate-result .agents/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .agents/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-result --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agent-skills/compileiq-validate-result .cursor/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .cursor/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NVIDIA/CompileIQ.git --path agent-skills/compileiq-validate-result--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-result --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agent-skills/compileiq-validate-result .gemini/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .gemini/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-resultInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .github/skills && cp -r skills-src/agent-skills/compileiq-validate-result .github/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .github/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NVIDIA/CompileIQ compileiq-validate-result --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NVIDIA/CompileIQ.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agent-skills/compileiq-validate-result .opencode/skills/compileiq-validate-result && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "compileiq-validate-result" agent skill from https://github.com/NVIDIA/CompileIQ/tree/main/agent-skills/compileiq-validate-result into .opencode/skills/compileiq-validate-result/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "compileiq-validate-result", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
compileiq-validate-resultUse AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF.
Compileiq Validate Result is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF. Loads the dumpresults CSV, extracts top-K candidates (single-objective) or the Pareto front (multi-objective), re-measures each against the no-ACF baseline with 100+ trials on fresh caches, runs Welch's t-test plus Cohen's d, rejects three classic false-positive patterns (lucky-min / higher-variance / multiple-comparisons-of-N), and saves the validated winner as best.acf. Triggers on "validate result", "extract best config"…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/welch_validate.py`).
It sits in Documents & Office, covering CSV and tabular files. The repository describes itself as: An Optimizer for Nvidia Compilers. The licence is Apache-2.0.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 743aca4. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashReadFrom allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compileiq Validate Result loads about 2.2k tokens when it runs. Until then it costs about 161 tokens; SKILL.md has 578 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, ReadAutomated 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.
The full file from NVIDIA/CompileIQ at commit 743aca4, republished under its Apache-2.0 licence (© NVIDIA). 578 words, ~2,167 tokens.
.claude/skills/compileiq-validate-result/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.The score CompileIQ reports during a search uses N=5-15 trials per evaluation and a shared cache. That's appropriate for the search loop but wildly insufficient for shipping. This skill is the gate before any ACF goes to production.
tuner.start() has returned and there's a dump_results= CSV on disk.from compileiq.results import SearchResult
results = SearchResult.from_csv("results.csv", problem_type="min", clear_duplicates=True)
df = results.get_results()
print(f"{len(df)} evaluations across {df['generation'].max()+1} generations")Single-objective:
best = results.get_best_result()
# dict: {metadata, generation, score_1, params, [norm_score_1]}
score = best.get("score_1", best.get("score")) # legacy defensiveness
acf_hex = best["params"] # hex stringscore_1 (with underscore-one) is the canonical key — it matches the
multi-objective convention score_N. Older code sometimes uses plain score;
the fallback above handles both shapes.
For top-K:
import pandas as pd
df_valid = df[pd.to_numeric(df["score_1"], errors="coerce") < 1e10]
top_k = df_valid.nsmallest(5, "score_1") # nlargest for MAX problemsMulti-objective:
front = results.pareto_front() # raises if num_objectives == 1
for candidate in front:
print(candidate["score_1"], candidate["score_2"], candidate["params"])Mixed user+compiler search space: results carry separate keys —
best["user_space"] for the user-side knobs, best["params"] for the ACF
hex. Save both.
| Stage | Warmup | Trials | Cache | GPU clocks |
|---|---|---|---|---|
Optimization (during tuner.start()) | 5-25 | 5-15 | per-eval | recommended locked |
| Validation | ≥50 | ≥100 | per-measurement | must be locked |
Both the baseline (no ACF) and each top-K candidate are re-measured at validation N. The optimization-time measurement is too noisy to ship from.
import numpy as np
from scipy import stats
def validate_speedup(baseline_ms: np.ndarray, optimized_ms: np.ndarray) -> dict:
t, p = stats.ttest_ind(baseline_ms, optimized_ms, equal_var=False) # Welch's
b_mean, b_std = baseline_ms.mean(), baseline_ms.std(ddof=1)
o_mean, o_std = optimized_ms.mean(), optimized_ms.std(ddof=1)
pooled = np.sqrt((b_std**2 + o_std**2) / 2)
d = (b_mean - o_mean) / pooled if pooled > 0 else 0.0
return {
"speedup_mean": b_mean / o_mean,
"speedup_median": np.median(baseline_ms) / np.median(optimized_ms),
"p_value": float(p),
"cohens_d": float(d),
"significant": bool(p < 0.05 and o_mean < b_mean and d > 0.2),
"baseline": {"mean": b_mean, "std": b_std,
"p5": np.percentile(baseline_ms, 5),
"p95": np.percentile(baseline_ms, 95)},
"optimized": {"mean": o_mean, "std": o_std,
"p5": np.percentile(optimized_ms, 5),
"p95": np.percentile(optimized_ms, 95)},
}Ship rule: p_value < 0.05 AND cohens_d > 0.2 (preferably > 0.5)
AND optimized.mean < baseline.mean. Anything weaker, do not claim a
speedup.
| # | Pattern | Symptom | Cause | Check | Disposition |
|---|---|---|---|---|---|
| 1 | Lucky-min | Optimized min is lower but mean is equal or worse | Optimizer picked a config that occasionally runs fast | Compare means, not minimums; reject if optimized.mean ≥ baseline.mean | Reject. |
| 2 | Higher-variance | Optimized p5-p95 range is wider than baseline with same mean | ACF didn't speed anything up; just spread the distribution | Compute (p95 - p5) for both; reject if optimized range is materially wider (>25%) | Reject. |
| 3 | Multiple-comparisons | Best of 500 evaluations looks 2-5% faster but doesn't reproduce | With 500 evals some will look good by chance | Re-measure top-K on a fresh cache and fresh trials; reject candidates that don't survive | Reject. |
from compileiq.utils.helpers import save_compiler_config
save_compiler_config("best.acf", best["params"])
# Mixed search spaces: persist the user_space knobs separately
if "user_space" in best:
import json
Path("best.user_space.json").write_text(json.dumps(best["user_space"], indent=2))Append one row per candidate decision to validation-log.csv. Fields, per
docs/flashinfer_booster.md:135-148:
ptxas, nvcc paths + versionsKEPT or REJECTED:<reason>The scripts/welch_validate.py helper records the timing/statistical fields,
ACF hash, benchmark commands, GPU/toolchain metadata, and common environment
variables automatically. Pass --manifest, --framework, and --input-shape
for workload-specific fields the helper cannot infer.
python scripts/welch_validate.py \
--acf best.acf \
--baseline-cmd "python bench.py --routine matmul" \
--opt-cmd "PTXAS_OPTIONS='--apply-controls=best.acf' python bench.py --routine matmul" \
--trials 100 --warmup 50 \
--score-regex 'mean: ([0-9.]+)' \
--manifest booster-packs-YYYY.MM.DD \
--framework "flashinfer <version>" \
--input-shape "routine=matmul, M=..., N=..., K=..." \
--output validation-log.csvPrints KEPT or REJECTED:<reason> and appends a row to the log. Also
importable: from welch_validate import validate_speedup.
python scripts/welch_validate.py --self-testSynthesizes two identical normal distributions, asserts the statistical gate
returns significant=False. Then differs them, asserts significant=True.
Catches misconfigured scipy/numpy before a real validation.
pareto_front() raises if num_objectives == 1. Guard with
if results.num_scores > 1: or use try/except.score_1 vs score. Current API is score_1. Some older results
exporters used plain score. The defensive read pattern
best.get("score_1", best.get("score")) handles both.CIQ_KEEP_CACHE=1
active during search, validation must explicitly wipe ~/.cache/compileiq
or use a fresh TRITON_CACHE_DIR and HELION_SKIP_CACHE=1. Otherwise the
optimization-time numbers re-appear and you're not validating anything.best.acf and validation-log.csv.compileiq-debug for diagnosis.compileiq-run-search with bigger
pool_size/generations.© 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
SKILL.md and 1 other file (scripts) in agent-skills/compileiq-validate-result of NVIDIA/CompileIQ.
Open the folder on GitHubat commit 743aca4
Compileiq Validate Result 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Compileiq Validate Result this skillNVIDIA/CompileIQ | 137 | — | ~2.2k | Automated safety check: Notes | Apache-2.0 | |
| Data Table Managern8n-io/n8n | 207k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Instrument Data To Allotropeaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | 2 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Abuse Hunternexu-io/harness-engineering-guide | 663 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Markitshift-labs-ai/markit | 1.3k | — | ~299 | Automated safety check: Pass | MIT | |
| Sector Analysttradermonty/claude-trading-skills | 3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
n8n-io/n8n
Load before calling data-tables or parse-file. An agent skill from n8n-io/n8n.
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
nexu-io/harness-engineering-guide
Detect and investigate bulk registration abuse on SaaS platforms.
shift-labs-ai/markit
Convert files and URLs to Markdown. An agent skill from shift-labs-ai/markit.
tradermonty/claude-trading-skills
This skill should be used when analyzing sector rotation patterns and market cycle positioning.
ckpxgfnksd-max/uap-release-analyzer
Inventory, extract, and analyze tranches of declassified UAP/UFO files — including war.gov/UFO/ "PURSUE" releases, FBI Vault, NARA boxes, and AARO publications.
NVIDIA/CompileIQ
Use BEFORE running a full CompileIQ search. An agent skill from NVIDIA/CompileIQ.
NVIDIA/CompileIQ
A skill your agent uses when starting a fresh CompileIQ project, hitting a socket timeout, or before running any other compileiq- skill.
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…
NVIDIA/CompileIQ
A skill your agent uses when composing the Search(...) call and calling .start().
NVIDIA/CompileIQ
A skill your agent uses when writing the objectivefunction= passed to Search().
NVIDIA/CompileIQ
A skill your agent uses when picking the searchspace= argument for Search().
Categories
Use AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF. Compileiq Validate Result is an agent skill from NVIDIA/CompileIQ, published by the product's own GitHub organization. Use AFTER a Search has completed and BEFORE claiming any speedup or shipping an ACF.
Compileiq Validate Result fits situations like: validate result; extract best config; is my speedup real.
Run `npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a claude-code`. Or copy the skill folder (agent-skills/compileiq-validate-result in NVIDIA/CompileIQ) into .claude/skills/compileiq-validate-result in your project. Claude Code loads it when a task matches its description.
Run `npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -a codex`. Or copy the skill folder (agent-skills/compileiq-validate-result in NVIDIA/CompileIQ) into .agents/skills/compileiq-validate-result in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/CompileIQ --skill compileiq-validate-result -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-validate-result, .gemini/skills/compileiq-validate-result, .github/skills/compileiq-validate-result and .opencode/skills/compileiq-validate-result in your project.
Going by SKILL.md and its folder, Compileiq Validate Result needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash, Read.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Compileiq Validate Result 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.
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Compileiq Validate Result: Data Table Manager (n8n-io/n8n, 207k stars), Instrument Data To Allotrope (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), Abuse Hunter (nexu-io/harness-engineering-guide, 663 stars) and Markit (shift-labs-ai/markit, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.