Agent skill

Fmri Task Design Guide

by NeuroAIHub in NeuroAIHub/BrainPilot

Guides fMRI task design: block vs. An agent skill from NeuroAIHub/BrainPilot.

AGPL-3.0Auto-check passed

Install Fmri Task Design Guide

skills CLI
$ npx skills add NeuroAIHub/BrainPilot --skill fmri-task-design-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeuroAIHub/BrainPilot fmri-task-design-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeuroAIHub/BrainPilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide .claude/skills/fmri-task-design-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fmri-task-design-guide
GitHub stars
1.1k
Token cost
~4.2k tokens
SKILL.md length
2,017 words
Files
2 (incl. references)
Skills in repo
59
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Guides fMRI task design: block vs. An agent skill from NeuroAIHub/BrainPilot.

  • Works in 5 steps: State the research question — What… → Justify the method choice — Why is this… → Declare expected outcomes — What results… → …
  • SKILL.md covers Purpose, When to Use This Skill, Research Planning Protocol and ⚠️ Verification Notice, plus 12 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fmri Task Design Guide is an agent skill from NeuroAIHub/BrainPilot. Guides fMRI task design: block vs. event-related vs. mixed; jittering; contrasts; power for BOLD detection

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/design-optimization-examples.md`).

The repository describes itself as: BrainPilot: Automating Brain Discovery with Agentic Research. The licence is AGPL-3.0.

Example prompts

  • “Use the fmri-task-design-guide skill to guide fMRI task design: block vs. An agent skill from NeuroAIHub/BrainPilot”
  • “/fmri-task-design-guide”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. State the research question — What specific question is this analysis/paradigm addressing?
  2. Justify the method choice — Why is this approach appropriate? What alternatives were considered?
  3. Declare expected outcomes — What results would support vs. refute the hypothesis?
  4. Note assumptions and limitations — What does this method assume? Where could it mislead?
  5. Present the plan to the user and WAIT for confirmation before proceeding.

What it can do on your machine

Read from SKILL.md and the folder at commit 93f6855. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fmri Task Design Guide loads about 4.2k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 2,017 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeuroAIHub/BrainPilot at commit 93f6855, republished under its AGPL-3.0 licence (© NeuroAIHub). 2,017 words, ~4,202 tokens.

Download SKILL.mdSave it as .claude/skills/fmri-task-design-guide/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
fmri-task-design-guide
description
Guides fMRI task design: block vs. event-related vs. mixed; jittering; contrasts; power for BOLD detection
domain
cognitive-neuroscience
version
1.0.0
authors
awesome_cognitive_and_neuroscience_skills contributors
papers
Friston et al., 1999, Petersen & Dubis, 2012, Dale, 1999, Bandettini et al., 1993, Glover, 1999, Desmond & Glover, 2002, Wager & Nichols, 2003
dependencies.required
research-literacy
dependencies.recommended
fmri-glm-analysis-guide, fmri-preprocessing-pipeline-guide
review_status
ai-generated

fMRI Task Design Guide

Purpose

The experimental design is the single most important determinant of an fMRI study's statistical power, interpretability, and scientific value. Choosing between block, event-related, and mixed designs involves trade-offs between detection power and estimation efficiency that depend on the research question. Similarly, the choice of inter-stimulus interval (ISI), jittering strategy, condition ordering, and trial count directly determines whether the BOLD signal of interest can be reliably detected.

A competent programmer without neuroimaging training would not know that block designs provide higher detection power but cannot estimate HRF shape, that exponentially distributed jitter is more efficient than uniform jitter, or that the BOLD response takes 12-16 seconds to return to baseline. This skill encodes those domain-specific design decisions.

When to Use This Skill

  • Planning a new task-based fMRI experiment
  • Choosing between block, event-related, or mixed designs
  • Optimizing inter-stimulus interval and jittering strategy
  • Calculating design efficiency for contrast detection
  • Determining minimum trial counts per condition
  • Integrating behavioral task constraints with fMRI timing requirements
  • Reviewing or troubleshooting an existing fMRI task design

Research Planning Protocol

Before executing the domain-specific steps below, you MUST:

  1. State the research question — What specific question is this analysis/paradigm addressing?
  2. Justify the method choice — Why is this approach appropriate? What alternatives were considered?
  3. Declare expected outcomes — What results would support vs. refute the hypothesis?
  4. Note assumptions and limitations — What does this method assume? Where could it mislead?
  5. Present the plan to the user and WAIT for confirmation before proceeding.

For detailed methodology guidance, see the research-literacy skill.

⚠️ Verification Notice

This skill was generated by AI from academic literature. All parameters, thresholds, and citations require independent verification before use in research. If you find errors, please open an issue.

Design Type Selection

Comparison of Design Types
Design TypeDetection PowerEstimation EfficiencyTrial-Level AnalysisBest ForSource
BlockHighLowNoDetecting whether a region is activeFriston et al., 1999; Petersen & Dubis, 2012
Event-related (slow)ModerateHighYesEstimating HRF shapeDale, 1999
Rapid event-relatedModerate-HighModerate-HighYesFlexible trial-by-trial analysis with good powerDale, 1999; Friston et al., 1999
Mixed (hybrid)High (sustained) + Moderate (transient)ModerateYes (transient component)Separating sustained and transient effectsPetersen & Dubis, 2012
Decision Tree
What is the primary goal?
 |
 +-- Detect presence/absence of activation (localization)
 | |
 | +-- Is HRF shape estimation needed?
 | |
 | +-- NO --> Block design (maximum detection power)
 | |
 | +-- YES --> Mixed design (blocks + events within blocks)
 |
 +-- Estimate trial-by-trial neural responses
 | |
 | +-- Are there enough trials (>40 per condition)?
 | |
 | +-- YES --> Rapid event-related design (jittered ISI)
 | |
 | +-- NO --> Slow event-related design (ISI > 12 s)
 |
 +-- Separate sustained state vs. transient item effects
 --> Mixed design (Petersen & Dubis, 2012)

Block Design Parameters

  • Optimal block duration: 15-20 seconds for maximum detection power (Maus et al., 2010; Bandettini et al., 1993). Shorter blocks (< 12 s) reduce sensitivity because the BOLD response does not reach steady state. Longer blocks (> 30 s) increase habituation and strategy effects (Poldrack et al., 2011, Ch. 3)
  • Minimum block duration: 12 seconds to allow the BOLD signal to reach near-plateau (Bandettini et al., 1993)
  • Number of blocks per condition: At least 4-6 blocks per condition per run for stable estimates (Poldrack et al., 2011, Ch. 3)
  • Condition alternation: Alternate conditions (ABAB or ABCABC) rather than grouping (AAABBB), which confounds condition with time (Poldrack et al., 2011, Ch. 3)
  • Rest blocks: Include rest/fixation blocks of at least 12-16 seconds between active blocks to allow BOLD signal return to baseline (Glover, 1999)
Inter-Stimulus Interval (ISI) and Jittering

The ISI between events is critical for statistical efficiency and BOLD signal separability.

ParameterRecommendationSource
Minimum ISI2-4 seconds (for partial BOLD recovery)Dale, 1999; Glover, 1999
Mean ISI for rapid designs4-6 secondsDale, 1999
ISI range for jittered designs2-8 secondsDale, 1999; Wager & Nichols, 2003
Null/fixation trials20-33% of total eventsFriston et al., 1999

Jittering strategies (from most to least recommended):

  1. Optimized sequences: Use design optimization tools (optseq2, NeuroDesign) to maximize efficiency for specific contrasts (Dale, 1999; Durnez et al., 2017)
  2. Truncated exponential distribution: More short ISIs, fewer long ISIs; near-optimal efficiency (Hagberg et al., 2001)
  3. Uniform random: Equal probability across ISI range; acceptable but suboptimal
  4. Fixed ISI: Avoid for rapid event-related designs; severely reduces design efficiency

Domain warning: Jittered designs can be over 10x more efficient than fixed-ISI designs with the same mean interval (Dale, 1999). Always jitter for event-related fMRI.

HRF Timing Constraints

The BOLD hemodynamic response imposes hard constraints on fMRI design timing:

  • HRF peak: 4-6 seconds after neural event onset (Glover, 1999)
  • Return to baseline: 12-16 seconds after a brief event (Glover, 1999)
  • BOLD nonlinearity: Responses to stimuli separated by < 2 seconds sum nonlinearly (reduced amplitude), making them harder to separate (Glover, 1999; Wager & Nichols, 2003)
Trial Count Requirements
Design TypeMinimum Trials per ConditionRecommended TrialsSource
Event-related (detection)2030-50Desmond & Glover, 2002
Event-related (HRF estimation)3050+Murphy & Garavan, 2005
Rapid event-related3040-60Desmond & Glover, 2002
FIR/deconvolution40+60+Glover, 1999

Domain insight: These are per-condition minimums. If comparing conditions (A vs. B), each condition needs this many trials. More conditions require longer scan sessions or fewer trials per condition, creating a power trade-off.

Design Efficiency

Efficiency Calculation

Design efficiency quantifies how well a given design matrix allows detection of specific contrasts:

Detection efficiency = 1 / trace(c' * inv(X'X) * c)

where c is the contrast vector and X is the design matrix (Dale, 1999; Liu et al., 2001).

Detection vs. Estimation Trade-off
  • Detection power: Ability to detect whether an effect exists. Maximized by block designs and rapid event-related designs with high event density (Liu et al., 2001)
  • Estimation efficiency: Ability to accurately characterize the HRF shape. Maximized by jittered designs with sufficient ISI variability (Liu et al., 2001)
  • These are inherently in tension: block designs maximize detection but cannot estimate HRF shape
Design Optimization Tools
  • optseq2 (FreeSurfer): Optimizes event ordering and null events for maximum efficiency (Dale, 1999)
  • NeuroDesign (Python): Genetic algorithm-based optimization (Durnez et al., 2017)
  • fMRIpower: Power calculations accounting for design and temporal autocorrelation (Mumford & Nichols, 2008)

Mixed Design Specification

Mixed designs combine sustained (block-level) and transient (event-level) components (Petersen & Dubis, 2012):

  1. Sustained regressor: Models the tonic task state (e.g., "task block on" vs. "rest"), boxcar convolved with HRF
  2. Transient regressors: Model individual trial onsets within each block, convolved with HRF
  3. These regressors are separable because they operate at different temporal frequencies

Key parameters:

  • Block duration: 20-40 seconds to provide enough events within each block (Petersen & Dubis, 2012)
  • Events per block: At least 4-6 for stable transient estimates
  • Inter-block rest: 16-20 seconds minimum for BOLD signal recovery (Glover, 1999)
ConstraintGuidelineRationale
TR synchronizationStimulus onsets need not align with TR boundaries for event-related designsJittered onsets relative to TR improve temporal sampling of HRF
Trigger pulsesStart experiment on scanner trigger pulse (TTL signal)Ensures precise alignment between stimulus and acquisition timing
Total scan duration5-15 minutes per runLonger runs increase motion and fatigue; shorter runs waste setup time (Poldrack et al., 2011, Ch. 3)
Number of runs2-4 runs typical; split conditions across runs if neededAllows rest between runs; run-level effects can be modeled
Dummy scansFirst 3-5 TRs (5-10 s) are T1 equilibration artifactsDiscard or model as confounds (Poldrack et al., 2011, Ch. 5)

Rest/Fixation Baseline

  • Allocate 25-30% of total scan time to rest/fixation baseline (Friston et al., 1999)
  • Rest periods serve dual purpose: allow BOLD signal recovery and provide baseline estimate
  • For block designs, rest blocks of 12-16 seconds between active blocks (Glover, 1999)
  • For event-related designs, null trials (fixation) distributed throughout the sequence (Friston et al., 1999)
Show full SKILL.md (824 more words)Show less

Condition Ordering

  • m-sequences: Pseudo-random sequences with optimal counterbalancing properties (Buracas & Boynton, 2002)
  • Optimized pseudo-random: Generated by optimization algorithms (optseq2, NeuroDesign) to maximize design efficiency while controlling trial-order effects (Dale, 1999)
  • Avoid: Simple alternation (ABABAB) which confounds condition with time, or purely random sequences which may produce long runs of the same condition

Behavioral Task Constraints

ConstraintGuidelineSource
Response mappingCounterbalance button assignments across subjectsPrevents lateralized motor confound
Practice effectsInclude out-of-scanner practice until performance plateausReduces learning-related activation changes during scanning
Task difficultyAim for 70-85% accuracyFloor/ceiling effects eliminate behavioral variance (Poldrack et al., 2011, Ch. 3)
Response windowAllow 1.5-3 seconds for speeded responsesAccommodate scanner environment slowing (~200 ms; Haatveit et al., 2010)
Stimulus duration0.5-4 seconds typical for visual stimuliLong enough for perceptual processing, short enough for event separation

Common Pitfalls

  1. Fixed ISI in event-related designs: Dramatically reduces design efficiency compared to jittered designs. Always jitter ISI for event-related fMRI (Dale, 1999)
  2. Too few trials per condition: Fewer than 20 events per condition yields unreliable single-subject estimates (Desmond & Glover, 2002). Plan for at least 30 per condition
  3. Ignoring HRF recovery time: Events separated by < 2 seconds produce nonlinear BOLD summation, making responses difficult to separate (Glover, 1999)
  4. No baseline/rest periods: Without rest periods, the model cannot estimate absolute activation levels and efficiency drops substantially (Friston et al., 1999)
  5. Confounding condition with time: Presenting all trials of one condition before another confounds the effect with scanner drift and fatigue
  6. Not counterbalancing response mappings: Lateralized motor responses (left vs. right hand) produce motor cortex activation that confounds task effects
  7. Ceiling/floor performance: If accuracy is near 100% or chance, there is no behavioral variance to correlate with brain activity
  8. Not optimizing the design matrix: Using arbitrary event timing instead of optimized sequences wastes statistical power that could be gained at no additional cost

Minimum Reporting Checklist

Based on COBIDAS guidelines (Nichols et al., 2017) and Poldrack et al. (2008):

  • Design type (block, event-related, mixed, rapid event-related)
  • Block duration (for block designs) or ISI distribution parameters (for event-related)
  • Number of conditions and number of trials per condition
  • Stimulus duration and response window
  • Jittering strategy and ISI range (min, max, mean, distribution)
  • Null trial proportion and distribution
  • Condition ordering method (optimized, m-sequence, pseudo-random)
  • Total scan duration per run and number of runs
  • Design optimization tool used (if any) and efficiency metric
  • Response mapping and counterbalancing scheme
  • Practice procedure (in-scanner or out-of-scanner, duration)
  • TR and its relationship to stimulus timing

References

  • Bandettini, P. A., Jesmanowicz, A., Wong, E. C., & Hyde, J. S. (1993). Processing strategies for time-course data sets in functional MRI of the human brain. Magnetic Resonance in Medicine, 30(2), 161-173.
  • Buracas, G. T., & Boynton, G. M. (2002). Efficient design of event-related fMRI experiments using m-sequences. NeuroImage, 16(3), 801-813.
  • Dale, A. M. (1999). Optimal experimental design for event-related fMRI. Human Brain Mapping, 8(2-3), 109-114.
  • Desmond, J. E., & Glover, G. H. (2002). Estimating sample size in functional MRI (fMRI) neuroimaging studies: Statistical power analyses. Journal of Neuroscience Methods, 118(2), 115-128.
  • Durnez, J., Blair, R., & Poldrack, R. A. (2017). NeuroDesign: Optimal experimental designs for task fMRI. bioRxiv, 119594.
  • Friston, K. J., Zarahn, E., Josephs, O., Henson, R. N. A., & Dale, A. M. (1999). Stochastic designs in event-related fMRI. NeuroImage, 10(5), 607-619.
  • Glover, G. H. (1999). Deconvolution of impulse response in event-related BOLD fMRI. NeuroImage, 9(4), 416-429.
  • Haatveit, B. C., Sundet, K., Hugdahl, K., et al. (2010). The validity of d prime as a working memory index. Neuropsychology, 24(5), 629-640.
  • Hagberg, G. E., Zito, G., Patria, F., & Sanes, J. N. (2001). Improved detection of event-related functional MRI signals using probability functions. NeuroImage, 14(5), 1193-1205.
  • Liu, T. T., Frank, L. R., Wong, E. C., & Buxton, R. B. (2001). Detection power, estimation efficiency, and predictability in event-related fMRI. NeuroImage, 13(4), 759-773.
  • Maus, B., van Breukelen, G. J. P., Goebel, R., & Berger, M. P. F. (2010). Optimal design of multi-subject blocked fMRI experiments. NeuroImage, 51(3), 1338-1348.
  • Mumford, J. A., & Nichols, T. E. (2008). Power calculation for group fMRI studies accounting for arbitrary design and temporal autocorrelation. NeuroImage, 39(1), 261-268.
  • Murphy, K., & Garavan, H. (2005). Deriving the optimal number of events for an event-related fMRI study based on the spatial extent of activation. NeuroImage, 27(4), 771-777.
  • Nichols, T. E., Das, S., Eickhoff, S. B., et al. (2017). Best practices in data analysis and sharing in neuroimaging using MRI (COBIDAS). Nature Neuroscience, 20(3), 299-303.
  • Petersen, S. E., & Dubis, J. W. (2012). The mixed block/event-related design. NeuroImage, 62(2), 1177-1184.
  • Poldrack, R. A., Fletcher, P. C., Henson, R. N., et al. (2008). Guidelines for reporting an fMRI study. NeuroImage, 40(2), 409-414.
  • Poldrack, R. A., Mumford, J. A., & Nichols, T. E. (2011). Handbook of Functional MRI Data Analysis. Cambridge University Press.
  • Wager, T. D., & Nichols, T. E. (2003). Optimization of experimental design in fMRI: A general framework using a genetic algorithm. NeuroImage, 18(2), 293-309.

See references/ for detailed design optimization examples and parameter lookup tables.

© NeuroAIHub, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide of NeuroAIHub/BrainPilot.

  • SKILL.md
  • references/design-optimization-examples.md

Open the folder on GitHubat commit 93f6855

Compare with similar skills

Fmri Task Design Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fmri Task Design Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fmri Task Design Guide this skillNeuroAIHub/BrainPilot1.1k—~4.2kAutomated safety check: PassAGPL-3.0
Eventscoreyhaines31/marketingskills54k—~3kAutomated safety check: PassMIT
Block Kitopenclaw/openclaw392k—~624Automated safety check: PassMIT
Event Delegationthedaviddias/Front-End-Checklist74k—~500Automated safety check: PassMIT
Render Blockingthedaviddias/Front-End-Checklist74k—~430Automated safety check: PassMIT
Blocking IO Guardbytedance/deer-flow84k—~1.7kAutomated safety check: PassMIT

Similar skills

  • Events

    coreyhaines31/marketingskills

    When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences.

    54k GitHub stars~3k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • Block Kit

    openclaw/openclaw

    Use proactively for structured or interactive Slack replies, and when asked to author or validate native Slack Block Kit JSON.

    392k GitHub stars~624 tokensUpdated today
    Auto-check passed
  • Event Delegation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Use event delegation for dynamic content.

    74k GitHub stars~500 tokensUpdated 4 days ago
    Auto-check passed
  • Render Blocking

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources.

    74k GitHub stars~430 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed
  • Blocking IO Guard

    bytedance/deer-flow

    Adds a runtime test anchor for backend async code that could block the asyncio event loop, and proves the anchor fails when the blocking call returns.

    84k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Color Blocking

    sickn33/agentic-awesome-skills

    Web and App implementation guide for Color Blocking. An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed

More from NeuroAIHub/BrainPilot

All 59 skills in this repo
  • Deeplabcut

    NeuroAIHub/BrainPilot

    Toolbox for markerless animal pose estimation with DeepLabCut.

    1.1k GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check passed
  • Fmriprep

    NeuroAIHub/BrainPilot

    Preprocess task-based or resting-state fMRI data with fMRIPrep — a robust, BIDS-App preprocessing pipeline built on FSL, ANTs, FreeSurfer, AFNI, and Nilearn.

    1.1k GitHub stars~4.1k tokensUpdated 8 days ago
    Auto-check passed
  • Mne Python Guide

    NeuroAIHub/BrainPilot

    Domain-validated pipeline guidance for EEG/MEG data analysis using MNE-Python: data loading, preprocessing (filtering, ICA, re-referencing), epoching, ERP/ERF computation, time-frequency…

    1.1k GitHub stars~2.3k tokensUpdated 8 days ago
    Auto-check passed
  • Netneurotools Guide

    NeuroAIHub/BrainPilot

    Domain-validated guidance for network neuroscience analysis using netneurotools: datasets, brain network metrics, connectivity consensus, modularity, spatial statistics, null models, and cortical…

    1.1k GitHub stars~2.6k tokensUpdated 8 days ago
    Auto-check passed
  • Nature Figure

    NeuroAIHub/BrainPilot

    Submission-grade Nature/high-impact journal figure workflow for Python or R.

    1.1k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Pycortex Guide

    NeuroAIHub/BrainPilot

    Domain-validated guidance for cortical surface visualization and brain surface rendering of fMRI data using pycortex: data types (Volume, Vertex, Dataset), 2D cortical flatmaps, 3D WebGL brain…

    1.1k GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed

Questions about Fmri Task Design Guide

What does Fmri Task Design Guide do?

Guides fMRI task design: block vs. An agent skill from NeuroAIHub/BrainPilot. Fmri Task Design Guide is an agent skill from NeuroAIHub/BrainPilot. Guides fMRI task design: block vs.

How do I install Fmri Task Design Guide in Claude Code?

Run `npx skills add NeuroAIHub/BrainPilot --skill fmri-task-design-guide -a claude-code`. Or copy the skill folder (packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide in NeuroAIHub/BrainPilot) into .claude/skills/fmri-task-design-guide in your project. Claude Code loads it when a task matches its description.

How do I install Fmri Task Design Guide in Codex?

Run `npx skills add NeuroAIHub/BrainPilot --skill fmri-task-design-guide -a codex`. Or copy the skill folder (packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide in NeuroAIHub/BrainPilot) into .agents/skills/fmri-task-design-guide in your project. Codex loads it when a task matches its description.

Can I use Fmri Task Design Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeuroAIHub/BrainPilot --skill fmri-task-design-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fmri-task-design-guide, .gemini/skills/fmri-task-design-guide, .github/skills/fmri-task-design-guide and .opencode/skills/fmri-task-design-guide in your project.

What does Fmri Task Design Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Fmri Task Design Guide is instructions for the agent only.

Does Fmri Task Design Guide access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Fmri Task Design Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fmri Task Design Guide use?

Fmri Task Design Guide is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fmri Task Design Guide use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.5k tokens, read only when the agent opens those files.

What are the alternatives to Fmri Task Design Guide?

Skills that share tags, products or a category with Fmri Task Design Guide: Events (coreyhaines31/marketingskills, 54k stars), Block Kit (openclaw/openclaw, 392k stars), Event Delegation (thedaviddias/Front-End-Checklist, 74k stars) and Render Blocking (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fmri Task Design Guide?

NeuroAIHub (a GitHub organization) maintains it in NeuroAIHub/BrainPilot, which has 1,062 GitHub stars. The repository holds 59 skills in this directory. The repository was last updated on October 2, 2026.

Source: NeuroAIHub/BrainPilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.