datalad-subdatasets

Locate and report present or absent subdatasets within a DataLad dataset.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/bcmcpher/my-skills --skill datalad-subdatasets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datalad-subdatasets
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/datalad-cli/skills/datalad-subdatasets
Command: npx skills add https://github.com/bcmcpher/my-skills --skill datalad-subdatasets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps investigators locate and report the status of subdatasets within a DataLad dataset, streamlining subdataset management across projects.

Core Features & Use Cases

  • List and enumerate subdatasets with their state (present or absent) and the pinned commit SHAs.
  • Filter and inspect subdatasets across single or nested trees, and view how they relate to .gitmodules.
  • Execute cross-subdataset commands using datalad foreach-dataset to run actions consistently across the tree.
  • Guided follow-ups to initialize absent subdatasets, update present ones, or adjust subdataset properties safely.

Quick Start

Ask the tool to list all subdatasets and show their present/absent state.

Frequently Asked Questions about datalad-subdatasets

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

FAQPage Schema
How do I check the status of subdatasets in a DataLad dataset?

To check subdataset status in a DataLad dataset, use the subdatasets command to list all nested subdatasets, showing whether each is present or absent along with its pinned commit SHA.

Can I run a command across all DataLad subdatasets at once?

Yes, you can run cross-subdataset commands using datalad foreach-dataset to execute actions consistently across the entire nested dataset tree.

How does DataLad manage subdataset properties in .gitmodules?

DataLad manages subdataset properties in .gitmodules by allowing you to inspect relationships across nested trees and apply targeted modifications using datalad subdatasets --set-property with user confirmation safeguards.

What is the best way to find absent subdatasets in a DataLad project?

The best way to find absent subdatasets is to run a read-only datalad subdatasets query, which reports the present or absent state of each subdataset to guide subsequent initialization.

Can I update subdataset properties across nested DataLad trees?

Yes, you can update subdataset properties across nested DataLad trees by applying datalad subdatasets --set-property, which includes safeguards and user confirmation prompts for safe modifications.

Do I need to initialize absent subdatasets before inspecting a DataLad dataset?

No, you do not need to initialize absent subdatasets first; the subdatasets command performs read-only queries to report which subdatasets are present or absent, then offers guided follow-ups to initialize them.