Skip to content
Skills Library
Science & research · Testing

check

/check

Verify that the braina plugin works - environment, Frites/HOI versions, JAX backend (CPU or GPU), MCP server connection, and an end-to-end smoke test of the tools. Use when the user asks to check, verify, test or debug the braina installation, when a braina MCP tool is unavailable or the server shows CONNECTION_CLOSED, or right after installing or updating the plugin.

Repository
braina ↗
Licence
BSD-3-Clause
Last repository change
18.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 18.09.2026, without references to retired models or APIs.

Licence

BSD-3-Clause, otwarta.

What it does and when to use it

Verify that the braina plugin works - environment, Frites/HOI versions, JAX backend (CPU or GPU), MCP server connection, and an end-to-end smoke test of the tools. Use when the user asks to check, verify, test or debug the braina installation, when a braina MCP tool is unavailable or the server shows CONNECTION_CLOSED, or right after installing or updating the plugin.

Original author description

Verify that the braina plugin works - environment, Frites/HOI versions, JAX backend (CPU or GPU), MCP server connection, and an end-to-end smoke test of the tools. Use when the user asks to check, verify, test or debug the braina installation, when a braina MCP tool is unavailable or the server shows CONNECTION_CLOSED, or right after installing or updating the plugin.

How it works

  1. 1. Smoke test (environment + tools)
  2. 2. If the braina MCP server did not connect
  3. 3. Interpret the JAX line
  4. 4. Optional: full test suite (development checkout only)
  5. Reporting
Original SKILL.md headings · 58 lines, 313 words
SKILL.md preview
---
name: check
description: Verify that the braina plugin works - environment, Frites/HOI versions, JAX backend (CPU or GPU), MCP server connection, and an end-to-end smoke test of the tools. Use when the user asks to check, verify, test or debug the braina installation, when a braina MCP tool is unavailable or the server shows CONNECTION_CLOSED, or right after installing or updating the plugin.
---

# Braina self-check

Run these steps in order and report the outcome plainly.

## 1. Smoke test (environment + tools)

```bash
uv run "${CLAUDE_PLUGIN_ROOT}/scripts/smoke_test.py"
```

- Prints the Frites / HOI / NumPy versions and the JAX backend, then runs
  `frites_sim_ar` -> `frites_conn_covgc` -> `frites_conn_net`, `hoi_oinfo`
  -> `hoi_get_nbest_mult`, and `plot_result` on simulated data.
- Ends with `SMOKE TEST PASSED` (exit 0) or `SMOKE TEST FAILED: [...]`.
- The **first** run after an install downloads ~150 MB of wheels and can
  take a few minutes; that is expected. Later runs take seconds.

## 2. If the braina MCP server did not connect

A `CONNECTION_CLOSED` / "Connection closed" status for the `braina` server
at session start almost always means the cold start exceeded Claude Code's
30 s MCP timeout while `uv` was still downloading dependencies. Fix:

```bash
uv sync --script "${CLAUDE_PLUGIN_ROOT}/mcp/braina_mcp.py"
```

then reconnect with `/mcp` (or restart the session). The plugin's
SessionStart hook runs this sync in the background automatically, so the
second session normally works without intervention. If `uv` itself is
missing: https://docs.astral.sh/uv/getting-started/installation/

## 3. Interpret the JAX line

- `JAX backend: CPU` - the default; HOI tools run on CPU. Fine for a
  handful of ROIs and `maxsize` <= 4-5.
- `JAX backend: GPU` - only happens if the user installed a CUDA-enabled
  `jax` in the environment `uv` resolves. Braina's own dependency block
  requests plain (CPU) `jax`; see the `hoi-metrics` skill, section
  "Compute backend", before promising GPU speed-ups.

## 4. Optional: full test suite (development checkout only)

From a clone of the braina repository:

```bash
uv run tests/run_tests.py
```

runs the pytest suite that exercises all 34 MCP tools on synthetic data.

## Reporting

State: versions, backend, whether the smoke test passed, and - if it did
not - the first failing tool and its error line verbatim. Do not describe
the installation as working until the smoke test has actually passed.

Versions

RepositoryScoreLicence
This page · brainets/braina100BSD-3-Clause
tw93/Waza100MIT
nigelng/nng-kit100MIT
Automatebasics/automatebasics-skills100MIT
tony/skills100MIT
vibiumdev/vibium100Apache-2.0
koda-ai-studio/agent-bom100Apache-2.0
JQ-WCoding/devkit100MIT
ribato22/vibecheck100MIT

Database snapshot: 13.11.2026 · package version 24a7b4f4941c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100orientation
    Use when the user has electrophysiological/neuroimaging data (fMRI, MEG, EEG, LFP, MUA) and an analysis question but hasn't settled on a method or a statistical approach - e.g. "how do I check if region A drives region B", "is this a connectivity or a higher-order interaction…
  • 100cuequivariance-jax
    Use when writing or debugging cuEquivariance JAX polynomials, irrep dictionaries, Flax NNX layers, or CPU/CUDA execution and layouts.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.