skills/research-literacy/SKILL.md
Core scientific methodology principles: research planning, method justification, assumption checking, and human-in-the-loop decision making for cognitive science and neuroscience
npx skillsauth add haoxuanlithuai/awesome_cognitive_and_neuroscience_skills research-literacyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
AI agents tend to execute analysis steps immediately without planning or justification. In research, every analysis decision needs a rationale grounded in theory, design, and data characteristics. This skill encodes the basic scientific thinking that should precede any domain-specific action.
A competent programmer without research training will typically: (a) pick a familiar method rather than the appropriate one, (b) skip assumption checks, (c) interpret results without considering alternative explanations, and (d) make undisclosed analytic choices that inflate false positive rates. This skill exists to prevent all four failure modes.
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.
A research question must be specific, falsifiable, and operationalized before any data analysis begins.
Adapted from evidence-based medicine, PICOS structures research questions systematically:
| Element | General Definition | Cognitive Science Example | |---|---|---| | Population | Who is studied | Healthy adults aged 18-35; patients with aphasia | | Intervention / Exposure | What manipulation or variable | Semantic priming; TMS to DLPFC | | Comparison | What is the control condition | Unrelated prime; sham stimulation | | Outcome | What is measured | N400 amplitude; reaction time; BOLD signal | | Study design | How is the study structured | Within-subjects; longitudinal; cross-sectional |
This distinction is critical for valid inference (Wagenmakers et al., 2012):
Rule: Always declare whether an analysis is confirmatory or exploratory before executing it. If the analysis plan changed after seeing the data, label it exploratory.
| Research Question Type | Analysis Family | Examples | |---|---|---| | Group differences | Comparison | t-test, ANOVA, Mann-Whitney, permutation test | | Relationships between variables | Association | Correlation, regression, structural equation modeling | | Predicting outcomes | Prediction | Regression, classification, machine learning | | Describing patterns | Description | Descriptive statistics, factor analysis, clustering | | Temporal dynamics | Time-series | Time-frequency, autoregressive models, HMM | | Neural representations | Multivariate | RSA, MVPA, encoding models |
When choosing a method, consider and document the following:
references/common-assumptions.md for method-specific guidance.references/common-assumptions.md."If all you have is a hammer, everything looks like a nail."
This anti-pattern occurs when a researcher applies the method they are most comfortable with, regardless of whether it is appropriate. Examples:
Rule: Always articulate why THIS method and not alternatives. Document the alternatives considered and why they were rejected.
Before running any analysis, declare what each possible outcome means:
Declaring expected outcomes in advance prevents:
No statistical method is assumption-free. Before applying any method, identify its key assumptions and check them. The full reference table is in references/common-assumptions.md.
Every study has limitations. Common categories:
Rule: List limitations upfront, not as an afterthought. This is not a weakness; it is scientific rigor.
Research involves judgment calls where reasonable experts disagree. These "researcher degrees of freedom" (Simmons et al., 2011) can inflate false positive rates from a nominal 5% to as high as 60% when left unchecked (Simmons et al., 2011). AI agents must not make these decisions silently.
ALWAYS present the analysis plan and WAIT for user confirmation before proceeding at these decision points:
These are well-documented threats to research integrity. An AI agent must actively avoid them and flag when a user's request risks falling into one.
Running multiple analyses, selectively reporting significant results, or tweaking analysis parameters until p < .05. Simulations show this can inflate false positive rates from 5% to over 60% (Simmons et al., 2011, Psychological Science, 22(11), 1359-1366).
How to avoid: Preregister analyses. Report all analyses conducted. Use correction for multiple comparisons.
Presenting post-hoc hypotheses as if they were a priori predictions (Kerr, 1998, Personality and Social Psychology Review, 2(3), 196-217).
How to avoid: Write down hypotheses before analysis. Clearly label any post-hoc exploration.
Selectively reporting evidence that supports preferred conclusions while downplaying contradictory evidence.
How to avoid: Report effect sizes and confidence intervals for all outcomes, not just significant ones. Use adversarial collaboration or preregistered analysis plans.
Even without deliberate p-hacking, undisclosed analytic flexibility creates a "garden of forking paths" where many analysis pipelines could have been chosen, inflating the effective number of comparisons (Gelman & Loken, 2014, American Scientist, 102(6), 460-465).
How to avoid: Document every analytic decision and its alternatives. Consider multiverse analysis (Steegen et al., 2016).
Applying statistical procedures as rituals without understanding the underlying assumptions or logic. The "null ritual" — mechanically testing H0 at alpha = .05 without specifying H1, considering effect sizes, or evaluating power — is the canonical example (Gigerenzer, 2004, Journal of Socio-Economics, 33, 587-606).
How to avoid: For every test, articulate: What is H0? What is H1? What is the expected effect size? What is the power? Is the test appropriate for this data structure?
Changing the primary outcome variable after seeing the data because the original outcome was not significant.
How to avoid: Preregister primary and secondary outcomes. Report results for the preregistered primary outcome regardless of significance.
This is the core procedure. Execute these steps before any analysis.
Write the question in one sentence. It must be specific, testable, and falsifiable. Use the PICOS framework above.
If confirmatory, a preregistered hypothesis must exist. If exploratory, label all results as hypothesis-generating.
Name the method, explain why it is appropriate for this question and data, and list alternatives that were considered and why they were rejected.
For each hypothesis, state what supporting, refuting, and ambiguous results would look like, with expected effect sizes where possible.
Enumerate the method's statistical assumptions and how they will be checked. List known limitations of the design and analysis.
Show the complete plan in a structured format (see references/planning-template.md). Include decision points where user input is required.
Do not proceed until the user approves the plan or requests modifications.
After analysis, explicitly compare results to the expected outcomes declared in Step 4. Discuss discrepancies honestly.
Reiterate limitations, including any that became apparent during analysis (e.g., assumption violations, unexpected data patterns).
tools
Convert a GitHub repository or local codebase into a well-structured Claude Code skill with progressive disclosure. Use this skill whenever the user provides a GitHub URL or local repo path and asks to turn it into a skill, create a skill from a repo, or convert a library/tool/framework into reusable skill documentation. Also trigger when users say things like 'make a skill from this repo', 'turn this codebase into a skill', or 'I want a skill for [library name]'.
development
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 viewers, volume-to-surface mapping, FreeSurfer/fMRIPrep integration, ROI management, and surface analysis. Use this skill whenever the user mentions pycortex, `import cortex`, cortical surfaces, brain flatmaps, WebGL brain viewers, cortical surface mapping, or wants to visualize neuroimaging data on the cortex, even if they don't explicitly name pycortex.
development
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 decomposition, source localization, decoding/MVPA, statistical testing, simulation, and visualization. Use this skill whenever the user works with EEG/MEG/sEEG/ECoG/NIRS/eye-tracking data in Python, mentions MNE, or needs neurophysiological analysis guidance.
development
Step-by-step guidance for contributing a new skill to the NeuroAIHub/awesome_cognitive_and_neuroscience_skills repository via GitHub Pull Request, including SKILL.md format requirements, quality rules, and PR checklist