ansys-agent

Automate ANSYS simulation workflows through doc-driven execution: discover installed ANSYS products and licenses, retrieve official/local API documentation, generate Workbench scripts, Mechanical APDL, PyMAPDL/PyAnsys code, or solver command files, run or guide simulations, diagnose blockers, and search trusted ANSYS forums when needed. Use when Codex is asked to create, modify, run, debug, or explain ANSYS Mechanical, MAPDL, Fluent, Electronics, Workbench, meshing, solving, post-processing, or result export tasks.

Jump to install

Repository: walterkken/doc-driven-engineering-software-skills
Last source activity: May 20, 2026 at 18:11
Detected SKILL.md language: English
Stars: 4
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/walterkken/doc-driven-engineering-software-skills --skill ansys-agent

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

5 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

ANSYS Agent

Overview

Use this skill to convert ANSYS simulation requests into reproducible scripts, solver inputs, output files, and validation notes. Prefer documented ANSYS command-line, scripting, and PyAnsys APIs over manual UI workflows.

Workflow

Frame the simulation: identify product family, physics, geometry, materials, mesh, loads, boundary conditions, solver, outputs, and validation criteria.

Discover access: check Workbench, MAPDL, Fluent, Electronics, PyAnsys packages, licenses, and command-line executables.

Retrieve docs first: use local/official command references, API docs, and examples before generating APDL, Python, journal, or Workbench scripts.

Generate reproducible automation: create scripts or solver input files that can rebuild and rerun the analysis.

Run or guide execution: run command-line/Python workflows when available; otherwise provide exact UI steps for unavoidable UI-only tasks.

Diagnose and unblock: use references/blocker-remediation.md for license checkout, missing products, solver errors, mesh failures, and environment issues.

Search forums when needed: use references/community-troubleshooting.md after official docs and local diagnostics are insufficient.

Report artifacts: list scripts, project files, solver logs, result exports, plots, and assumptions.

Resources

references/software-notes.md: ANSYS-specific automation surfaces and artifacts.

references/blocker-remediation.md: legitimate ways to resolve license, solver, module, and environment blockers.

references/community-troubleshooting.md: trusted forum search process.

Never bypass license checks or suppress solver warnings. Treat engineering simulation outputs as unvalidated until the solver log, mesh quality, units, and expected behavior are reviewed.