By Haoyu-Hu
Auto-PsyNet — automate the lifecycle of online behavioral experiments on PsyNet: idea → verified plan → experiment code → LLM-pilot + human deployment → analysis → paper. Run /apsy:setup.
Run the current experiment for debugging — launches `bin/apsy-debug.sh` in the background, monitors the boot log, and reports when the server is up. Targets: local | ec2 | stop.
Configure Amazon Mechanical Turk recruitment params for the current experiment.
Export data and run the preregistered analysis; report effects, then iterate or ship (gates G5/G6/G7).
Generate the PsyNet experiment from a G1-verified plan — scaffold, implement, wire timeline, bot-test to G2.
Configure the consent form (default PsyNet MainConsent) — separate file? class/function to import? how to use it?
Adversarial reviewer (red team) for research plans and findings — surfaces confounds, validity threats, statistical issues, alternative explanations, generalizability concerns, and methodological pitfalls. Optional independent pass at G1 (plan) and G6 (findings). Adversarial but fair; never invents flaws.
Code reviewer for generated PsyNet experiments and analysis scripts — enforces the 8 PsyNet gotchas, Python correctness, secret/PII hygiene, and analysis-script-matches-preregistration. Severity-tiered findings (🛑 critical / ⚠️ major / 🔵 minor). Optional pass after implement-paradigm/wire-timeline (BUILD) and before running an analysis script (ANALYZE).
Data analyst for online behavioral experiments — live data-quality monitoring during recruitment and analysis support (completion, exclusions, attention checks, bot/bad-actor detection, wrangling, visualization). Use during recruitment (Track B) and ANALYZE.
Failure-driven debugger for Auto-PsyNet runs — diagnoses errors, test failures, and unexpected behavior, applies the MINIMAL fix, and verifies. Invoked when `psynet test local` (G2) fails, the LLM pilot crashes, the analysis script errors, or any engine step exits non-zero. Never claims a fix without re-running and observing green.
Literature scholar for behavioral-science research — finds and synthesizes prior paradigms, expected effect sizes, the novelty gap, and methodological pitfalls in prior work. Cites only real sources. Use during FORMULATE (apsy:literature-ground) and PUBLISH (Introduction / Discussion sourcing).
Add a new PsyNet recipe file under skills/psynet/psynet-function/ (a new paradigm or cross-cutting capability) and auto-update the parent index in skills/psynet/SKILL.md. Use when extending the PsyNet knowledge pack with something not yet covered — e.g. a new TrialMaker subclass, a new prescreen, a new asset workflow, or a domain-specific recipe.
FORMULATE step — lock the preregistered analysis plan (statistical model, primary/secondary outcomes, decision rules) BEFORE data. This is the holdout that defends against p-hacking.
Smart router — single natural-language entry point that picks the right /apsy:* command. Use when the user types /apsy:auto, says 'just do X', or has a request that doesn't obviously map to one specific /apsy:* command. Routing is deterministic + transparent — no LLM-scored guesswork.
ANALYZE gate G5 — screen the data for quality: completion, attention/manipulation checks, the preregistered exclusions, duplicates/bots, and target-N. Produces the clean analysis dataset.
FORMULATE step — choose the experimental paradigm and design. Maps the question archetype to a PsyNet paradigm via config/affinity.yaml, reads the recipe + domain priors, may propose elevating to a differentiating paradigm, and specifies conditions, counterbalancing, prescreens, population/languages, and consent.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
apsy)A Claude Code plugin that automates the lifecycle of online behavioral experiments built on PsyNet: from a raw research idea → preregistered plan → working PsyNet code → LLM-piloted (and human) deployment → analysis → publication-ready paper. Subjects can be humans, LLM agents, or both.
Also available as a Cursor Marketplace plugin → auto-psynet-cursor. Same logic, gates, ethics policy, and
bin/engines; install with/add-plugin apsyin Cursor 2.5+.
Inside a Claude Code session (requires Claude Code with plugin support):
# Add the marketplace from GitHub, then install the plugin:
/plugin marketplace add Haoyu-Hu/auto-psynet
/plugin install apsy@auto-psynet
# Then:
/apsy:setup # one-time config (interpreter, project-dir, LLM backend, AWS, ...)
/apsy:install # install psynet + dallinger (offers a managed venv)
/apsy:doctor # verify the runtime
Developing locally? Point the marketplace at your checkout instead of GitHub — the plugin
source is a repo-root relative path, so it resolves against whichever copy you added:
/plugin marketplace add /path/to/auto-psynet # your local clone
/plugin install apsy@auto-psynet
If
/plugin installreports "This plugin uses a source type your Claude Code version does not support," update Claude Code to a recent version (claude update) and re-run/plugin marketplace update auto-psynetbefore installing.
/apsy:idea "<your research question>" # → preregistered plan (gate G1)
/apsy:build # → working PsyNet code (gate G2)
/apsy:services start # Redis + Postgres for local debug
/apsy:debug # launch psynet debug local
/apsy:export # export data while it runs
/apsy:debug stop # clean shutdown
/apsy:services stop
/apsy:pilot # LLM-agent participants (gate G3)
/apsy:analyze # preregistered analysis (gates G5/G6/G7)
/apsy:paper # paper draft + OSF reproducibility package
For real human deployment, /apsy:deploy triggers gate G4 — explicit human approval + IRB
attestation + a spend cap required at every autonomy level (see
config/ethics-policy.md).
New here? The G1–G7 references above are the plugin's seven quality gates (preregistration
discipline, no p-hacking, no synthetic-as-human, no unethical deployment). For a plain-English
introduction to what gates are, why they exist, and what each one checks, read
GATES.md. How often the plugin pauses to ask you vs. acts on its own is
controlled by the per-experiment autonomy level (defaults to supervised); see
AUTONOMY.md for the three levels and how to switch between them.
For a single browsable reference document with every command's purpose, arguments, outputs, and
the gates it triggers, see COMMANDS.md. In-CLI, the same content is
available via /apsy:help:
/apsy:help # list every command + a one-line description
/apsy:help <name> # detailed help for one command (e.g. /apsy:help debug)
/apsy:help --search redis # filter by keyword
Or use /apsy:auto "<free-text intent>" to let the smart router pick the right command for you.
FORMULATE →[G1] BUILD →[G2] PILOT & DEPLOY →[G3/G4] ANALYZE →[G5/G6/G7] PUBLISH
idea→plan experiment code LLM-pilot · humans data → findings paper
╰────────────── iterate ──────────────╯
Seven quality gates (G1-G7) gate transitions — what each one checks is explained in
GATES.md; runnable rubrics live in config/gates/.
/apsy:run walks the whole pipeline autonomously, honoring autonomy_level (see
AUTONOMY.md — supervised / semi_autonomous / autonomous; G4 is always
hard at every level).
Set APSY_PROJECT_DIR once (via /apsy:setup or /apsy:project-dir) and every new study gets a
consistent home; exports + PsyNet's hardcoded data paths are routed into it:
$APSY_PROJECT_DIR/
├── pleasantness-rating/ ← per-experiment dir
│ ├── experiment.py config.txt requirements.txt constraints.txt
│ └── .apsy/ ← state + reports + paper draft
├── color-gsp/
└── data/ ← (optional ~/psynet-data symlink)
├── export/<study>/ ← exports land here
└── assets/ launch-data/ ← PsyNet's other hardcoded dirs
npx claudepluginhub haoyu-hu/auto-psynet --plugin apsyHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.