Agent skill

Neuron Nki Profiling

by uw-syfi in uw-syfi/vibesys

This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.

MITAuto-check passed

Install Neuron Nki Profiling

skills CLI
$ npx skills add uw-syfi/vibesys --skill neuron-nki-profiling -a claude-code

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

GitHub CLI
$ gh skill install uw-syfi/vibesys neuron-nki-profiling --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/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-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
neuron-nki-profiling
GitHub stars
105
Token cost
~3.2k tokens
SKILL.md length
877 words
Files
3 (incl. scripts)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.

  • Works in 6 steps: Set Environment Variables → Execute Kernel → Create Dedicated Profile Folder → …
  • Encountering profile kernel
  • SKILL.md covers Quick Start, Prerequisites, Complete Profiling Workflow and Output Directory Structure, plus 7 more sections
  • Runs Python scripts from its folder; calls jq, python3 and python

What it does

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.

When your agent uses it

  • Encountering profile kernel
  • Capture execution trace
  • Get summary-json
  • Asking how to profile NKI kernel

Example prompts

  • “profile kernel”
  • “capture execution trace”
  • “generate NEFF”
  • “/neuron-nki-profiling”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Set Environment Variables
  2. Execute Kernel
  3. Create Dedicated Profile Folder
  4. Capture Profile with neuron-explorer
  5. View Results with neuron-explorer (JSON)
  6. Querying the profile and/or profile analysis (optional)

What it can do on your machine

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

  • Tool permissions

    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.

  • Runs code

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

    Shell commands in SKILL.md call:

    • jq
    • python3
    • python

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

  • Network

    No URLs in SKILL.md.

    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

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.

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

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 passed

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.

SKILL.md

The full file from uw-syfi/vibesys at commit 9f52142, republished under its MIT licence (© uw-syfi). 877 words, ~3,217 tokens.

Download SKILL.mdSave it as .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.
name
neuron-nki-profiling
description
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".
argument-hint
[kernel file]

Profiling NKI Kernels

This skill provides a complete workflow for profiling NKI kernel execution on Trainium/Inferentia hardware using Neuron profiling tools.

Quick Start

Minimal workflow to profile a kernel:

bash
# 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.ntff

The workflow generates two key artifacts:

  • NEFF file: Compiled kernel binary, generated during execution
  • NTFF file: Execution trace captured by neuron-explorer

Prerequisites

Before profiling kernels, resolve the NKI virtual environment path:

  1. Check environment: echo $NKI_VENV_PATH
  2. If empty, read .claude/nki-dev-suite.local.md and extract nki_venv_path from YAML frontmatter
  3. If still not found, report: "NKI_VENV_PATH not configured. Set the environment variable or create .claude/nki-dev-suite.local.md with nki_venv_path in frontmatter."

Activate before running any profiling commands:

bash
source $NKI_VENV_PATH/bin/activate

Hardware requirement: Profiling requires execution on actual Trainium/Inferentia hardware.

Complete Profiling Workflow

Step 1: Set Environment Variables

Add these environment variables in your Python script before kernel execution:

python
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 VariableDescription
NEURON_RT_INSPECT_ENABLEEnable runtime inspection
NEURON_RT_INSPECT_DEVICE_PROFILEEnable device-level profiling
NEURON_RT_INSPECT_OUTPUT_DIRDirectory for NEFF output
NEURON_RT_VISIBLE_CORESPin to specific core(s) — prevents contention when multiple agents profile concurrently
Step 2: Execute Kernel

Run your kernel script. This compiles and executes the kernel, generating the NEFF file in the output directory.

bash
python my_kernel.py

Important: 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.

python
# 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 NEFF

The runtime creates a subdirectory with instance and process ID naming:

./output/
└── i-0823210096b01e7ec_pid_1187583/
    └── neff_*_vnc_0.neff
Step 3: Create Dedicated Profile Folder

Create a dedicated folder for this profiling iteration. This prevents confusion when comparing multiple optimization attempts:

bash
mkdir -p ./profiles/run_001

Organize profile iterations:

./profiles/
├── run_001/              # Baseline profiling
│   ├── profile.ntff
│   └── metrics.json
├── run_002/              # After first optimization
│   ├── profile.ntff
│   └── metrics.json
└── run_003/              # After second optimization
Step 4: Capture Profile with neuron-explorer

Locate the NKI kernel NEFF and capture execution profile:

bash
# 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
FlagDescription
-nPath to NEFF file
-sOutput path for NTFF trace file
--profile-nth-exec=2Profile the 2nd execution (skip warmup)
--enable-dge-notifsEnable DMA engine notifications for detailed analysis
Step 5: View Results with neuron-explorer (JSON)

Generate a JSON summary of the profile results:

bash
neuron-explorer view \
    --output-format summary-json \
    -n $NEFF_PATH \
    -s ./profiles/run_001/profile.ntff

This outputs structured JSON with all metrics. Parse for specific values:

bash
neuron-explorer view \
    --output-format summary-json \
    -n $NEFF_PATH \
    -s ./profiles/run_001/profile.ntff | jq '.latency'

Common JSON queries:

bash
# 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:

bash
neuron-explorer view \
    --output-format summary-json \
    -n $NEFF_PATH \
    -s ./profiles/run_001/profile.ntff > ./profiles/run_001/metrics.json
Step 6: Querying the profile and/or profile analysis (optional)

For 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.

Output Directory Structure

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.

NEFF Identification

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:

bash
# 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.

Key Metrics Quick Reference

MetricDescriptionTarget
latencyTotal kernel execution time (ms)Lower is better
tensor_engine_active_time_percentTensorE utilization>90% for compute-bound
hbm_read_bytesHBM read trafficMinimize
hbm_write_bytesHBM write trafficMinimize
mm_arithmetic_intensityFLOPs per byte of memory trafficCompare to peak ratio
Show full SKILL.md (337 more words)Show less

Comparing Optimization Iterations

When optimizing a kernel, compare metrics across iterations:

bash
# 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:

IterationChangeLatency (ms)TensorE (%)
Baseline-1.2345%
Larger tilesIncreased tile 64→1280.9572%
Double bufferAdded prefetching0.7889%

Keep notes on what changed between iterations to correlate optimizations with metric improvements.

Complete Example

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.

Configuration

Required settings:

SettingSourceDescription
nki_venv_path.claude/nki-dev-suite.local.md or NKI_VENV_PATHPython venv with neuronx packages

Environment variables (set in kernel script):

VariableValuePurpose
NEURON_RT_INSPECT_ENABLE1Enable runtime inspection
NEURON_RT_INSPECT_DEVICE_PROFILE1Enable device profiling
NEURON_RT_INSPECT_OUTPUT_DIRPathNEFF output directory
SkillPurpose
/neuron-nki-profile-queryingDetailed profile querying and analysis
/neuron-nki-debuggingDebug compilation errors
/neuron-nki-docsLook up API documentation
/neuron-nki-writingWrite NKI kernels

Troubleshooting

Multiple NEFFs generated (can't tell which is the NKI kernel):

  • Primary fix: Compute reference operations (e.g., torch.matmul) on CPU, not on the XLA device. Each on-device XLA graph generates its own NEFF.
  • Identify NEFFs: Use 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.
  • Match NEFF to NTFF: Each NEFF neff_<ID>_vnc_0.neff has a matching trace <ID>_vnc_0.ntff in the same directory.

No NEFF file generated:

  • Verify NEURON_RT_INSPECT_ENABLE=1 is set before imports
  • Check NEURON_RT_INSPECT_OUTPUT_DIR path exists and is writable
  • Ensure kernel actually executed (print forces XLA compilation)
  • Confirm you are on Trainium/Inferentia hardware: neuron-ls

neuron-explorer capture fails:

  • Verify running on Trainium/Inferentia hardware
  • Check NEFF file path is correct with ls -la <path>
  • Ensure neuronx packages are installed in venv
  • Check sufficient disk space for NTFF file

Empty or minimal profile data:

  • Use --profile-nth-exec=2 to skip warmup execution
  • Add --enable-dge-notifs for detailed DMA analysis
  • Verify kernel ran successfully before profiling
  • Check NTFF file size is non-trivial: ls -lh profile.ntff

Latency varies between runs:

  • Use --profile-nth-exec=2 or higher to skip warmup
  • Ensure system is not under other load
  • Run multiple iterations and average results
  • Check for thermal throttling in profile output

© 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

Files

SKILL.md and 2 other files (scripts) in resources/skills/neuron-agentic-development/skills/neuron-nki-profiling of uw-syfi/vibesys.

  • SKILL.md
  • examples/basic-profiling-workflow.py
  • scripts/identify-neffs.py

Open the folder on GitHubat commit 9f52142

Compare with similar skills

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.

Neuron Nki Profiling compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Neuron Nki Profiling this skilluw-syfi/vibesys105—~3.2kAutomated safety check: PassMIT
Profileccusage/ccusage19k—~430Automated safety check: PassCustom licence
Write Guidevercel/next.js143k—~1.6kAutomated safety check: PassMIT
Cpu ProfileClickHouse/ClickHouse50k—~1.9kAutomated safety check: NotesApache-2.0
Kernel Organizationsgl-project/sglang37k—~1.3kAutomated safety check: PassApache-2.0
Codex Profilessickn33/agentic-awesome-skills47k1 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Profile

    ccusage/ccusage

    Profiles ccusage performance. An agent skill from ccusage/ccusage.

    19k GitHub stars~430 tokensUpdated today
    Auto-check passed
  • Write Guide

    vercel/next.js

    Official

    Generates technical guides that teach real-world use cases through progressive examples.

    143k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Cpu Profile

    ClickHouse/ClickHouse

    Profile a ClickHouse query using the sampling query profiler and system.tracelog.

    50k GitHub stars~1.9k tokensUpdated today
    DatabasesAuto-check: notes
  • Kernel Organization

    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.

    37k GitHub stars~1.3k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Codex Profiles

    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.

    47k GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Metal Kernel

    pytorch/pytorch

    Write Metal/MPS kernels for PyTorch operators. An agent skill from pytorch/pytorch.

    104k GitHub stars~4.9k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from uw-syfi/vibesys

All 15 skills in this repo
  • Neuron Nki Debugging

    uw-syfi/vibesys

    This skill guides debugging NKI compilation errors on Neuron hardware.

    105 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Neuron Nki Docs

    uw-syfi/vibesys

    Research NKI documentation for API lookups, tutorials, error codes, architecture, and optimization guides.

    105 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Query and analyze NKI kernel profile data from neuron-explorer parquet files.

    105 GitHub stars~4.3k tokensUpdated today
    Auto-check passed
  • Neuron Nki Writing

    uw-syfi/vibesys

    Guide for writing and modifying NKI kernels. An agent skill from uw-syfi/vibesys.

    105 GitHub stars~5k tokensUpdated today
    Auto-check passed
  • Triage PRs

    uw-syfi/vibesys

    Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys.

    105 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Open PR

    uw-syfi/vibesys

    Prepare and open VibeSys pull requests from local repo changes.

    105 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Neuron Nki Profiling

What does Neuron Nki Profiling do?

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.

When should I use Neuron Nki Profiling?

Neuron Nki Profiling fits situations like: encountering profile kernel; capture execution trace; get summary-json; asking how to profile NKI kernel.

How do I install Neuron Nki Profiling in Claude Code?

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.

How do I install Neuron Nki Profiling in Codex?

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.

Can I use Neuron Nki Profiling 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 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.

What does Neuron Nki Profiling need to run?

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.

Does Neuron Nki Profiling access the network?

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.

Is Neuron Nki Profiling safe to install?

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.

What licence does Neuron Nki Profiling use?

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.

How many tokens does Neuron Nki Profiling use?

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.

What are the alternatives to Neuron Nki Profiling?

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.

Who maintains Neuron Nki Profiling?

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.