run_models

Route NeuroClaw run requests to model docs and modality skills via claw-shell.

78|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/CUHK-AIM-Group/NeuroClaw --skill run-models
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run_models
Source: https://github.com/CUHK-AIM-Group/NeuroClaw/tree/main/skills/run_models
Command: npx skills add https://github.com/CUHK-AIM-Group/NeuroClaw --skill run-models

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized orchestration layer to coordinate NeuroClaw model execution by routing high-level run requests to the appropriate modality-specific skills and model docs, ensuring safe, auditable, and reproducible runs.

Core Features & Use Cases

  • Centralized model routing: selects BrainGNN, FM-APP, NeuroStorm, GLM, ICA, DictLearning, SVM, SpaceNet, K-means, Hierarchical, Filtering, or Detrending workflows and directs preprocessing to the corresponding skill stacks.
  • Execution planning with guardrails: generates a numbered plan, requires user confirmation, and delegates preprocessing to modality skills before execution via claw-shell.
  • Experiment logging and results organization: maintains traceable run artifacts under run_models_output and supports drift monitoring and reproducibility checks.

Quick Start

Request a numbered run plan to select a model and delegate modality preprocessing via fmri-skill and smri-skill.

Frequently Asked Questions about run_models

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

FAQPage Schema
How do I orchestrate end-to-end fMRI model workflows across multiple algorithms like BrainGNN and ICA?

Orchestrate fMRI model workflows by routing high-level run requests to appropriate modality skills and model docs. The system coordinates preprocessing delegation and execution via claw-shell, generating a numbered plan with dependency planning and auditable run-paths.

What is the best way to ensure reproducibility when running NeuroStorm or GLM workflows?

Ensure reproducibility for NeuroStorm or GLM workflows by maintaining traceable run artifacts under run_models_output. The orchestration layer supports drift monitoring, dependency planning, and structured result organization for auditable neuroimaging experiment execution.

Can I use this to route preprocessing steps to modality-specific skills before executing SpaceNet or DictLearning?

Route preprocessing to modality-specific skills like fmri-skill and smri-skill before executing SpaceNet or DictLearning. The system generates a numbered plan, requires user confirmation, and delegates preprocessing to corresponding skill stacks before model execution.

How do I get a numbered execution plan for SVM or K-means clustering with dependency planning?

Generate a numbered execution plan for SVM or K-means by submitting a high-level run request. The system creates a structured plan with pointers to model docs, delegated preprocessing steps, and dependency planning, requiring user confirmation before execution via claw-shell.

Does this workflow orchestration support filtering and detrending as preprocessing steps?

Filtering and detrending are supported as preprocessing workflows within the orchestration layer. The system routes these steps to appropriate modality skills, ensuring safe delegation and execution before producing organized results under run_models_output.