Agent skill · Data & Analytics

aibl-skill

Use this skill whenever the user wants an end-to-end workflow for the AIBL (Australian Imaging, Biomarkers and Lifestyle) dataset, including data access guidance, BIDS organization, and multimodal processing of sMRI and PET (PiB, FDG, tau). Triggers include: 'AIBL', 'AIBL data', 'process AIBL', 'AIBL PET', 'AIBL MRI', or any request to run the AIBL multimodal pipeline. This is the NeuroClaw dataset-orchestration layer for AIBL.

BioTender-maxgithub.com/BioTender-maxGitHub ↗
claude-codeNOASSERTION
Install
npx skills add BioTender-max/awesome-bio-agent-skills --skill aibl-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: 13 KB
Bundled scripts: none
Requires: - smri-skill - bids-organizer - claw-shell
Path: skills/neuroclaw/aibl-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

# AIBL Skill (Dataset-Orchestration Layer) ## Overview `aibl-skill` is the NeuroClaw orchestration skill for the **AIBL (Australian Imaging, Biomarkers and Lifestyle)** dataset. It coordinates a fixed three-phase workflow: 1. Guide AIBL data access and download from the AIBL research portal. 2. Prepare and validate BIDS-style data organization for downstream processing. 3. Delegate modality pipelines to `smri-skill` for structural MRI and PET processing. It also provides **phenotype extraction** and **QC integration** paths: - Extract and merge AIBL phenotype tables (cognitive assessments, blood biomarkers, APOE genotype, lifestyle data). - 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 AIBL data is distributed through the **AIBL research portal**: - Website: https://aibl.csiro.au/ - Data access: requires registration and data use agreement - Imaging data available via LONI Imag

What's inside
Steps it walks through
  1. Overview
  2. Download Stage (Mandatory First Step)
  3. Source
  4. Supported AIBL Data Packages
  5. Delegation Rules for Download
  6. Download Inputs to Confirm in Plan
  7. Narrow Path: AIBL Raw Data -> 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/reorganizeaibl.py
Commands it runs
python skills/aibl-skill/scripts/reorganize_aibl.py \
python skills/aibl-skill/scripts/extract_aibl_phenotype.py \
python skills/aibl-skill/scripts/aibl_qc_summary.py \
More from awesome-bio-agent-skills
All skills →
About this skill
What does the aibl-skill skill do?

Use this skill whenever the user wants an end-to-end workflow for the AIBL (Australian Imaging, Biomarkers and Lifestyle) dataset, including data access guidance, BIDS organization, and multimodal processing of sMRI and PET (PiB, FDG, tau). Triggers include: 'AIBL', 'AIBL data', 'process AIBL', 'AIBL PET', 'AIBL MRI', or any request to run the AIBL multimodal pipeline. This is the NeuroClaw dataset-orchestration layer for AIBL.

How do I install it?

Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill aibl-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