psychopy

Plan PsychoPy Builder experiment routines, stimuli, responses, and logging.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/MarvinCui/NeuroForge --skill psychopy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: psychopy
Source: https://github.com/MarvinCui/NeuroForge/tree/main/NeuroForge/skills/psychopy
Command: npx skills add https://github.com/MarvinCui/NeuroForge --skill psychopy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) and scripts (resource) components.

What problem does it solve?

PsychoPy experiment workflows can become error-prone when you need to plan routines, stimuli, event/response logging, and cross-tool handoffs without breaking timing or assumptions.

Core Features & Use Cases

  • Experiment design guidance: Plan PsychoPy Builder concepts such as routines, trial structure, stimuli, responses, triggers, and task logging.
  • Safe workflow planning: Identify what to check before suggesting commands, and clarify what should be treated as planning/inspection rather than heavy execution.
  • Cross-modality handoff support: Help connect behavioral outputs to downstream analysis workflows (e.g., EEG/fMRI) by translating what needs to be logged.

Quick Start

Use the psychopy skill when you have a description of your PsychoPy experiment (Builder files, routines/trials, or expected logging columns) and you want a structured plan for stimulus/response handling and what to verify before running or exporting.

Frequently Asked Questions about psychopy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure PsychoPy Builder routines and trial logging for a behavioral experiment?

To structure PsychoPy Builder experiments, you plan routines, trial sequences, stimuli, and response logging to ensure safe, well-organized behavioral outputs for downstream analysis.

What do I need to log in PsychoPy to prepare data for EEG or fMRI analysis?

Mapping behavioral outputs to EEG or fMRI analysis requires logging precise event triggers, trial structures, and response timestamps in PsychoPy to align with downstream neural data.

How do I plan PsychoPy stimuli and event handling without breaking experiment timing?

Planning PsychoPy stimuli and event handling involves verifying routine structures and safety cautions beforehand, treating workflow setup as documentation and inspection to prevent timing breaks.

Can I use this approach to design experiments for both behavioral responses and cross-modality handoffs?

This experiment design guidance supports both behavioral response handling and cross-modality handoffs by translating task descriptions into structured plans for triggers and logging columns.

What are the limitations of planning PsychoPy experiments as a structured workflow?

The limitation is that this approach focuses on documentation, workflow planning, and safety inspection rather than executing heavy processing or making direct file assumptions during the experiment.