brainx-install

Installs, upgrades, and uninstalls the BrainX Python meta-package with device-targeted verification.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/chaobrain/BrainX-skill --skill brainx-install-chaobrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainx-install
Source: https://github.com/chaobrain/BrainX-skill/tree/main/brainx-display-cases/creative-experiment-verification/06-seizure-recruitment/run2/.agents/skills/brainx-install
Command: npx skills add https://github.com/chaobrain/BrainX-skill --skill brainx-install-chaobrain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Installing the BrainX ecosystem correctly is error-prone: users must pick a coherent release whose component versions are compatible, choose the right device extra (cpu, cuda12, cuda13, tpu), and avoid mutating the wrong Python environment. This Skill enforces a confirmation-gated workflow that inspects the environment, selects one indivisible BrainX release, and verifies the result before reporting. ## Core Features & Use Cases - Guided installation and upgrade: Performs read-only environment inspection, requires explicit device-target confirmation, resolves the latest Python-compatible BrainX release, and installs only the confirmed meta-package release. - Compatibility-matrix release matching: When BrainX components already exist or a pinned version is requested, uses the bundled version matrix to select one coherent release instead of mixing component versions. - Safe uninstall and cleanup: Removes BrainX ecosystem packages (and optionally JAX distributions) from one confirmed virtual environment while preserving shared dependencies, with reverse-dependency checks and pip-check verification. - Use Case: A researcher with an NVIDIA GPU asks to set up BrainX. The Skill detects CUDA evidence, asks the user to confirm cuda12, presents the full installation specification, and only after approval creates the venv, installs BrainX[cuda12], and verifies JAX sees the GPU. ## Quick Start Ask the agent to install BrainX for your device target, for example: install BrainX with CUDA 12 support in a new virtual environment and verify it works.

Frequently Asked Questions about brainx-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install BrainX with CUDA support in Python?

Confirm your device target explicitly, then install the matching extra such as pip install -U BrainX[cuda12] or BrainX[cuda13] inside a Python 3.11+ virtual environment. The Skill verifies success by importing BrainX and checking that jax.devices() reports a CUDA device.

How do I upgrade or pin a specific BrainX version?

BrainX uses date-style releases, so pin with pip install BrainX==2025.9.15 while keeping your confirmed hardware extra. When components already exist, the compatibility matrix is used to select one coherent release rather than mixing component versions.

What Python version does BrainX require?

BrainX requires a Python interpreter at version 3.11 or newer. The Skill inspects candidate interpreters and existing virtual environments read-only before proposing one to create or reuse.

How do I uninstall BrainX without breaking my environment?

Uninstall only the confirmed BrainX ecosystem distributions from one verified virtual environment using its exact Python executable. JAX removal is a separate explicit opt-in, and shared dependencies like NumPy, SciPy, and Optax are always preserved.

Why must I confirm the device target instead of auto-detecting it?

Detected GPU or TPU hardware is treated as evidence, not consent, because the intended runtime may differ from the visible hardware. The Skill requires an explicit choice among cpu, cuda12, cuda13, or tpu before any installation.

Can I install individual BrainX component packages separately?

No. Each BrainX release is an indivisible compatibility set, so only the meta-package release is installed and components are never installed or version-mixed individually.