[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F3HPCH20BFCJA324ATRCZT":3,"skill-same:01M7F3HPCH20BFCJA324ATRCZT":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7F3HPCH20BFCJA324ATRCZT","datalad",null,"Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a small pointer instead of real data; when an analysis needs a machine-readable record of how each output was produced so it can be re-executed; or when publishing a dataset to siblings such as a GitHub repository plus a storage remote. Also use to decide between DataLad and plain Git for a data-carrying repository.","beanspowt\u002Fbeancode","beanspowt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F333943283?v=4","01M7F39F0GDWKS57BCKW8JJH7F","01M7F39F1B1TVPDJMS37BZQHWM",0,"MIT","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fconfig\u002Fopencode\u002Fskills\u002Fdatalad\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: datalad\ndescription: Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink or a small pointer instead of real data; when an analysis needs a machine-readable record of how each output was produced so it can be re-executed; or when publishing a dataset to siblings such as a GitHub repository plus a storage remote. Also use to decide between DataLad and plain Git for a data-carrying repository.\ncompatibility: Requires Python 3.10+, DataLad 1.6.5, Git, and git-annex 10.x. Tested with git-annex 10.20260901 and datalad-container 1.2.6 on macOS ARM64. Containers additionally require Singularity, Apptainer, or Docker. Remote data access needs network access and may need provider credentials. Local filesystem workflows work offline.\nlicense: MIT\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: \"1.2\"\n  last-reviewed: \"2026-09-30\"\n  skill-author: Dylan Pulver\n---\n\n# DataLad\n\n## Overview\n\nDataLad is a data management layer over Git and git-annex. Git tracks the dataset\nstructure, small text files, and the history. git-annex tracks the *content* of large\nfiles, storing each file as a key and keeping the bytes somewhere that is not necessarily\nthe local repository.\n\nA normal clone retrieves Git history and the top-level file listing while leaving\nannexed bytes unfetched. Installed subdatasets have their own histories; a clone does not\nautomatically populate them. Clone cost depends on Git history and file count, not just\nthe data volume. Retrieve annexed bytes selectively with `datalad get`.\n\nThe second thing DataLad adds is provenance. `datalad run` executes a command and commits\nthe result together with a machine-readable record of the command, its inputs, and its\noutputs. `datalad rerun` reads that record back and re-executes it. This turns \"how was\nthis figure produced\" from an archaeology problem into a command.\n\n## When to use DataLad instead of plain Git\n\nUse DataLad when any of the following holds:\n\n- Files are too large for Git to handle comfortably, or the total exceeds what every\n  collaborator wants on disk.\n- Data lives in more than one place (a lab server, a cluster scratch, S3, a supercomputer)\n  and you need to know which copies exist.\n- The analysis must be re-executable, and a plain commit message is not enough evidence.\n- You are consuming published datasets from OpenNeuro, DANDI, or `datasets.datalad.org`,\n  which are distributed as DataLad datasets.\n- The project nests other datasets inside it and you want each one to keep its own\n  independent history.\n\nUse plain Git when the repository is code and text only, everything fits comfortably in\nGit, and nobody needs partial checkouts. DataLad on top of a small pure-code repository\nadds indirection without buying anything.\n\n## Installation\n\n```bash\n# git-annex is NOT written in Python but is available from PyPI if you already\n# have git itself installed:\nuv pip install git-annex\n# You can also install it first from the system\n# (Debian\u002FUbuntu: apt install git-annex; macOS: brew install git-annex;\n#  conda-forge: conda install -c conda-forge git-annex)\nuv pip install \"datalad==1.6.5\"\nuv pip install \"datalad-container==1.2.6\"   # only for containers-run\n\ndatalad wtf --section dependencies   # confirm git-annex version is visible\n```\n\nThe PyPI `git-annex` package supplies platform-specific binaries. The reviewed\n10.20260901.post1 wheels cover Linux glibc 2.34+ (x86_64\u002FARM64), macOS ARM64 14+ and\nx86_64 15+, and Windows x86_64. Use a system package when no wheel matches. Keep its\nenvironment on `PATH` and verify the executable; the wheel does not supply Git itself.\nConfigure Git author name\u002Femail before creating or saving a dataset.\n\n`datalad wtf` prints the resolved environment and is the first thing to run when behaviour\nlooks impossible. An old or missing git-annex is behind a large share of confusing errors.\n\nDataLad is MIT licensed; git-annex has a separate AGPL license. Consult the upstream\nlicense when redistributing either tool.\n\n## The failure that bites first: pointers are not data\n\nAfter `datalad clone`, annexed files exist as symlinks into `.git\u002Fannex\u002Fobjects\u002F` (or as\nsmall pointer files where symlinks are unavailable, such as on Windows or a crippled\nfilesystem). Nothing has downloaded the content yet.\n\nIllustrative remote-data example; inspect the selected revision for the exact path and\ninstall NiBabel before the Python read. The refresh tested equivalent local pointer\u002Fget\nbehavior without downloading imaging data.\n\n```bash\ndatalad clone https:\u002F\u002Fgithub.com\u002FOpenNeuroDatasets\u002Fds000001.git\ncd ds000001\nls sub-01\u002Fanat\u002F            # the file is listed\npython -c \"import nibabel; nibabel.load('sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz')\"   # fails\ndatalad get sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz                                   # now it works\n```\n\nThe failure mode to recognise: a tool reports the file as empty, truncated, corrupt, \"not\na gzip file\", or a broken symlink, and the file size on disk is a few hundred bytes. These symptoms can indicate an unfetched annex pointer; confirm with annex status\nbefore diagnosing corruption. **Run `datalad get` before reading data, and treat\n\"file exists\" as insufficient evidence that its content is present.**\n\nBefore an analysis touches a directory, fetch it explicitly:\n\n```bash\ndatalad get sub-01\u002F                  # everything under a path\ndatalad get -r .                     # everything, including subdatasets\ndatalad get -n -r .                  # subdataset structure only, no file content\n```\n\n`datalad status --annex availability` checks which content is present locally, and\n`git annex whereis \u003Cpath>` reports which repositories hold a given file. `whereis` reads\nrecorded state and does not contact the remotes, so it tells you what git-annex last\nlearned rather than what is true right now.\n\nSee [data-access.md](references\u002Fdata-access.md) for finding datasets, subdataset\nbehaviour, dropping content safely, and repairing a dataset.\n\n## Recording provenance with datalad run\n\n`datalad run` is the reason to reach for DataLad in a methods context. It saves the\ncommand alongside its effect, in the same commit:\n\nIllustrative FSL example (requires `bet` and an existing `derivatives\u002F` directory):\n\n```bash\ndatalad run -m \"extract brain and mask\" \\\n  --input \"sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain_mask.nii.gz\" \\\n  \"bet {inputs[0]} {outputs[0]} -m\"\n```\n\nWhat each part does, and why skipping it hurts:\n\n- `--input` retrieves the content before running, so the command does not fail on a\n  pointer. It also records the dependency, which is what lets `rerun` fetch the same\n  inputs on a different machine.\n- `--output` unlocks or removes the target first, so git-annex does not refuse to write\n  over content it is protecting. Without it, a second run of the same command commonly\n  fails with a permission error on an annexed file that looks read-only.\n- `{inputs}` and `{outputs}` expand to those values. `{pwd}`, `{dspath}`, and `{tmpdir}`\n  are also available, and `{inputs[0]}` indexes individual entries.\n- The commit message carries a JSON run record between `=== Do not change lines below ===`\n  and `^^^ Do not change lines above ^^^`. Do not hand-edit that block; `rerun` parses it.\n\n`datalad run` refuses to start when the dataset has unsaved modifications, because an\nunclean starting state makes the record unreliable. Save or discard first, or pass\n`--explicit` to save only declared outputs. This does not capture unsaved input changes;\nsave all dependencies before claiming the run is reproducible. Check a\ncommand before committing to it with `--dry-run basic` or `--dry-run command`.\n\nA run that changes nothing produces no commit, exactly as `datalad save` does.\n\n`run` records the command and dataset state; it does not freeze arbitrary host-installed software or external services. Version an environment lockfile and scripts as declared inputs, or use a tracked container image with `containers-run`. Record random seeds and relevant runtime settings, then test `rerun` from a fresh environment before claiming computational reproducibility.\n\n### Re-executing\n\n```bash\ndatalad rerun                       # redo the run recorded at HEAD\ndatalad rerun --report              # show what would be done, change nothing\ndatalad rerun --script recompute.sh # extract the commands instead of running them\ndatalad rerun --since \u003Ccommit> -b check \u003Crevision>   # replay a range onto a new branch\n```\n\n`--report` only inspects the plan; it does not execute or validate the result. A branch\n(`-b`) preserves the original commits, but uses the same worktree. See the reference for\na `--since`\u002F`--onto` replay that starts before the first run, and compare annex keys or\ncontent checksums as well as scientific outputs.\n\n### Containers\n\nWith the `datalad-container` extension, register an image once and every subsequent run\nrecords which image produced the outputs:\n\nIllustrative container workflow using a previously built local SIF image (not executed\nin this refresh; the runtime and image must be available):\n\n```bash\ndatalad containers-add fsl --url \u002Fpath\u002Fto\u002Ffsl.sif \\\n  --call-fmt 'apptainer exec {img} {cmd}'\ndatalad containers-run -n fsl -m \"brain and mask in container\" \\\n  --input \"sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain_mask.nii.gz\" \\\n  \"bet {inputs[0]} {outputs[0]} -m\"\n```\n\nThe image itself is tracked in the dataset, so the software environment travels with the\ndata and the provenance record rather than living in someone's shell history. When only\none container is configured, `-n` may be omitted.\n\nSee [provenance.md](references\u002Fprovenance.md) for the STAMPED principles and the YODA\nproject layout, the run record format, `--explicit` and `--assume-ready` semantics, and\nexporting provenance toward W3C PROV.\n\n## Saving and inspecting changes\n\n```bash\ndatalad status                 # what changed, including subdataset state\ndatalad save -m \"add QC report\" path\u002Fto\u002Ffile\ndatalad save -m \"checkpoint\" -r                 # recurse into subdatasets\ndatalad save -m \"small text file\" --to-git notes.md\n```\n\n`datalad save` decides per file whether content goes to Git or to git-annex, following the\ndataset's `.gitattributes`. Force a file into Git with `--to-git`, which is the right call\nfor code and small text files that should stay directly readable. The `yoda` procedure\n(`datalad create -c yoda`) sets this up for `code\u002F`, `README.md`, and `CHANGELOG.md`\nautomatically.\n\n## Creating a dataset\n\n```bash\ndatalad create my_dataset               # plain dataset\ndatalad create -c yoda my_analysis      # analysis layout (code\u002F tracked in Git,\n                                        # README.md and CHANGELOG.md preconfigured)\ndatalad create -d . inputs\u002Fraw          # register a new subdataset under an existing one\n```\n\n`-c yoda` applies the analysis project layout described in\n[provenance.md](references\u002Fprovenance.md). `-d .` is what registers a new dataset as a\nsubdataset of the parent rather than leaving an unrelated repository inside it.\n\n## Publishing\n\nA DataLad dataset is usually published to two places at once: a Git hosting service for\nthe history, and a storage remote for the annexed content.\n\nIllustrative authenticated publication (creates remote resources; requires a GitHub\ntoken and S3 credentials). Use `myorg\u002Fmydataset` only for an organization namespace.\n\n```bash\ndatalad create-sibling-github mydataset\ngit annex initremote store type=S3 bucket=my-bucket protocol=https \\\n  encryption=none autoenable=true\ndatalad siblings configure -s github --publish-depends store\ndatalad push --to github\n```\n\nThe Git sibling and the storage sibling are created by different tools on purpose. A Git\nsibling is a Git remote, and `datalad create-sibling-*` handles the hosting-service ones.\nAn S3 bucket (or WebDAV, or an SSH directory) is a *git-annex special remote*, not a Git\nremote, so it is created with `git annex initremote`. `datalad siblings` picks the special\nremote up afterwards and treats it like any other. Using `datalad siblings add --url\ns3:\u002F\u002F...` here is the mistake this section exists to prevent: `--url` is a Git remote URL,\nS3 is not, and the `push --to github` below then fails on the `--publish-depends` hop.\n\n`--publish-depends` is what stops the common broken publication: a Git repository whose\nhistory references content that was never uploaded, so collaborators clone successfully\nand then find every `datalad get` failing. Declaring the dependency makes the storage\nsibling publish first, every time.\n\n`datalad push` sends both the Git history and, by default (`--data auto-if-wanted`), the\nannexed content selected by a target's wanted settings; without wanted settings it\ntransfers all selected current content. `--data anything` bypasses preferred-content\nfiltering, but does not recover missing local bytes or archive every historical version.\n\nSee [publishing.md](references\u002Fpublishing.md) for RIA stores, special remotes, credential\nhandling, and configuring which sibling holds what.\n\n## Freeing disk space\n\n```bash\ngit annex whereis sub-01\u002F                 # inspect recorded locations first\ndatalad drop sub-01\u002F                      # remove local content, keep the pointer\n```\n\n`datalad drop` checks required copies and availability by default. `--nocheck` is\ndeprecated in favor of `--reckless availability`, which disables those protections.\n`--if-dirty` is deprecated and ignored; it is not an availability-check option.\n`--what` selects between `filecontent` (the default), `allkeys`, `datasets`, and `all`.\n\n## Failure modes worth knowing\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| File reads as empty, truncated, or a broken symlink | Content not retrieved; only the pointer is present | `datalad get \u003Cpath>` |\n| \"Permission denied\" writing an existing output | git-annex write-protects annexed content | Declare it with `--output`, or `datalad unlock \u003Cpath>` |\n| `datalad run` refuses to start | Dataset has unsaved changes | `datalad save` first, or pass `--explicit` |\n| `datalad drop` refuses | No verified second copy of the content | Push to a reachable sibling, then retry the safety check |\n| Collaborator clones but every `get` fails | History published without the content | Publish the storage sibling, and set `--publish-depends` |\n| Clone succeeds, subdataset directories are empty | Subdatasets are not installed by default | `datalad get -n -r .`, then `get` the paths you need |\n| Commands behave impossibly | git-annex missing or too old | `datalad wtf --section dependencies` |\n\n## Detailed references\n\n- [data-access.md](references\u002Fdata-access.md): finding published datasets\n  (`registry.datalad.org`, OpenNeuro, DANDI, `datasets.datalad.org` and the `\u002F\u002F\u002F`\n  shortcut), clone and get options, subdataset handling, annex content states, dropping\n  and removing, and `fsck` repair.\n- [provenance.md](references\u002Fprovenance.md): the STAMPED principles and the YODA layout,\n  the run record format, `run` and `rerun` options in full, `containers-run`, and the\n  current state of exporting DataLad provenance toward W3C PROV.\n- [publishing.md](references\u002Fpublishing.md): siblings and their actions,\n  `create-sibling-*` variants, RIA stores, special remotes, `push` semantics, and\n  credential handling.\n\n## Related skills\n\nThe `bids` skill covers the Brain Imaging Data Structure that most of the neuroimaging\ndatasets distributed through DataLad are organised in. A typical workflow clones a BIDS\ndataset with DataLad, validates it with the BIDS tooling, then runs a BIDS-App under\n`datalad containers-run` so the derivatives carry provenance.\n\n## Validation scope\n\nReviewed 2026-09-30 against DataLad 1.6.5 and datalad-container 1.2.6 source and\ncurrent official manuals. Tiny local tests cover clone\u002Fget\u002Fdrop, unlocked saves,\nsubdataset installation, run\u002Frerun, default push selection, and RIA publish\u002Fclone\u002Fget.\nRemote hosting, credentials, FSL, and container execution examples are illustrative;\nno authenticated remote publication or scientific-data downloads were performed.\n\n## Primary sources\n\n- DataLad documentation: \u003Chttps:\u002F\u002Fdocs.datalad.org\u002Fen\u002Fstable\u002F>\n- DataLad Handbook: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002F>\n- `datalad run` chapter: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002Fbasics\u002F101-108-run.html>\n- YODA principles: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002Fbasics\u002F101-127-yoda.html>\n- STAMPED principles (operationalized from YODA): \u003Chttps:\u002F\u002Fstamped-principles.org>\n- datalad-container: \u003Chttps:\u002F\u002Fdocs.datalad.org\u002Fprojects\u002Fcontainer\u002Fen\u002Fstable\u002F>\n- git-annex: \u003Chttps:\u002F\u002Fgit-annex.branchable.com\u002F>\n- Dataset registry: \u003Chttps:\u002F\u002Fregistry.datalad.org>\n\n## Acknowledgment\n\nTopic scope for this skill was informed in part by @bcmcpher's MIT-licensed\n[datalad-cli](https:\u002F\u002Fgithub.com\u002Fbcmcpher\u002Fmy-skills\u002Ftree\u002Fmain\u002Fplugins\u002Fdatalad-cli)\nplugin (nineteen per-command slash-command skills). The text here is written\nindependently and grounded in the upstream DataLad documentation; overlap is unavoidable\nbecause both cover DataLad, but the structure, style, and specific technical claims are\ndifferent.\n","# DataLad\n\n## Overview\n\nDataLad is a data management layer over Git and git-annex. Git tracks the dataset\nstructure, small text files, and the history. git-annex tracks the *content* of large\nfiles, storing each file as a key and keeping the bytes somewhere that is not necessarily\nthe local repository.\n\nA normal clone retrieves Git history and the top-level file listing while leaving\nannexed bytes unfetched. Installed subdatasets have their own histories; a clone does not\nautomatically populate them. Clone cost depends on Git history and file count, not just\nthe data volume. Retrieve annexed bytes selectively with `datalad get`.\n\nThe second thing DataLad adds is provenance. `datalad run` executes a command and commits\nthe result together with a machine-readable record of the command, its inputs, and its\noutputs. `datalad rerun` reads that record back and re-executes it. This turns \"how was\nthis figure produced\" from an archaeology problem into a command.\n\n## When to use DataLad instead of plain Git\n\nUse DataLad when any of the following holds:\n\n- Files are too large for Git to handle comfortably, or the total exceeds what every\n  collaborator wants on disk.\n- Data lives in more than one place (a lab server, a cluster scratch, S3, a supercomputer)\n  and you need to know which copies exist.\n- The analysis must be re-executable, and a plain commit message is not enough evidence.\n- You are consuming published datasets from OpenNeuro, DANDI, or `datasets.datalad.org`,\n  which are distributed as DataLad datasets.\n- The project nests other datasets inside it and you want each one to keep its own\n  independent history.\n\nUse plain Git when the repository is code and text only, everything fits comfortably in\nGit, and nobody needs partial checkouts. DataLad on top of a small pure-code repository\nadds indirection without buying anything.\n\n## Installation\n\n```bash\n# git-annex is NOT written in Python but is available from PyPI if you already\n# have git itself installed:\nuv pip install git-annex\n# You can also install it first from the system\n# (Debian\u002FUbuntu: apt install git-annex; macOS: brew install git-annex;\n#  conda-forge: conda install -c conda-forge git-annex)\nuv pip install \"datalad==1.6.5\"\nuv pip install \"datalad-container==1.2.6\"   # only for containers-run\n\ndatalad wtf --section dependencies   # confirm git-annex version is visible\n```\n\nThe PyPI `git-annex` package supplies platform-specific binaries. The reviewed\n10.20260901.post1 wheels cover Linux glibc 2.34+ (x86_64\u002FARM64), macOS ARM64 14+ and\nx86_64 15+, and Windows x86_64. Use a system package when no wheel matches. Keep its\nenvironment on `PATH` and verify the executable; the wheel does not supply Git itself.\nConfigure Git author name\u002Femail before creating or saving a dataset.\n\n`datalad wtf` prints the resolved environment and is the first thing to run when behaviour\nlooks impossible. An old or missing git-annex is behind a large share of confusing errors.\n\nDataLad is MIT licensed; git-annex has a separate AGPL license. Consult the upstream\nlicense when redistributing either tool.\n\n## The failure that bites first: pointers are not data\n\nAfter `datalad clone`, annexed files exist as symlinks into `.git\u002Fannex\u002Fobjects\u002F` (or as\nsmall pointer files where symlinks are unavailable, such as on Windows or a crippled\nfilesystem). Nothing has downloaded the content yet.\n\nIllustrative remote-data example; inspect the selected revision for the exact path and\ninstall NiBabel before the Python read. The refresh tested equivalent local pointer\u002Fget\nbehavior without downloading imaging data.\n\n```bash\ndatalad clone https:\u002F\u002Fgithub.com\u002FOpenNeuroDatasets\u002Fds000001.git\ncd ds000001\nls sub-01\u002Fanat\u002F            # the file is listed\npython -c \"import nibabel; nibabel.load('sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz')\"   # fails\ndatalad get sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz                                   # now it works\n```\n\nThe failure mode to recognise: a tool reports the file as empty, truncated, corrupt, \"not\na gzip file\", or a broken symlink, and the file size on disk is a few hundred bytes. These symptoms can indicate an unfetched annex pointer; confirm with annex status\nbefore diagnosing corruption. **Run `datalad get` before reading data, and treat\n\"file exists\" as insufficient evidence that its content is present.**\n\nBefore an analysis touches a directory, fetch it explicitly:\n\n```bash\ndatalad get sub-01\u002F                  # everything under a path\ndatalad get -r .                     # everything, including subdatasets\ndatalad get -n -r .                  # subdataset structure only, no file content\n```\n\n`datalad status --annex availability` checks which content is present locally, and\n`git annex whereis \u003Cpath>` reports which repositories hold a given file. `whereis` reads\nrecorded state and does not contact the remotes, so it tells you what git-annex last\nlearned rather than what is true right now.\n\nSee [data-access.md](references\u002Fdata-access.md) for finding datasets, subdataset\nbehaviour, dropping content safely, and repairing a dataset.\n\n## Recording provenance with datalad run\n\n`datalad run` is the reason to reach for DataLad in a methods context. It saves the\ncommand alongside its effect, in the same commit:\n\nIllustrative FSL example (requires `bet` and an existing `derivatives\u002F` directory):\n\n```bash\ndatalad run -m \"extract brain and mask\" \\\n  --input \"sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain_mask.nii.gz\" \\\n  \"bet {inputs[0]} {outputs[0]} -m\"\n```\n\nWhat each part does, and why skipping it hurts:\n\n- `--input` retrieves the content before running, so the command does not fail on a\n  pointer. It also records the dependency, which is what lets `rerun` fetch the same\n  inputs on a different machine.\n- `--output` unlocks or removes the target first, so git-annex does not refuse to write\n  over content it is protecting. Without it, a second run of the same command commonly\n  fails with a permission error on an annexed file that looks read-only.\n- `{inputs}` and `{outputs}` expand to those values. `{pwd}`, `{dspath}`, and `{tmpdir}`\n  are also available, and `{inputs[0]}` indexes individual entries.\n- The commit message carries a JSON run record between `=== Do not change lines below ===`\n  and `^^^ Do not change lines above ^^^`. Do not hand-edit that block; `rerun` parses it.\n\n`datalad run` refuses to start when the dataset has unsaved modifications, because an\nunclean starting state makes the record unreliable. Save or discard first, or pass\n`--explicit` to save only declared outputs. This does not capture unsaved input changes;\nsave all dependencies before claiming the run is reproducible. Check a\ncommand before committing to it with `--dry-run basic` or `--dry-run command`.\n\nA run that changes nothing produces no commit, exactly as `datalad save` does.\n\n`run` records the command and dataset state; it does not freeze arbitrary host-installed software or external services. Version an environment lockfile and scripts as declared inputs, or use a tracked container image with `containers-run`. Record random seeds and relevant runtime settings, then test `rerun` from a fresh environment before claiming computational reproducibility.\n\n### Re-executing\n\n```bash\ndatalad rerun                       # redo the run recorded at HEAD\ndatalad rerun --report              # show what would be done, change nothing\ndatalad rerun --script recompute.sh # extract the commands instead of running them\ndatalad rerun --since \u003Ccommit> -b check \u003Crevision>   # replay a range onto a new branch\n```\n\n`--report` only inspects the plan; it does not execute or validate the result. A branch\n(`-b`) preserves the original commits, but uses the same worktree. See the reference for\na `--since`\u002F`--onto` replay that starts before the first run, and compare annex keys or\ncontent checksums as well as scientific outputs.\n\n### Containers\n\nWith the `datalad-container` extension, register an image once and every subsequent run\nrecords which image produced the outputs:\n\nIllustrative container workflow using a previously built local SIF image (not executed\nin this refresh; the runtime and image must be available):\n\n```bash\ndatalad containers-add fsl --url \u002Fpath\u002Fto\u002Ffsl.sif \\\n  --call-fmt 'apptainer exec {img} {cmd}'\ndatalad containers-run -n fsl -m \"brain and mask in container\" \\\n  --input \"sub-01\u002Fanat\u002Fsub-01_T1w.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain.nii.gz\" \\\n  --output \"derivatives\u002Fsub-01_brain_mask.nii.gz\" \\\n  \"bet {inputs[0]} {outputs[0]} -m\"\n```\n\nThe image itself is tracked in the dataset, so the software environment travels with the\ndata and the provenance record rather than living in someone's shell history. When only\none container is configured, `-n` may be omitted.\n\nSee [provenance.md](references\u002Fprovenance.md) for the STAMPED principles and the YODA\nproject layout, the run record format, `--explicit` and `--assume-ready` semantics, and\nexporting provenance toward W3C PROV.\n\n## Saving and inspecting changes\n\n```bash\ndatalad status                 # what changed, including subdataset state\ndatalad save -m \"add QC report\" path\u002Fto\u002Ffile\ndatalad save -m \"checkpoint\" -r                 # recurse into subdatasets\ndatalad save -m \"small text file\" --to-git notes.md\n```\n\n`datalad save` decides per file whether content goes to Git or to git-annex, following the\ndataset's `.gitattributes`. Force a file into Git with `--to-git`, which is the right call\nfor code and small text files that should stay directly readable. The `yoda` procedure\n(`datalad create -c yoda`) sets this up for `code\u002F`, `README.md`, and `CHANGELOG.md`\nautomatically.\n\n## Creating a dataset\n\n```bash\ndatalad create my_dataset               # plain dataset\ndatalad create -c yoda my_analysis      # analysis layout (code\u002F tracked in Git,\n                                        # README.md and CHANGELOG.md preconfigured)\ndatalad create -d . inputs\u002Fraw          # register a new subdataset under an existing one\n```\n\n`-c yoda` applies the analysis project layout described in\n[provenance.md](references\u002Fprovenance.md). `-d .` is what registers a new dataset as a\nsubdataset of the parent rather than leaving an unrelated repository inside it.\n\n## Publishing\n\nA DataLad dataset is usually published to two places at once: a Git hosting service for\nthe history, and a storage remote for the annexed content.\n\nIllustrative authenticated publication (creates remote resources; requires a GitHub\ntoken and S3 credentials). Use `myorg\u002Fmydataset` only for an organization namespace.\n\n```bash\ndatalad create-sibling-github mydataset\ngit annex initremote store type=S3 bucket=my-bucket protocol=https \\\n  encryption=none autoenable=true\ndatalad siblings configure -s github --publish-depends store\ndatalad push --to github\n```\n\nThe Git sibling and the storage sibling are created by different tools on purpose. A Git\nsibling is a Git remote, and `datalad create-sibling-*` handles the hosting-service ones.\nAn S3 bucket (or WebDAV, or an SSH directory) is a *git-annex special remote*, not a Git\nremote, so it is created with `git annex initremote`. `datalad siblings` picks the special\nremote up afterwards and treats it like any other. Using `datalad siblings add --url\ns3:\u002F\u002F...` here is the mistake this section exists to prevent: `--url` is a Git remote URL,\nS3 is not, and the `push --to github` below then fails on the `--publish-depends` hop.\n\n`--publish-depends` is what stops the common broken publication: a Git repository whose\nhistory references content that was never uploaded, so collaborators clone successfully\nand then find every `datalad get` failing. Declaring the dependency makes the storage\nsibling publish first, every time.\n\n`datalad push` sends both the Git history and, by default (`--data auto-if-wanted`), the\nannexed content selected by a target's wanted settings; without wanted settings it\ntransfers all selected current content. `--data anything` bypasses preferred-content\nfiltering, but does not recover missing local bytes or archive every historical version.\n\nSee [publishing.md](references\u002Fpublishing.md) for RIA stores, special remotes, credential\nhandling, and configuring which sibling holds what.\n\n## Freeing disk space\n\n```bash\ngit annex whereis sub-01\u002F                 # inspect recorded locations first\ndatalad drop sub-01\u002F                      # remove local content, keep the pointer\n```\n\n`datalad drop` checks required copies and availability by default. `--nocheck` is\ndeprecated in favor of `--reckless availability`, which disables those protections.\n`--if-dirty` is deprecated and ignored; it is not an availability-check option.\n`--what` selects between `filecontent` (the default), `allkeys`, `datasets`, and `all`.\n\n## Failure modes worth knowing\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| File reads as empty, truncated, or a broken symlink | Content not retrieved; only the pointer is present | `datalad get \u003Cpath>` |\n| \"Permission denied\" writing an existing output | git-annex write-protects annexed content | Declare it with `--output`, or `datalad unlock \u003Cpath>` |\n| `datalad run` refuses to start | Dataset has unsaved changes | `datalad save` first, or pass `--explicit` |\n| `datalad drop` refuses | No verified second copy of the content | Push to a reachable sibling, then retry the safety check |\n| Collaborator clones but every `get` fails | History published without the content | Publish the storage sibling, and set `--publish-depends` |\n| Clone succeeds, subdataset directories are empty | Subdatasets are not installed by default | `datalad get -n -r .`, then `get` the paths you need |\n| Commands behave impossibly | git-annex missing or too old | `datalad wtf --section dependencies` |\n\n## Detailed references\n\n- [data-access.md](references\u002Fdata-access.md): finding published datasets\n  (`registry.datalad.org`, OpenNeuro, DANDI, `datasets.datalad.org` and the `\u002F\u002F\u002F`\n  shortcut), clone and get options, subdataset handling, annex content states, dropping\n  and removing, and `fsck` repair.\n- [provenance.md](references\u002Fprovenance.md): the STAMPED principles and the YODA layout,\n  the run record format, `run` and `rerun` options in full, `containers-run`, and the\n  current state of exporting DataLad provenance toward W3C PROV.\n- [publishing.md](references\u002Fpublishing.md): siblings and their actions,\n  `create-sibling-*` variants, RIA stores, special remotes, `push` semantics, and\n  credential handling.\n\n## Related skills\n\nThe `bids` skill covers the Brain Imaging Data Structure that most of the neuroimaging\ndatasets distributed through DataLad are organised in. A typical workflow clones a BIDS\ndataset with DataLad, validates it with the BIDS tooling, then runs a BIDS-App under\n`datalad containers-run` so the derivatives carry provenance.\n\n## Validation scope\n\nReviewed 2026-09-30 against DataLad 1.6.5 and datalad-container 1.2.6 source and\ncurrent official manuals. Tiny local tests cover clone\u002Fget\u002Fdrop, unlocked saves,\nsubdataset installation, run\u002Frerun, default push selection, and RIA publish\u002Fclone\u002Fget.\nRemote hosting, credentials, FSL, and container execution examples are illustrative;\nno authenticated remote publication or scientific-data downloads were performed.\n\n## Primary sources\n\n- DataLad documentation: \u003Chttps:\u002F\u002Fdocs.datalad.org\u002Fen\u002Fstable\u002F>\n- DataLad Handbook: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002F>\n- `datalad run` chapter: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002Fbasics\u002F101-108-run.html>\n- YODA principles: \u003Chttps:\u002F\u002Fhandbook.datalad.org\u002Fen\u002Flatest\u002Fbasics\u002F101-127-yoda.html>\n- STAMPED principles (operationalized from YODA): \u003Chttps:\u002F\u002Fstamped-principles.org>\n- datalad-container: \u003Chttps:\u002F\u002Fdocs.datalad.org\u002Fprojects\u002Fcontainer\u002Fen\u002Fstable\u002F>\n- git-annex: \u003Chttps:\u002F\u002Fgit-annex.branchable.com\u002F>\n- Dataset registry: \u003Chttps:\u002F\u002Fregistry.datalad.org>\n\n## Acknowledgment\n\nTopic scope for this skill was informed in part by @bcmcpher's MIT-licensed\n[datalad-cli](https:\u002F\u002Fgithub.com\u002Fbcmcpher\u002Fmy-skills\u002Ftree\u002Fmain\u002Fplugins\u002Fdatalad-cli)\nplugin (nineteen per-command slash-command skills). The text here is written\nindependently and grounded in the upstream DataLad documentation; overlap is unavoidable\nbecause both cover DataLad, but the structure, style, and specific technical claims are\ndifferent.\n",{"name":5,"license":14,"metadata":23,"description":7,"allowed-tools":27,"compatibility":28},{"version":24,"skill-author":25,"last-reviewed":26},"1.2","Dylan Pulver","2026-09-30","Read Write Edit Bash","Requires Python 3.10+, DataLad 1.6.5, Git, and git-annex 10.x. Tested with git-annex 10.20260901 and datalad-container 1.2.6 on macOS ARM64. Containers additionally require Singularity, Apptainer, or Docker. Remote data access needs network access and may need provider credentials. Local filesystem workflows work offline.","main","66c9bd32ac14a921980362cf85872a1c402101c2","config\u002Fopencode\u002Fskills\u002Fdatalad","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode","https:\u002F\u002Fgithub.com\u002Fbeanspowt","2026-11-10 23:22:33",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add beanspowt\u002Fbeancode --skill datalad",{"tool":41,"command":42},"bunx","bunx skills add beanspowt\u002Fbeancode --skill datalad",{"tool":44,"command":45},"pnpm","pnpm dlx skills add beanspowt\u002Fbeancode --skill datalad","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fconfig\u002Fopencode\u002Fskills\u002Fdatalad\u002FSKILL.md",true,[49,55,59],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdata-access.md","REFERENCE","参考文档",9714,"https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fconfig\u002Fopencode\u002Fskills\u002Fdatalad\u002Freferences\u002Fdata-access.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fprovenance.md",14087,"https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fconfig\u002Fopencode\u002Fskills\u002Fdatalad\u002Freferences\u002Fprovenance.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fpublishing.md",11174,"https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fconfig\u002Fopencode\u002Fskills\u002Fdatalad\u002Freferences\u002Fpublishing.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7F6BB3VS43C65P23JR4ZN5G","venue-templates","Prepares journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds. Supports selecting an official template, checking current page or anonymity rules, adapting academic writing to a venue, or inspecting a submission PDF.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fvenue-templates\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7F6B4CBVEHY1RKVW55X8484","scientific-writing","Drafts, revises, and audits scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fscientific-writing\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7F6AXKSP5AXE8B7RCE1KP0C","scientific-visualization","Creates and audits truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly. Use it for figure design, multi-panel layouts, uncertainty and missing-data displays, color\u002Fcontrast review, image metadata validation, and journal export planning.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fscientific-visualization\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7F6AMRHS0QH64CMKE8TP9Y7","scientific-slides","Builds slide decks and presentations for research talks. Used for making PowerPoint slides, conference presentations, seminar talks, research presentations, thesis defense slides, or any scientific talk. Provides slide structure, design templates, timing guidance, and visual validation. Works with PowerPoint and LaTeX Beamer.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fscientific-slides\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7F6ACZ7GQJNNW0682235MC3","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7F6A2JDHTYABYSA4NCE82VG","research-grants","Supports research proposal preparation and review for NSF, NIH, DOE, DARPA, and Taiwan NSTC, including opportunity-specific requirements, aims, review criteria, budgets, broader impacts, forms, and resubmissions. Use for investigator-authored grant development, compliance matrices, and proposal critiques.","https:\u002F\u002Fgithub.com\u002Fbeanspowt\u002Fbeancode\u002Fblob\u002Fmain\u002Fhermes\u002Fprofiles\u002Fworker-writer\u002Fskills\u002Fresearch-grants\u002FSKILL.md",[],[]]