Cai-aa/CAE-Agent-Hub

---

name: abaqus-contact-analysis

description: Analyze multi-body contact. Use when user mentions parts touching, friction between surfaces, bolt-plate contact, press fit, or assembly with contact.

---

name: abaqus-coupled-analysis

description: Complete workflow for coupled thermomechanical analysis. Use when user mentions thermal stress, thermal expansion, or temperature causing deformation.

---

name: abaqus-dynamic-analysis

description: Complete workflow for dynamic analysis. Use when user mentions impact, crash, drop test, transient, or time-varying response. Handles explicit and implicit dynamics.

---

name: abaqus-fatigue-analysis

description: Workflow for fatigue and durability analysis - cycle counting, damage accumulation, and fatigue life prediction.

---

name: abaqus-modal-analysis

description: Complete workflow for modal/frequency analysis - extract natural frequencies and mode shapes. Use for vibration analysis and resonance avoidance.

---

name: abaqus-static-analysis

description: Complete workflow for static structural analysis. Use when analyzing stress, displacement, or reaction forces under constant loads. For strength and stiffness evaluation.

---

name: abaqus-thermal-analysis

description: Complete workflow for heat transfer analysis - steady-state and transient thermal. Use when user asks about temperature distribution, conduction, convection, or heat flow.

---

name: composite-curing-simulation

description: Master skill for composite curing simulation with mold contact, friction, temperature, and Model Change springback in Abaqus. Invoke when user asks for curing simulation, springback analysis, composite layup with mold, or UMAT subroutine for composites. Routes to specialized sub-skills.

---

name: abaqus

description: Master skill for Abaqus FEA scripting. Use for any finite element analysis, topology optimization, or Abaqus Python scripting task. Routes to appropriate specialized skills.

---

name: abaqus-export

description: Export Abaqus geometry and results. Use when user mentions exporting to STL, STEP, CSV, or generating input files for external use.

---

name: abaqus-job

description: Create and manage Abaqus jobs. Use when user asks to run the analysis, submit the job, execute the model, or generate input file.

---

name: abaqus-geometry

description: Create and manipulate Abaqus geometry - parts, sketches, extrusions, CAD import. Use for any geometry creation task including box, cylinder, or STEP/IGES import.

---

name: abaqus-interaction

description: Define contact and interactions - contact pairs, tie constraints, connectors. Use when user mentions contact, friction, tie, parts touching, or bonded surfaces.

---

name: abaqus-material

description: Define material properties for FEA models. Use when user mentions steel, aluminum, Young's modulus, elastic, plastic, density, or asks about material properties.

---

name: abaqus-mesh

description: Generate finite element meshes. Use when user mentions mesh, elements, nodes, refine mesh, mesh size, or asks about element types like C3D8R, C3D10, S4R.

---

name: abaqus-optimization

description: Configure Tosca optimization. Use when user mentions design response, objective function, optimization constraint, or SIMP penalty. Base module for topology/shape optimization.

---

name: abaqus-shape-optimization

description: Optimize fillet/notch geometry. Use when user mentions stress concentration, fillet optimization, reshaping surfaces, or reducing peak stress. Moves surfaces only.

---

name: aedt-evidence-electromagnetics

description: Evidence-first Ansys Electronics Desktop and PyAEDT automation for Maxwell, HFSS, Q3D, Icepak, and related electromagnetic workflows. Use when Codex must check AEDT/PyAEDT, create or run a real AEDT design, verify the selected design and solution type, extract fields or matrices, export an .aedt project, or distinguish direct PyAEDT work from an AEDT MCP bridge.

---

name: ansys-mechanical-evidence-structural

description: Evidence-first Ansys Mechanical structural automation through Workbench RunWB2 journals, Mechanical Scripting/ACT ExtAPI, or PyMechanical gRPC. Use when Codex must build, solve, inspect, postprocess, or validate static, modal, thermal-structural, contact, nonlinear, or other Mechanical analyses with mesh metrics, MAPDL logs, reaction balance, RST files, numeric exports, and result images.

---

name: ansys-structural-workbench

description: Operate or inspect live ANSYS Workbench Mechanical structural simulations through the configured MCP, including model setup, materials, connections, loads, mesh, solve, convergence, validation, and reporting. Use whenever a user asks Codex to create, configure, inspect, mesh, solve, troubleshoot, or validate a live Workbench structural analysis. Before model decisions or mutation, load ansys-workbench-practical-reference once as the book-distilled router and then the matching narrow reference Skill. Load static-modeling for every Static Structural task, plus nonlinear-contact for contact, friction, plasticity, large deformation, buckling, or nonlinear convergence. Do not use for theory-only questions or Fluent/CFX operation.

---

name: run-fluent-autoclave

description: Run, diagnose, reproduce, and validate ANSYS Fluent CFD simulations of forced-convection autoclaves using Fluent MCP or PyFluent. Use for autoclave or hot-air vessel projects involving SCDOC/STEP geometry, annular velocity inlets, pressure outlets, Spalart-Allmaras turbulence, energy transport, calorimeter temperature boundaries, automatic meshing, longitudinal velocity contours, streamlines, mass-balance checks, or the Bohne paper boundary-condition case.

---

name: calculix-fem

description: Workflow skill for driving the CalculiX MCP server over .inp decks — model inspection, in-place design-variable edits, ccx solve, .dat result reading, and result_mesh.json export for the viewer. Use when an agent must run an open-source linear-static FEM analysis on CalculiX, tune section/material/load parameters, or produce a viewer-renderable result.

---

name: calculix-modal-analysis

description: Workflow skill for CalculiX modal analysis (*FREQUENCY steps) — natural frequencies and mode shapes via the CalculiX MCP. read_results returns the frequency table; export_results with mode=N renders that mode shape in the browser viewer. Use when an agent must extract natural frequencies, check resonance margins, or visualize mode shapes on an open-source solver.

---

name: calculix-sizing-optimization

description: Workflow skill for two-stage sizing/parameter optimization on a CalculiX shell or beam deck via the optimize_structure tool — Latin Hypercube sweep plus coordinate descent to minimize mass subject to stress/displacement or natural-frequency constraints by tuning scalar section/material/load cards. Use when an agent must lighten a CalculiX shell or beam model while keeping stress and deflection within limits, or must thin a deck until its first modes clear a resonance floor (freq_1_hz constraint on a *FREQUENCY deck).

---

name: comsol-motor-nvh-evidence

description: Evidence-first COMSOL Java API and batch workflow for permanent-magnet motor NVH. Use when Codex must build, resume, solve, validate, or report a 2D motor model that couples rotating magnetic machinery, Maxwell-force harmonics, structural eigenmodes, pressure acoustics, acoustic-structure interaction, far-field SPL, or Campbell sweeps; also use when converting an existing motor NVH prompt or run into public-safe scripts, checkpoints, exports, and acceptance evidence.

---

name: cst-simulation-workflow

description: Use this skill when driving CST Studio Suite through the CST MCP for electromagnetic simulation workflows: creating or opening CST projects, resolving missing inputs, selecting templates, setting up geometry/materials/ports/boundaries/mesh/solvers/monitors, running or planning simulations, extracting S-parameters/far-field/near-field/eigenmode results, validating outputs, parameter sweeps, optimization handoff, and report generation.

---

name: fep-agent-hub

description: Orchestrate and validate evidence-first CAE workflows through the independent FreeCAD, Elmer FEM, and ParaView MCP servers in FEP Agent Hub. Use for FEP repository setup or diagnostics; CAD-to-mesh-to-solver-to-postprocessing automation; steady or transient heat transfer; 2D harmonic transformer induction; 2D plane-stress beams; 2D steady laminar channel flow; 2D transient eddy-current and Lenz-law studies; regression, acceptance reports, or scientifically honest CAE videos built from these verified profiles.

---

name: cylinder-o-grid

description: Plan, create, adapt, and quality-audit coin-style five-block O-grid hexahedral meshes for cylindrical CAE models. Use for software-independent O-grid planning or implementation in a selected preprocessor, including requests mentioning 钱币原理、圆柱网格、中心正方形、顶点切到圆周、结构化六面体网格, mapped square-to-circle partitions, or HEX8 meshes. Includes a generic planner and an Abaqus/CAE execution adapter; do not claim automated support in another CAE application without a matching adapter or proved live native-tool path.

---

name: lammps-evidence-md

description: Evidence-first LAMMPS molecular-dynamics workflow for input decks, potentials, minimization, equilibration, deformation, thermo logs, trajectories, restart/data files, stress-strain extraction, and reproducibility checks. Use when Codex must prepare, run, diagnose, or report a LAMMPS materials simulation or hand its trajectory to OVITO without overstating nanoscale demo results as calibrated macroscopic properties.

---

name: ovito-evidence-postprocessing

description: Evidence-first OVITO atomistic postprocessing for LAMMPS trajectories and other particle data, including pipeline construction, modifiers, coloring, clipping, camera setup, images, animations, tables, and state files. Use when Codex must inspect or present molecular-dynamics results while distinguishing OVITO Basic GUI availability from ovitos/external Python automation and separating rendering evidence from upstream solver evidence.