stanislavjiricek/phase-preregistration
skills/phase-preregistration/SKILL.md
Phase guidance for the neuroflow /preregistration command. Loaded automatically when /preregistration is invoked to orient agent behavior, relevant skills, and workflow hints for creating and managing pre-registration documents.
$ install --global
skillsauthnpx skillsauth add stanislavjiricek/neuroflow phase-preregistrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 11:55 PM2.4s1 file scanned
SKILL.md
- name:
- phase-preregistration
- description:
- Phase guidance for the neuroflow /preregistration command. Loaded automatically when /preregistration is invoked to orient agent behavior, relevant skills, and workflow hints for creating and managing pre-registration documents.
phase-preregistration
The preregistration phase produces and manages pre-registration documents that commit the research team to a specific hypothesis, design, and analysis plan before data collection begins.
Approach
- Identify which mode applies (draft, review, deviation log, link registered report) before starting
- Always pull the research question and hypothesis from
.neuroflow/ideation/if it exists; pull paradigm details from.neuroflow/experiment/if it exists — do not ask the user to repeat information already in project memory - Ask which registry or template applies before drafting; structure adapts significantly between OSF and AsPredicted
- In all pre-registration drafts: hypotheses must be directional and falsifiable, analysis plans fully specified, and exploratory analyses clearly distinguished from confirmatory ones
- If a power calculation is missing, prompt the user to provide one before saving the document
- After data collection begins, use the deviation log mode to record any plan changes — never silently edit a submitted pre-registration document
Relevant skills
neuroflow:neuroflow-core— read first; defines the command lifecycle and.neuroflow/write rules
Workflow hints
prereg-[registry]-[date].md— the primary pre-registration document; version-control this fileprereg-review-[date].md— completeness and consistency review reportdeviations.md— running log of post-registration deviations; append only, never overwrite past entriesregistered-report.md— metadata for any submitted or accepted registered reports (DOI, stage, date)- Pre-registration documents are the scientific record — flag any ambiguity that could allow selective reporting or HARKing (Hypothesizing After Results are Known)
- If the user is drafting for a registered report journal submission, note that stage 1 acceptance is typically contingent on the analysis plan being fully specified
Related Skills
stanislavjiricek/bids
testing
VerifiedTrustedCommunity
This skill should be used whenever the user mentions BIDS, Brain Imaging Data Structure, BIDS conversion, BIDS validation, BIDS compliance, organizing neuroimaging data, dataset_description.json, participants.tsv, bids-validator, pybids, MNE-BIDS, or asks how to structure EEG/MEG/fMRI/iEEG/PET/DWI data for sharing or preprocessing. Also invoke when the user asks how to name scan files, what sidecar JSON fields are needed, how to set up derivatives/, or how to run fMRIPrep/MRIQC on their dataset. Invoke proactively during /data, /data-preprocess, and /data-analyze phases whenever the dataset structure is relevant to the task at hand.
3SKILL.mdUpdated Jun 5, 2026
stanislavjiricek/phase-meeting
tools
VerifiedTrustedCommunity
Phase guidance for the /meeting command. Covers meeting file structure, recurring templates, attendee resolution from profiles, Google Calendar MCP integration, agenda preparation with project context, and action-item-to-task conversion at all three levels (project, flowie, hive).
3SKILL.mdUpdated Apr 25, 2026
stanislavjiricek/worker-critic
data-ai
VerifiedTrustedCommunity
Worker-critic agentic loop protocol — orchestrator coordinates a worker agent and a critic agent across up to 3 revision cycles to produce a vetted output for any phase.
3SKILL.mdUpdated Apr 14, 2026
stanislavjiricek/wiki
development
VerifiedTrustedCommunity
Knowledge base skill — Karpathy-style LLM-maintained wiki at three levels (personal/flowie, project, team/hive). Handles ingest, query, lint, schema, and project-tagging workflows. Invoked by /flowie --wiki-* (personal), /wiki (project), /hive --wiki-* (team).
3SKILL.mdUpdated Apr 14, 2026