bids

Organize and convert neuroscience datasets into BIDS-compliant directory structures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gabrielvuksani/wotann --skill bids-gabrielvuksani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bids
Source: https://github.com/gabrielvuksani/wotann/tree/main/skills/scientific/bids
Command: npx skills add https://github.com/gabrielvuksani/wotann --skill bids-gabrielvuksani

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you correctly structure and verify Brain Imaging Data Structure (BIDS) datasets so neuroscience and biomedical files are consistently organized, discoverable, and ready for downstream tools.

Core Features & Use Cases

  • BIDS dataset structuring & discovery: Organize modalities into the correct sub-* / ses-* / <datatype>/ hierarchy and query datasets using BIDS entities (subject, session, task, run, acquisition, etc.).
  • BIDS compliance validation & fixes: Validate datasets against the BIDS specification and use .bidsignore to manage what gets checked.
  • Conversion and metadata authoring: Convert DICOM to BIDS with common pipelines (HeuDiConv, dcm2bids, BIDScoin), generate dataset_description.json, and write/maintain JSON sidecar metadata and events/participants files.

Quick Start

Use the bids skill to validate that your dataset follows BIDS and to guide you in adding any missing dataset_description.json, sidecar fields, and required event/metadata files for tasks like func/bold.

Frequently Asked Questions about bids

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

FAQPage Schema
How do I convert DICOM files to a BIDS-compliant directory structure?

To convert DICOM to BIDS, you organize raw imaging data into the `sub-*/ses-*/<datatype>/` hierarchy using conversion pipelines like HeuDiConv, dcm2bids, or BIDScoin, generating required `dataset_description.json` and JSON sidecars for compliance.

What does BIDS dataset validation check for in neuroimaging data?

BIDS validation checks neuroimaging datasets for correct entity-based file naming, metadata inheritance, required JSON sidecars, and proper `sub-*/ses-*/<datatype>/` directory hierarchy against the BIDS specification using validator-compatible layouts.

How do I create valid `_events.tsv` and `dataset_description.json` files for fMRI BIDS datasets?

You create valid `_events.tsv` and `dataset_description.json` files by applying BIDS schema knowledge to author required metadata sidecars and task event files, ensuring proper entity-based naming for functional bold data.

Can I use pybids to query and organize MRI and EEG datasets by subject and session entities?

Yes, you can use pybids to query MRI, EEG/MEG/iEEG, and DWI datasets by applying BIDS entities like subject, session, task, run, and acquisition to organize modalities into the correct directory hierarchy.

What's the best way to manage BIDS validation errors for derivatives and metadata sidecars?

Manage BIDS validation errors for derivatives and metadata sidecars by using a `.bidsignore` file to specify which paths the validator should skip, while correcting missing required fields in your JSON sidecars and event files.

When do I need BIDS metadata inheritance for organizing biomedical datasets?

You need BIDS metadata inheritance when organizing biomedical datasets with multiple sessions or modalities, allowing shared JSON sidecar metadata to propagate down to lower-level files while validating compliance across the directory structure.