菜单
Evidence-first workflow for MATLAB/Simulink, OpenFOAM, and ParaView automation. Use when the user asks Codex to run MATLAB scripts, Simulink smoke checks, OpenFOAM cases, ParaView postprocessing, or public-safe AI CAE Automation Lab run records.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Abaqus evidence-first modeling and simulation workflow for Codex. Use when the user asks to build, run, submit, validate, postprocess, or report Abaqus/CAE or Abaqus input-deck simulations with real logs, job status, ODB evidence, screenshots, CSV exports, and AI CAE Automation Lab run records.
Evidence-first run management for AI-assisted CAE and engineering automation. Use when Codex needs to plan, execute, audit, or report a simulation/CAD automation task with AI CAE Automation Lab, MCP tools, run folders, evidence scans, credibility grading, or report generation.
COMSOL Multiphysics evidence-first automation workflow for Codex. Use when the user asks to inspect COMSOL installations, Java API docs, Model Builder scripts, batch runs, MPH files, heat transfer, CFD, photonics, multiphysics simulation, result exports, or AI CAE Automation Lab run records.
Ansys Fluent evidence-first CFD workflow for Codex. Use when the user asks to prepare, run, journal, automate, validate, postprocess, or report Fluent CFD simulations using batch journals, PyFluent, TUI commands, residual logs, case/data files, exported plots, CSV reports, and AI CAE Automation Lab run records.
PCSCHEMATIC Automation evidence-first electrical CAD workflow for Codex. Use when the user asks to inspect PCSCHEMATIC installations, COM/OLE automation, scripts, component databases, symbol libraries, electrical schematic generation, terminal lists, component lists, cable lists, exports, or AI CAE Automation Lab run records.
| name | open-toolchain-evidence |
| description | Evidence-first workflow for MATLAB/Simulink, OpenFOAM, and ParaView automation. Use when the user asks Codex to run MATLAB scripts, Simulink smoke checks, OpenFOAM cases, ParaView postprocessing, or public-safe AI CAE Automation Lab run records. |
Use this skill for MATLAB/Simulink, OpenFOAM, and ParaView tasks that need traceable execution. Do not claim a model, case, or visualization succeeded unless logs and exported artifacts exist.
ai-cae-toolbox env-check --json
ai-cae-toolbox bridge-plan --solver <matlab|openfoam|paraview> --objective "<objective>"
ai-cae-toolbox create-run --solver <solver> --case <case-name> --objective "<objective>"
ai-cae-toolbox write-smoke-template --solver <solver> --run-dir <run-dir> --case <case-name>
If the MCP server is available, prefer:
solver_bridge_planwrite_solver_smoke_templatematlab_check_installationmatlab_run_script_fileopenfoam_check_installationopenfoam_run_case_commandparaview_check_installationparaview_run_pvpython_scriptscan_run_evidencegenerate_run_report.m source, .mat or CSV outputs, figures, and diagnostics.log.*, blockMesh/checkMesh output, residual data, and result folders.Do not commit proprietary Simulink models, private geometry, large OpenFOAM time directories, or screenshots that expose private project names. Keep heavy result folders in local run directories or private releases.
ai-cae-toolbox scan-evidence <run-dir>
ai-cae-toolbox generate-report <run-dir>
Report missing software, failed imports, missing case directories, and rendering errors honestly.