Best for
- Planning a new task-based fMRI experiment
- Choosing between block, event-related, or mixed designs
- Optimizing inter-stimulus interval and jittering strategy
NeuroAIHub/BrainPilot/packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide/SKILL.md
Guides fMRI task design: block vs. event-related vs. mixed; jittering; contrasts; power for BOLD detection
Decision brief
Guides fMRI task design: block vs. event-related vs.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/NeuroAIHub/BrainPilot --skill "packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide"Inspect the Agent Skill "fmri-task-design-guide" from https://github.com/NeuroAIHub/BrainPilot/blob/e9ddc112cab9b1c6272dae0c8a6bdceb5c9c3880/packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide/SKILL.md at commit e9ddc112cab9b1c6272dae0c8a6bdceb5c9c3880. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
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.
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 depe…
Planning a new task-based fMRI experiment
Before executing the domain-specific steps below, you MUST:
Review the “Design Type Selection” section in the pinned source before continuing.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 99/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 424 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.
Before executing the domain-specific steps below, you MUST:
For detailed methodology guidance, see the research-literacy skill.
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 | Detection Power | Estimation Efficiency | Trial-Level Analysis | Best For | Source |
|---|---|---|---|---|---|
| Block | High | Low | No | Detecting whether a region is active | Friston et al., 1999; Petersen & Dubis, 2012 |
| Event-related (slow) | Moderate | High | Yes | Estimating HRF shape | Dale, 1999 |
| Rapid event-related | Moderate-High | Moderate-High | Yes | Flexible trial-by-trial analysis with good power | Dale, 1999; Friston et al., 1999 |
| Mixed (hybrid) | High (sustained) + Moderate (transient) | Moderate | Yes (transient component) | Separating sustained and transient effects | Petersen & Dubis, 2012 |
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)
The ISI between events is critical for statistical efficiency and BOLD signal separability.
| Parameter | Recommendation | Source |
|---|---|---|
| Minimum ISI | 2-4 seconds (for partial BOLD recovery) | Dale, 1999; Glover, 1999 |
| Mean ISI for rapid designs | 4-6 seconds | Dale, 1999 |
| ISI range for jittered designs | 2-8 seconds | Dale, 1999; Wager & Nichols, 2003 |
| Null/fixation trials | 20-33% of total events | Friston et al., 1999 |
Jittering strategies (from most to least recommended):
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.
The BOLD hemodynamic response imposes hard constraints on fMRI design timing:
| Design Type | Minimum Trials per Condition | Recommended Trials | Source |
|---|---|---|---|
| Event-related (detection) | 20 | 30-50 | Desmond & Glover, 2002 |
| Event-related (HRF estimation) | 30 | 50+ | Murphy & Garavan, 2005 |
| Rapid event-related | 30 | 40-60 | Desmond & Glover, 2002 |
| FIR/deconvolution | 40+ | 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 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).
Mixed designs combine sustained (block-level) and transient (event-level) components (Petersen & Dubis, 2012):
Key parameters:
| Constraint | Guideline | Rationale |
|---|---|---|
| TR synchronization | Stimulus onsets need not align with TR boundaries for event-related designs | Jittered onsets relative to TR improve temporal sampling of HRF |
| Trigger pulses | Start experiment on scanner trigger pulse (TTL signal) | Ensures precise alignment between stimulus and acquisition timing |
| Total scan duration | 5-15 minutes per run | Longer runs increase motion and fatigue; shorter runs waste setup time (Poldrack et al., 2011, Ch. 3) |
| Number of runs | 2-4 runs typical; split conditions across runs if needed | Allows rest between runs; run-level effects can be modeled |
| Dummy scans | First 3-5 TRs (5-10 s) are T1 equilibration artifacts | Discard or model as confounds (Poldrack et al., 2011, Ch. 5) |
| Constraint | Guideline | Source |
|---|---|---|
| Response mapping | Counterbalance button assignments across subjects | Prevents lateralized motor confound |
| Practice effects | Include out-of-scanner practice until performance plateaus | Reduces learning-related activation changes during scanning |
| Task difficulty | Aim for 70-85% accuracy | Floor/ceiling effects eliminate behavioral variance (Poldrack et al., 2011, Ch. 3) |
| Response window | Allow 1.5-3 seconds for speeded responses | Accommodate scanner environment slowing (~200 ms; Haatveit et al., 2010) |
| Stimulus duration | 0.5-4 seconds typical for visual stimuli | Long enough for perceptual processing, short enough for event separation |
Based on COBIDAS guidelines (Nichols et al., 2017) and Poldrack et al. (2008):
See references/ for detailed design optimization examples and parameter lookup tables.
Frequently asked questions
Guides fMRI task design: block vs. event-related vs.
The source record exposes this install command: npx skills add https://github.com/NeuroAIHub/BrainPilot --skill "packages/skills/skills/06_fMRI_Neuroimaging/fmri-task-design-guide". Inspect the command and pinned source before running it.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
narrative-io/narrative-skills-marketplace
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "