Agent skill · Data & Analytics

hbn-skill

Use this skill whenever the user wants an end-to-end workflow for the Healthy Brain Network (HBN) dataset, including download, BIDS organization, and multimodal processing of sMRI, dMRI, rs-fMRI, task-fMRI, and EEG data. Triggers include: 'HBN', 'Healthy Brain Network', 'process HBN', 'HBN fMRI', 'HBN EEG', or any request to run the HBN multimodal pipeline. This is the NeuroClaw dataset-orchestration layer for HBN.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill hbn-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Requires: - smri-skill - fmri-skill - dwi-skill - eeg-skill - bids-organizer - claw-shell
Path: skills/neuroclaw/hbn-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 135
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# HBN Skill (Dataset-Orchestration Layer) ## Overview `hbn-skill` is the NeuroClaw orchestration skill for the **Healthy Brain Network (HBN)** dataset. It coordinates a fixed multi-phase workflow: 1. Download HBN data from the FCP/INDI repository. 2. Prepare and validate BIDS-style data organization for downstream processing. 3. Delegate modality pipelines to `smri-skill`, `fmri-skill`, `dwi-skill`, and `eeg-skill`. It also provides **phenotype extraction** and **QC integration** paths: - Extract and merge HBN phenotype tables (psychiatric, behavioral, cognitive, lifestyle, genetics, actigraphy). - Generate per-subject QC summaries with exclusion lists. This skill follows NeuroClaw hierarchy: - Defines **WHAT to do**, not low-level implementation details. - Does **not** execute direct shell commands itself. - Delegates all execution via `claw-shell` to base/tool skills. **Research use only.** --- ## Download Stage (Mandatory First Step) ### Source HBN data is distributed through the **FCP/INDI** repository: - Website: https://fcon_1000.projects.nitrc.org/indi/cmi_healthy_brain_network/ ### Supported HBN Data Packages - **Imaging data**: T1w, T2w, dMRI, rs-fMRI, task-fMRI (NIfTI for

What's inside
Steps it walks through
  1. Overview
  2. Download Stage (Mandatory First Step)
  3. Source
  4. Supported HBN Data Packages
  5. Delegation Rules for Download
  6. Download Inputs to Confirm in Plan
  7. Narrow Path: HBN Raw NIfTI -> BIDS Staging
  8. When this narrow path should dominate
  9. Narrow-path contract
  10. Expected narrow-path behavior
  11. Core Workflow (Never Bypassed)
  12. Input Layout (Example)
  13. BIDS Preparation
  14. Script: scripts/reorganizehbn.py
Commands it runs
python skills/hbn-skill/scripts/reorganize_hbn.py \
python skills/hbn-skill/scripts/extract_hbn_phenotype.py \
python skills/hbn-skill/scripts/hbn_qc_summary.py \
More from awesome-bio-agent-skills
All skills →
About this skill
What does the hbn-skill skill do?

Use this skill whenever the user wants an end-to-end workflow for the Healthy Brain Network (HBN) dataset, including download, BIDS organization, and multimodal processing of sMRI, dMRI, rs-fMRI, task-fMRI, and EEG data. Triggers include: 'HBN', 'Healthy Brain Network', 'process HBN', 'HBN fMRI', 'HBN EEG', or any request to run the HBN multimodal pipeline. This is the NeuroClaw dataset-orchestration layer for HBN.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill hbn-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going