Ansys Mechanical Evidence Structural logo

Ansys Mechanical Evidence Structural

CommunityPopular
Cai-aa
ansys-mechanical-evidence-structural

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.

Overview

PublisherCai-aa
RepositoryCAE-Agent-Hub
Skill nameansys-mechanical-evidence-structural
Stars
1K
Forks
130
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Cai-aa on GitHub. Read the source before you install it.

Installation

Install the Ansys Mechanical Evidence Structural AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/Ansys/ansys-mechanical-evidence-structural
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Cai-aa/CAE-Agent-Hub.git /tmp/CAE-Agent-Hub
mkdir -p .claude/skills
cp -r /tmp/CAE-Agent-Hub/Skill/Ansys/ansys-mechanical-evidence-structural .claude/skills/ansys-mechanical-evidence-structural
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ansys Mechanical Evidence Structural in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ansys Mechanical Evidence Structural on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ansys Mechanical Evidence Structural is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ansys Mechanical Evidence Structural

Treat Mechanical as its own solver module. Workbench is an orchestration route, not proof that the Mechanical analysis solved.

Start

powershell
ai-cae-toolbox context-scope --solver ansys-mechanical
ai-cae-toolbox bridge-plan --solver ansys-mechanical --objective "<objective>"
ai-cae-toolbox create-run --solver ansys-mechanical --case <case-name> --objective "<objective>"

If MCP is available, prefer:

  • mechanical_check_installation
  • mechanical_run_workbench_journal_file
  • mechanical_run_python_controller_file
  • mechanical_validate_result_summary_file

Choose One Control Route

  1. Use RunWB2.exe -B -R <journal.wbjn> for project-level orchestration.
  2. Use Mechanical Scripting/ACT with ExtAPI for model-tree operations.
  3. Use PyMechanical gRPC for an external Python controller and explicit session lifecycle.

Record the selected route and do not let two controllers own the same session.

Model and Solve

Audit units, geometry scale, materials, contacts, joints, loads, constraints, large-deflection setting, solver controls, result requests, and mesh controls. Use stable names for bodies, named selections, contacts, loads, and results.

Before claiming success, read references/acceptance-gates.md. A .mechdat, Workbench project, or result PNG alone is insufficient.

Finish

Export .mechdat or .wbpj, file.rst, solve.out, mesh metrics, load and reaction data, result CSV/JSON, PNG images, and report.md. State every approximation such as bonded contacts, suppressed bodies, linear materials, or disabled large deformation.

powershell
ai-cae-toolbox scan-evidence <run-dir>
ai-cae-toolbox generate-report <run-dir>

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ansys Mechanical Evidence Structural AI skill do?

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.

Why use Ansys Mechanical Evidence Structural on TypingMind?

Because you install it once and use it with any model. Ansys Mechanical Evidence Structural is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ansys Mechanical Evidence Structural in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Cai-aa/CAE-Agent-Hub/tree/main/Skill/Ansys/ansys-mechanical-evidence-structural. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ansys Mechanical Evidence Structural?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ansys Mechanical Evidence Structural?

As many as you like. As long as a model supports skills, you can use Ansys Mechanical Evidence Structural with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ansys Mechanical Evidence Structural AI skill free?

Yes. It is published on GitHub by Cai-aa under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇