ansys-structural-workbench

ANSYS Structural Workbench

Operate Workbench as an engineering workflow with explicit quality gates. Treat the MCP as the execution adapter and this Skill as the analysis, meshing, validation, and reporting policy.

Start safely

1. Discover the available Workbench MCP tools and read references/mcp-adapter.md.
2. Probe both bridge health and live Workbench/Mechanical state. A reachable server is not proof that a project, Model, or analysis is loaded.
3. Convert the request into the contract in references/job-spec.md, including every applicable analysis profile. Use a temporary in-memory object unless a saved spec benefits the task.
4. Inspect the current project before mutation. Never clear, overwrite, suppress, or replace existing user work without explicit authorization.
5. Record assumptions. Stop for missing information only when no conservative, reversible default exists.

If the MCP lacks a required capability, use its generic Workbench/Mechanical script-execution tool when available. Otherwise report the exact unsupported gate; do not fabricate completion.

Select references

Always read:

• references/core-workflow.md
• references/quality-gates.md

Then read only what applies:

• Analysis behavior: references/analysis-profiles.md
• Mesh generation or review: references/mesh-orchestration.md and references/mesh-profiles.md
• Solver failure or warnings: references/solver-diagnostics.md
• Double-shear clevis regression/smoke test: references/example-clevis-pin.json

Execute the gated workflow

1. CAPABILITY_CHECK: prove that the MCP can inspect, modify, mesh, solve, query results, and export the evidence required by the selected profile set.
2. INTAKE: normalize model source, units, materials, analysis profile, outputs, and acceptance criteria.
3. MODEL_INSPECTION: inventory bodies, dimensions, materials, named selections, connections, analyses, loads, supports, and existing results.
4. MODEL_SETUP: create only missing or authorized objects. Prefer existing named selections; otherwise use validated geometry predicates.
5. MODEL_GATE: verify entity counts, geometry properties, material coverage, connection scoping, units, load directions, and rigid-body restraint.
6. MESH_PLAN: classify bodies and critical regions before generating mesh.
7. MESH_GATE: generate, inspect distributions and worst elements, repair by approved actions, and reject hard failures.
8. PRE_SOLVE_GATE: inspect initial contact state where applicable and verify load-step tables and solution controls.
9. SOLVE: solve and retain solver output, warnings, errors, substep history, and final converged time.
10. SOLVER_GATE: reject incomplete or unconverged final states even if the UI says Completed.
11. RESULT_EXTRACTION: extract scoped engineering quantities, reactions, energy, contact quantities, modal/buckling values, mesh statistics, and evidence images.
12. VALIDATION_GATE: run deterministic checks and compare with analytical, test, or user-defined criteria when available.
13. CONVERGENCE_GATE: compare at least the final two mesh levels for every configured metric. Do not use a singular peak stress as the only metric.
14. REPORT: state pass, warning, blocked, or unsupported; include assumptions, evidence paths, limitations, and unresolved warnings.