Agent skill · Data & Analytics

nsd-skill

Use this skill whenever the user wants an end-to-end workflow for the Natural Scenes Dataset (NSD), including data access, BIDS validation, multimodal processing of task-fMRI and structural MRI, stimulus metadata extraction, and QC integration. Triggers include: 'NSD', 'Natural Scenes Dataset', 'process NSD data', 'NSD fMRI', 'visual neuroscience', or any request to run the NSD multimodal pipeline.

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

# NSD Skill (Dataset-Orchestration Layer) ## Overview `nsd-skill` is the NeuroClaw orchestration skill for the **Natural Scenes Dataset (NSD)**. It strictly follows the NeuroClaw hierarchical design principles: - This skill **only describes WHAT needs to be done** and **which tool skill to delegate to**. - It contains **no implementation code or concrete commands**. - All concrete execution is delegated to existing base/tool skills via `claw-shell`. - Companion scripts in `scripts/` provide reference implementations for BIDS validation, stimulus extraction, and QC. **Core workflow (never bypassed):** 1. Identify input NSD data and target modalities. 2. Generate a **numbered execution plan** clearly stating WHAT needs to be done and which tool skill will handle each step. 3. Present the full plan, estimated runtime, resource requirements, and risks to the user and wait for explicit confirmation ("YES" / "execute" / "proceed"). 4. On confirmation, delegate every step to the appropriate skill via `claw-shell`. 5. After execution, save all outputs in a clean directory structure (`nsd_output/`). **Research use only.** --- ## Quick Reference | Task | What needs to be done | Delegate to |

What's inside
Steps it walks through
  1. Overview
  2. Quick Reference
  3. Dataset Characteristics
  4. Supported Modalities
  5. NSD Task Paradigms
  6. COCO Stimulus Metadata
  7. BIDS Preparation
  8. Script: scripts/validatensd.py
  9. Core Workflow (Never Bypassed)
  10. Modality Processing Delegation
  11. Standard Output Layout
  12. Benchmark Adapter Guidance
  13. Safety and Execution Policy
  14. Important Notes and Limitations
Commands it runs
python skills/nsd-skill/scripts/validate_nsd.py \
More from awesome-bio-agent-skills
All skills →
About this skill
What does the nsd-skill skill do?

Use this skill whenever the user wants an end-to-end workflow for the Natural Scenes Dataset (NSD), including data access, BIDS validation, multimodal processing of task-fMRI and structural MRI, stimulus metadata extraction, and QC integration. Triggers include: 'NSD', 'Natural Scenes Dataset', 'process NSD data', 'NSD fMRI', 'visual neuroscience', or any request to run the NSD multimodal pipeline.

How do I install it?

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