brainx-modeling-loop

Orchestrates end-to-end BrainX brain-modeling projects from specification through Codex review.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/chaobrain/BrainX-skill --skill brainx-modeling-loop-chaobrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainx-modeling-loop
Source: https://github.com/chaobrain/BrainX-skill/tree/main/skills/brainx-modeling-loop
Command: npx skills add https://github.com/chaobrain/BrainX-skill --skill brainx-modeling-loop-chaobrain

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires brainstate, braintools, brainunit, braincell, brainmass, jax, numpy, pandas, matplotlib, and includes references (resource) components.

What problem does it solve? Brain modeling projects involve many error-prone stages—specification, literature verification, implementation, acceleration, experiment execution, and independent review—and losing track of progress or skipping validation steps produces unreliable scientific results. This Skill enforces a rigorous, checkpointed loop that keeps every stage auditable and resumable. ## Core Features & Use Cases - Checkpointed modeling loop: Maintains an append-only brainmodeling-memory.md so work can resume after interruptions without repeating completed experiments or reviews. - Specification and literature gate: Produces a locked NeuroSpecification.md and optionally triggers bio-neuro-lit research when mechanisms are unknown, unverified, or controversial. - Guided implementation and execution: Routes through BrainX package skills (braincell, brainpy-state, brainmass), acceleration parity checks, and immutable run snapshots via run-experiment and monitor-experiment references. - Independent Codex review: Sends each iteration's code and results to the Codex MCP server, preserving verbatim review reports and looping back on REFUSE verdicts. - Use Case: A researcher asks for a Hodgkin-Huxley parameter-fitting study; the Skill writes the specification, studies the relevant BrainX skills, implements and accelerates the model, runs the experiment, obtains a Codex review, and only visualizes results after the review passes. ## Quick Start Use brainx-modeling-loop to start a new BrainX modeling project from my research question, or resume the existing loop recorded in brainmodeling-memory.md.

Frequently Asked Questions about brainx-modeling-loop

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

FAQPage Schema
How do I run an end-to-end BrainX modeling project?

Invoke the modeling loop, which writes a locked NeuroSpecification.md, studies the relevant BrainX package skills, implements and accelerates the model, runs the experiment, and submits everything to Codex review. Progress is checkpointed in brainmodeling-memory.md after every step.

How do I resume an interrupted BrainX modeling loop?

The loop reads brainmodeling-memory.md, verifies the latest checkpoint's artifact pointers, and continues from the first unfinished action. Completed experiments and Codex reviews are never repeated just because terminal context was lost.

When does the loop trigger literature research with bio-neuro-lit?

Literature research triggers only when unresolved scientific evidence could change the model, experiment, validation, or allowed claims—such as unknown mechanisms, unverified premises, or controversial explanations. Ordinary BrainX API or implementation uncertainty routes to the package skills instead.

What happens when the Codex review returns REFUSE?

The iteration increments, the loop returns to step 1, and every reviewer finding is mapped to the owning BrainX package skill for restudy before code changes. Steps 1-5 repeat with the same training or fitting coverage until the review passes.

Can I use task training or parameter fitting inside the modeling loop?

Yes, the specification's execution mode selects coverage: training-workflow.md for task-training, parameter-fitting-workflow.md for parameter-fitting, or both for hybrid. The chosen reference stays active through implementation, acceleration, experiment execution, and review.

Why is visualization blocked after a successful experiment?

Visualization only occurs after the Codex review passes, and the planned visualization-workflow.md reference has not been authored yet. Until it exists, the loop preserves accepted artifacts and records step 6 as blocked in the memory file.