hcpep-skill

Orchestrates download, BIDS staging, and multimodal processing of the HCP Early Psychosis dataset.

89|5|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/CUHK-AIM-Group/NeuroDiscovery --skill hcpep-skill-cuhk-aim-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hcpep-skill
Source: https://github.com/CUHK-AIM-Group/NeuroDiscovery/tree/main/skills/hcpep-skill
Command: npx skills add https://github.com/CUHK-AIM-Group/NeuroDiscovery --skill hcpep-skill-cuhk-aim-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pandas, and includes scripts (resource) components.

What problem does it solve? Processing the HCP Early Psychosis (HCP-EP) dataset requires coordinating ConnectomeDB downloads, BIDS reorganization, and separate sMRI, fMRI, and dMRI pipelines, which is error-prone when done manually across a clinical cohort. ## Core Features & Use Cases - End-to-End Orchestration: Plans and delegates the full HCP-EP workflow from ConnectomeDB download through BIDS staging to modality-specific processing via dedicated skills. - BIDS Reorganization: Converts HCP-EP native directory layouts into BIDS-compliant datasets with task mapping, sidecar metadata, and dataset_description.json generation. - Phenotype and QC Tooling: Extracts clinical measures (PANSS, BPRS, MATRICS, medication, diagnosis) into merged CSVs and generates per-subject QC summaries with exclusion lists. - Use Case: A researcher studying early psychosis downloads the HCP-EP cohort, stages it to BIDS, runs structural, functional, and diffusion pipelines, then merges diagnostic and cognitive phenotype data for a case-control group analysis. ## Quick Start Ask the agent to download the HCP Early Psychosis dataset from ConnectomeDB, organize it into BIDS format, and run the full sMRI, fMRI, and dMRI processing pipeline with phenotype extraction.

Frequently Asked Questions about hcpep-skill

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

FAQPage Schema
How do I process the HCP Early Psychosis dataset end to end?

The skill generates a numbered execution plan covering ConnectomeDB download, BIDS staging, and sMRI, fMRI, and dMRI processing, then delegates each step to the appropriate modality skill after your explicit confirmation. Outputs are organized under an hcpep_output directory.

How to convert HCP-EP native data to BIDS format?

Run the reorganize_hcpep.py script with input and output directories to map HCP native layouts into BIDS structure. It normalizes subject IDs, routes T1w, T2w, task-fMRI, resting-state, and diffusion files, and generates dataset_description.json, with a dry-run mode for previewing.

What clinical phenotype data can be extracted from HCP-EP?

The phenotype extraction script merges diagnosis, PANSS, BPRS, SAPS, SANS, GAF scores, medication and chlorpromazine equivalents, MATRICS cognitive domains, and illness duration measures. It merges multiple source files by subject ID and can filter to subjects with imaging data.

Does the HCP-EP workflow require a ConnectomeDB account?

Yes, downloading HCP-EP data requires a ConnectomeDB account and acceptance of the HCP data use agreement. If raw data already exists locally, the download stage can be skipped and the workflow proceeds directly to BIDS staging.

What QC thresholds are used for HCP-EP fMRI data?

The QC script flags subjects whose mean framewise displacement exceeds a default threshold of 0.3 mm, applied equally to patients and controls. It also pulls FreeSurfer eTIV from aseg.stats and can attach diagnosis labels to the QC summary.

What are the limitations of this HCP-EP orchestration skill?

The skill is orchestration-only and contains no preprocessing implementation; all modality processing is delegated to separate smri, fmri, and dwi skills. Clinical patient data also requires careful de-identification, and motion thresholds may need adjustment for early psychosis cohorts.