datalad-siblings

Configure and manage DataLad dataset siblings and their remotes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and configure sibling remotes — named locations where dataset history and annexed content can be pushed and pulled.

Core Features & Use Cases

  • Query configured siblings to understand current remotes and their statuses.
  • Add and configure a new sibling with URL, push URL, and publish-depends to ensure annexed content is pushed correctly.
  • Enable or remove siblings, and construct platform-specific commands for GitHub, GitLab, RIA stores, or GIN backends.

Quick Start

Add a new DataLad sibling by specifying a name and a remote URL for the target dataset.

Frequently Asked Questions about datalad-siblings

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

FAQPage Schema
How do I add a new sibling remote to a DataLad dataset?

To add a DataLad sibling, specify a name, remote URL, and optional push URL for the target dataset. The tool configures publish-depends to ensure annexed content routes correctly, and displays the full command before execution.

Can I configure DataLad siblings for specific platforms like GitHub or GitLab?

DataLad siblings can be configured for specific platforms including GitHub, GitLab, RIA stores, and GIN backends. The tool constructs platform-specific commands with appropriate flags to manage annex-enabled remotes across these services.

What is the best way to check existing DataLad remotes and their statuses?

Querying configured siblings lets you inspect current DataLad remotes and their statuses. The tool queries named locations where dataset history and annexed content can be pushed or pulled, providing a clear view of all connected backends.

How do I enable or remove a sibling from a git-annex dataset?

Enabling or removing a sibling from a git-annex dataset involves targeting the specific remote by name. The tool executes the configuration change while always displaying the full DataLad command before performing the removal or enable action.

Does configuring DataLad siblings require separate push URL setup?

Configuring DataLad siblings supports separate push URLs alongside the remote URL. Adding a new sibling lets you specify both values and uses publish-depends to ensure annexed content is pushed correctly to the designated target.

Why are my annexed files not pushing to my DataLad sibling remote?

Annexed files may fail to push if the sibling lacks publish-depends configuration. Adding a sibling with the correct push URL and publish-depends flag ensures annexed content routes properly to the target remote backend.