vibeflow-moose

Coordinate MOOSE-based simulation workflows inside VibeCAE.

12|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-moose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibeflow-moose
Source: https://github.com/sunrise-hjx/vibeFlow-skills/tree/main/vibeflow-moose
Command: npx skills add https://github.com/sunrise-hjx/vibeFlow-skills --skill vibeflow-moose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamline preparation, execution, debugging, and development of MOOSE-based simulations within VibeCAE, enabling teams to orchestrate complex multiphysics workflows from a unified interface.

Core Features & Use Cases

  • Backend mode handling: decide between using an existing MOOSE app or developing a custom app/module, and generate the corresponding input templates and run wrappers.
  • Debugging and validation: leverage TestHarness, HIT inputs, and traceability to 0-caseDict/caseDict with full logging and diagnostics.
  • Workflow integration: support for input generation, app execution, results extraction, and reference to up-to-date playbooks (moose-playbook.md, moose-practical-tips.md) for guidance.

Quick Start

Start by selecting the MOOSE backend, then generate and run a minimal case to verify inputs, execution, and logs.

Frequently Asked Questions about vibeflow-moose

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

FAQPage Schema
How do I generate MOOSE input files from a caseDict within VibeCAE?

MOOSE input file generation from a caseDict is handled by mapping caseDict-driven inputs to executable MOOSE applications. The workflow generates corresponding input templates and run wrappers to validate inputs before execution.

How do I debug MOOSE simulation results using TestHarness and HIT inputs?

Debugging MOOSE simulation results leverages TestHarness validation and HIT input parsing with full logging and diagnostics. It provides traceability back to the original caseDict to identify input mapping errors during execution.

Can I use this to develop a custom MOOSE application or module instead of an existing one?

Developing a custom MOOSE application or module is fully supported. Backend mode handling decides between using an existing MOOSE app or developing a custom one, then generates the matching input templates and run wrappers.

What is the best way to orchestrate multiphysics MOOSE workflows end to end?

Orchestrating multiphysics MOOSE workflows is streamlined by integrating input generation, app execution, results extraction, and debugging into a unified interface. It references official playbooks for validation guidance throughout the process.

Why are my MOOSE workflow runs failing to map caseDict inputs to executable apps?

MOOSE workflow run failures during caseDict input mapping are addressed through full logging and diagnostics. Traceability to the original caseDict and TestHarness validation help isolate mismatches between generated inputs and executable apps.

Do I need to reference official MOOSE playbooks to validate my simulation workflows?

Official MOOSE playbooks are referenced automatically within the workflow for validation guidance. Up-to-date references like moose-playbook.md and moose-practical-tips.md provide best practices for running and debugging MOOSE applications.