Profile
ccusage/ccusage
Profiles ccusage performance. An agent skill from ccusage/ccusage.
This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.
$ npx skills add uw-syfi/vibesys --skill neuron-nki-profiling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --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/uw-syfi/vibesys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .claude/skills/neuron-nki-profiling && 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 "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .claude/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profilingType 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 uw-syfi/vibesys --skill neuron-nki-profiling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .agents/skills/neuron-nki-profiling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .agents/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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 uw-syfi/vibesys --skill neuron-nki-profiling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .cursor/skills/neuron-nki-profiling && 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 "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .cursor/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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/uw-syfi/vibesys.git --path resources/skills/neuron-agentic-development/skills/neuron-nki-profiling--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 uw-syfi/vibesys --skill neuron-nki-profiling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .gemini/skills/neuron-nki-profiling && 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 "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .gemini/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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 uw-syfi/vibesys neuron-nki-profilingInstalls 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 uw-syfi/vibesys --skill neuron-nki-profiling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .github/skills/neuron-nki-profiling && 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 "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .github/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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 uw-syfi/vibesys --skill neuron-nki-profiling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling .opencode/skills/neuron-nki-profiling && 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 "neuron-nki-profiling" agent skill from https://github.com/uw-syfi/vibesys/tree/main/resources/skills/neuron-agentic-development/skills/neuron-nki-profiling into .opencode/skills/neuron-nki-profiling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "neuron-nki-profiling", 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.
neuron-nki-profilingThis skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.
Neuron Nki Profiling is an agent skill from uw-syfi/vibesys. This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware. Use when encountering "profile kernel", "capture execution trace", "generate NEFF", "get summary-json", or asking "how to profile NKI kernel".
Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `examples/basic-profiling-workflow.py` and `scripts/identify-neffs.py`).
The repository describes itself as: Can AI Agents Build Bespoke Systems? The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9f52142. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
jqpython3pythonFrom 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.
Neuron Nki Profiling loads about 3.2k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 877 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 found no risky patterns in SKILL.md.
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.
The full file from uw-syfi/vibesys at commit 9f52142, republished under its MIT licence (© uw-syfi). 877 words, ~3,217 tokens.
.claude/skills/neuron-nki-profiling/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.This skill provides a complete workflow for profiling NKI kernel execution on Trainium/Inferentia hardware using Neuron profiling tools.
Minimal workflow to profile a kernel:
# 1. Set environment variables in Python before kernel execution
os.environ['NEURON_RT_INSPECT_ENABLE'] = '1'
os.environ['NEURON_RT_INSPECT_DEVICE_PROFILE'] = '1'
os.environ['NEURON_RT_INSPECT_OUTPUT_DIR'] = './output'
# 2. Run kernel to generate NEFF
python my_kernel.py
# 3. Find the NKI kernel NEFF (skip XLA-generated NEFFs)
NEFF_PATH=$(python3 scripts/identify-neffs.py ./output my_kernel_func_name)
# 4. Capture profile with neuron-explorer
neuron-explorer capture -n $NEFF_PATH -s profile.ntff --profile-nth-exec=2 --enable-dge-notifs
# 5. View results with neuron-explorer
neuron-explorer view --output-format summary-json -n $NEFF_PATH -s profile.ntffThe workflow generates two key artifacts:
Before profiling kernels, resolve the NKI virtual environment path:
echo $NKI_VENV_PATH.claude/nki-dev-suite.local.md and extract nki_venv_path from YAML frontmatterActivate before running any profiling commands:
source $NKI_VENV_PATH/bin/activateHardware requirement: Profiling requires execution on actual Trainium/Inferentia hardware.
Add these environment variables in your Python script before kernel execution:
import os
# Enable runtime inspection and device profiling
os.environ['NEURON_RT_INSPECT_ENABLE'] = '1'
os.environ['NEURON_RT_INSPECT_DEVICE_PROFILE'] = '1'
os.environ['NEURON_RT_INSPECT_OUTPUT_DIR'] = './output'
# Compiler flags for target hardware
os.environ['NEURON_CC_FLAGS'] = '--target trn2 --lnc 1' # use lnc=2 if explicitely told to.
# Pin to a specific neuron core(s) to avoid conflicts with concurrent sessions
os.environ['NEURON_RT_VISIBLE_CORES'] = '0' # '0,1', '0-1'| Environment Variable | Description |
|---|---|
NEURON_RT_INSPECT_ENABLE | Enable runtime inspection |
NEURON_RT_INSPECT_DEVICE_PROFILE | Enable device-level profiling |
NEURON_RT_INSPECT_OUTPUT_DIR | Directory for NEFF output |
NEURON_RT_VISIBLE_CORES | Pin to specific core(s) — prevents contention when multiple agents profile concurrently |
Run your kernel script. This compiles and executes the kernel, generating the NEFF file in the output directory.
python my_kernel.pyImportant: Compute references on CPU. If the test script computes a reference result (e.g., torch.matmul for comparison), do it on CPU — not on the XLA device. Every XLA graph compiled on-device generates a separate NEFF. Running reference operations on-device creates extra NEFFs that make it hard to identify the NKI kernel's NEFF.
# CORRECT: Reference on CPU — generates only the NKI kernel NEFF
expected = torch.relu(torch.matmul(lhs.cpu(), rhs.cpu()))
result = my_nki_kernel(lhs, rhs) # Only this generates a NEFF
# WRONG: Reference on device — generates an extra NEFF
expected = torch.relu(torch.matmul(lhs, rhs)) # Compiles to its own NEFF!
result = my_nki_kernel(lhs, rhs) # Another NEFFThe runtime creates a subdirectory with instance and process ID naming:
./output/
└── i-0823210096b01e7ec_pid_1187583/
└── neff_*_vnc_0.neffCreate a dedicated folder for this profiling iteration. This prevents confusion when comparing multiple optimization attempts:
mkdir -p ./profiles/run_001Organize profile iterations:
./profiles/
├── run_001/ # Baseline profiling
│ ├── profile.ntff
│ └── metrics.json
├── run_002/ # After first optimization
│ ├── profile.ntff
│ └── metrics.json
└── run_003/ # After second optimizationLocate the NKI kernel NEFF and capture execution profile:
# Find NKI kernel NEFF by function name (skips XLA-generated NEFFs)
NEFF_PATH=$(python3 scripts/identify-neffs.py ./output my_kernel_func_name)
# Capture profile trace
neuron-explorer capture \
-n $NEFF_PATH \
-s ./profiles/run_001/profile.ntff \
--profile-nth-exec=2 \
--enable-dge-notifs| Flag | Description |
|---|---|
-n | Path to NEFF file |
-s | Output path for NTFF trace file |
--profile-nth-exec=2 | Profile the 2nd execution (skip warmup) |
--enable-dge-notifs | Enable DMA engine notifications for detailed analysis |
Generate a JSON summary of the profile results:
neuron-explorer view \
--output-format summary-json \
-n $NEFF_PATH \
-s ./profiles/run_001/profile.ntffThis outputs structured JSON with all metrics. Parse for specific values:
neuron-explorer view \
--output-format summary-json \
-n $NEFF_PATH \
-s ./profiles/run_001/profile.ntff | jq '.latency'Common JSON queries:
# Get latency in milliseconds
jq '.latency'
# Get all engine utilizations
jq '{tensor: .tensor_engine_active_time_percent, vector: .vector_engine_active_time_percent}'
# Get memory metrics
jq '{hbm_read: .hbm_read_bytes, hbm_write: .hbm_write_bytes}'
# Check if memory-bound or compute-bound
jq '{intensity: .mm_arithmetic_intensity, peak_ratio: .peak_flops_bandwidth_ratio}'Save the full JSON output for later comparison:
neuron-explorer view \
--output-format summary-json \
-n $NEFF_PATH \
-s ./profiles/run_001/profile.ntff > ./profiles/run_001/metrics.jsonFor detailed analysis of the kernel profile, use the /neuron-nki-profile-querying skill. It allows for high level performance bounds analysis, as well as zoomed in, instruction level investigation of specific inefficiencies through python on parquet.
Understanding the generated file structure:
./output/ # NEURON_RT_INSPECT_OUTPUT_DIR
└── i-0823210096b01e7ec_pid_1187583/ # Instance ID + process ID
├── neff_307444798579300_vnc_0.neff # One NEFF per compiled XLA graph
├── neff_324387526933418_vnc_0.neff # (may include non-NKI NEFFs)
├── 307444798579300_vnc_0.ntff # Matching execution traces
├── 324387526933418_vnc_0.ntff
└── ntrace.pb # System trace metadata
./profiles/ # Organized profile iterations
├── run_001/
│ ├── profile.ntff # Execution trace
│ └── metrics.json # Summary metrics
├── run_002/
│ └── ...The instance/pid subdirectory naming (i-xxx_pid_xxx) is automatic and includes the EC2 instance ID and process ID for traceability.
When the output directory contains multiple NEFFs (from multiple on-device operations), use the included identify-neffs.py script to identify which NEFF belongs to which kernel:
# List all NEFFs with identification
python3 scripts/identify-neffs.py ./output/i-*_pid_*/
# Output:
# [NKI:matmul_relu] ./output/.../neff_389250674131083_vnc_0.neff
# inputs: ['lhs_T', 'rhs', 'tmp.4'] outputs: ['output.51']
# ntff: ./output/.../389250674131083_vnc_0.ntff
# [XLA:broadcast,dot,maximum] ./output/.../neff_418708643727628_vnc_0.neff
# Find a specific kernel by name (useful with multiple NKI kernels)
NEFF_PATH=$(python3 scripts/identify-neffs.py ./output/i-*_pid_*/ matmul_relu)How it works: Each NEFF embeds its compile workdir path (/tmp/.../neuroncc_compile_workdir/<uuid>/). The script reads the HLO module in that workdir. NKI kernels appear as custom-call ops with AwsNeuronCustomNativeKernel and carry a base64-encoded JSON blob containing func_name, input_names, and output_names.
Limitation: Depends on compile workdirs in /tmp/ still existing. Run promptly after kernel execution.
| Metric | Description | Target |
|---|---|---|
latency | Total kernel execution time (ms) | Lower is better |
tensor_engine_active_time_percent | TensorE utilization | >90% for compute-bound |
hbm_read_bytes | HBM read traffic | Minimize |
hbm_write_bytes | HBM write traffic | Minimize |
mm_arithmetic_intensity | FLOPs per byte of memory traffic | Compare to peak ratio |
When optimizing a kernel, compare metrics across iterations:
# Baseline measurement
neuron-explorer view --output-format summary-json \
-n $NEFF -s ./profiles/baseline/profile.ntff > ./profiles/baseline/metrics.json
# After optimization
neuron-explorer view --output-format summary-json \
-n $NEFF -s ./profiles/optimized/profile.ntff > ./profiles/optimized/metrics.json
# Compare latencies
echo "Baseline: $(jq .latency ./profiles/baseline/metrics.json)"
echo "Optimized: $(jq .latency ./profiles/optimized/metrics.json)"Optimization tracking table:
| Iteration | Change | Latency (ms) | TensorE (%) |
|---|---|---|---|
| Baseline | - | 1.23 | 45% |
| Larger tiles | Increased tile 64→128 | 0.95 | 72% |
| Double buffer | Added prefetching | 0.78 | 89% |
Keep notes on what changed between iterations to correlate optimizations with metric improvements.
See examples/basic-profiling-workflow.py for a complete end-to-end profiling script demonstrating all steps: environment setup, kernel execution, NEFF identification, profile capture, and JSON metric extraction.
Required settings:
| Setting | Source | Description |
|---|---|---|
nki_venv_path | .claude/nki-dev-suite.local.md or NKI_VENV_PATH | Python venv with neuronx packages |
Environment variables (set in kernel script):
| Variable | Value | Purpose |
|---|---|---|
NEURON_RT_INSPECT_ENABLE | 1 | Enable runtime inspection |
NEURON_RT_INSPECT_DEVICE_PROFILE | 1 | Enable device profiling |
NEURON_RT_INSPECT_OUTPUT_DIR | Path | NEFF output directory |
| Skill | Purpose |
|---|---|
/neuron-nki-profile-querying | Detailed profile querying and analysis |
/neuron-nki-debugging | Debug compilation errors |
/neuron-nki-docs | Look up API documentation |
/neuron-nki-writing | Write NKI kernels |
Multiple NEFFs generated (can't tell which is the NKI kernel):
torch.matmul) on CPU, not on the XLA device. Each on-device XLA graph generates its own NEFF.python3 scripts/identify-neffs.py ./output to list all NEFFs with their type (NKI vs XLA) and kernel names. See the NEFF Identification section for details.neff_<ID>_vnc_0.neff has a matching trace <ID>_vnc_0.ntff in the same directory.No NEFF file generated:
NEURON_RT_INSPECT_ENABLE=1 is set before importsNEURON_RT_INSPECT_OUTPUT_DIR path exists and is writableneuron-lsneuron-explorer capture fails:
ls -la <path>Empty or minimal profile data:
--profile-nth-exec=2 to skip warmup execution--enable-dge-notifs for detailed DMA analysisls -lh profile.ntffLatency varies between runs:
--profile-nth-exec=2 or higher to skip warmup© uw-syfi, MIT. 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 2 other files (scripts) in resources/skills/neuron-agentic-development/skills/neuron-nki-profiling of uw-syfi/vibesys.
Open the folder on GitHubat commit 9f52142
Neuron Nki Profiling 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 |
|---|---|---|---|---|---|---|
| Neuron Nki Profiling this skilluw-syfi/vibesys | 105 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Profileccusage/ccusage | 19k | — | ~430 | Automated safety check: Pass | Custom licence | |
| Write Guidevercel/next.js | 143k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Cpu ProfileClickHouse/ClickHouse | 50k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Kernel Organizationsgl-project/sglang | 37k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Codex Profilessickn33/agentic-awesome-skills | 47k | 1 repos | ~1.7k | Automated safety check: Pass | MIT |
ccusage/ccusage
Profiles ccusage performance. An agent skill from ccusage/ccusage.
vercel/next.js
Generates technical guides that teach real-world use cases through progressive examples.
ClickHouse/ClickHouse
Profile a ClickHouse query using the sampling query profiler and system.tracelog.
sgl-project/sglang
Apply the SGLang kernels RFC when adding, moving, splitting, or reviewing kernel APIs, registry metadata, kernel tests, benchmarks, and model-specific implementations.
sickn33/agentic-awesome-skills
Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEXHOME profiles for separate accounts, projects, and local state.
pytorch/pytorch
Write Metal/MPS kernels for PyTorch operators. An agent skill from pytorch/pytorch.
uw-syfi/vibesys
This skill guides debugging NKI compilation errors on Neuron hardware.
uw-syfi/vibesys
Research NKI documentation for API lookups, tutorials, error codes, architecture, and optimization guides.
uw-syfi/vibesys
Query and analyze NKI kernel profile data from neuron-explorer parquet files.
uw-syfi/vibesys
Guide for writing and modifying NKI kernels. An agent skill from uw-syfi/vibesys.
uw-syfi/vibesys
Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys.
uw-syfi/vibesys
Prepare and open VibeSys pull requests from local repo changes.
This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware. Neuron Nki Profiling is an agent skill from uw-syfi/vibesys. This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.
Neuron Nki Profiling fits situations like: encountering profile kernel; capture execution trace; get summary-json; asking how to profile NKI kernel.
Run `npx skills add uw-syfi/vibesys --skill neuron-nki-profiling -a claude-code`. Or copy the skill folder (resources/skills/neuron-agentic-development/skills/neuron-nki-profiling in uw-syfi/vibesys) into .claude/skills/neuron-nki-profiling in your project. Claude Code loads it when a task matches its description.
Run `npx skills add uw-syfi/vibesys --skill neuron-nki-profiling -a codex`. Or copy the skill folder (resources/skills/neuron-agentic-development/skills/neuron-nki-profiling in uw-syfi/vibesys) into .agents/skills/neuron-nki-profiling 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 uw-syfi/vibesys --skill neuron-nki-profiling -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/neuron-nki-profiling, .gemini/skills/neuron-nki-profiling, .github/skills/neuron-nki-profiling and .opencode/skills/neuron-nki-profiling in your project.
Going by SKILL.md and its folder, Neuron Nki Profiling needs Python for the scripts in its folder and the command-line tools its instructions call (jq, python3 and python). Our summary lists: Python 3.
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 no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. 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.
Neuron Nki Profiling is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.2k tokens (SKILL.md is roughly 13k 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 Neuron Nki Profiling: Profile (ccusage/ccusage, 19k stars), Write Guide (vercel/next.js, 143k stars), Cpu Profile (ClickHouse/ClickHouse, 50k stars) and Kernel Organization (sgl-project/sglang, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
uw-syfi (a GitHub organization) maintains it in uw-syfi/vibesys, which has 105 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 10, 2026.
Source: uw-syfi/vibesys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.