fluent-cfd-skill
A Codex skill for Ansys Fluent and PyFluent CFD workflows.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/cavoiie--fluent-cfd-skill)HTML
<a href="/listings/cavoiie--fluent-cfd-skill"><img src="/api/listings/cavoiie--fluent-cfd-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Copy this folder to your Codex skills directory:
Copy-Item -Recurse . "$env:USERPROFILE\.codex\skills\fluent-cfd"
After installation, Codex can trigger the skill when a task mentions Fluent, PyFluent, Fluent TUI, CFD simulation setup, mesh quality, boundary conditions, turbulence models, residual convergence, UDFs, or post-processing.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 57 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- ---
- name: fluent-cfd
- description: Guide Ansys Fluent and PyFluent CFD simulation workflows with MCP tool-use discipline. Use when Codex works on Fluent, PyFluent, Fluent TUI, CFD or fluid simulation setup, case/data files, mesh quality, boundary conditions, turbulence models, residual convergence, UDFs, post-processing, solver diagnostics, or validation of Ansys Fluent results.
- ---
- # Fluent CFD
- Use this skill as the workflow and judgment layer for Ansys Fluent work. Keep Fluent documentation as the fact source, use the local `pyfluent` MCP server as the execution layer, and use this skill to decide the order of operations, checks, and validation criteria.
- ## Operating Rules
- - Define the physics before touching the solver: objective quantity, geometry, units, fluid, regime, steady/transient behavior, compressibility, heat transfer, multiphase, rotating zones, and expected validation evidence.
- - Do not treat residual decrease alone as convergence. Require monitor stabilization and conservation checks for the quantities that matter.
- - Do not skip mesh quality, units, boundary-zone naming, boundary-condition consistency, and wall-resolution checks.
- - Do not change turbulence models without a physical reason or a stated validation purpose.
- - Prefer safe MCP tools and explicit Fluent TUI commands. Use `execute_python` only when `PYFLUENT_MCP_ENABLE_PYTHON=1` and the workflow is trusted.
- - Before starting Fluent or consuming a license, state that the action will launch Fluent and may occupy a license/session.
- - End live Fluent sessions with `exit_fluent` when the task is complete unless the user asks to keep the session open.
- ## Workflow
- 1. Frame the case: identify objective metrics, physics, known inputs, missing data, expected outputs, and acceptance criteria.
- 2. Choose solver and models: decide pressure-based vs density-based, steady vs transient, energy, multiphase, turbulence, wall treatment, and reference values.
- 3. Check the mesh and setup basis: units, cell/face zones, boundary names, quality metrics, non-orthogonality/skewness, and y+ target.
- 4. Set or review materials, boundary conditions, operating/reference conditions, numerics, initialization, and monitors.
- 5. Run a smoke test first: a short iteration/time-step run to catch setup errors before a full solve.
- 6. Iterate or advance time while monitoring residuals, integral balances, and objective quantities.
- 7. Save case/data and report validation status, remaining risks, and next checks.
- ## Reference Loading
- Load only the reference files needed for the current task:
- - `references/workflow.md`: complete Fluent workflow and task routing.
- - `references/solver-selection.md`: model and solver selection rules.
- - `references/boundary-conditions.md`: inlet, outlet, wall, symmetry, periodic, and rotating-zone boundary checks.
- - `references/turbulence-and-wall-treatment.md`: turbulence model, wall treatment, y+, and mesh implications.
- - `references/numerics-and-convergence.md`: discretization, initialization, monitors, residuals, and convergence.
- - `references/pyfluent-mcp.md`: local `pyfluent` MCP tools, call order, safety limits, and failure handling.
- - `references/validation-checklist.md`: conservation, mesh independence, physical plausibility, and post-processing checks.
- - `references/error-recovery.md`: divergence, reversed flow, negative volume, CFL, residual stalls, and launch/license failures.
- ## MCP Tool Discipline
- When a task requires real Fluent execution through the local MCP server:
- 1. Call `server_info` first to confirm PyFluent, Ansys roots, and whether Python execution is enabled.
- 2. Call `launch_fluent` only after stating that Fluent will start and may consume a license.
- 3. Use `read_case` for existing `.cas`, `.cas.h5`, or equivalent case files.
- 4. Use `run_tui` for explicit, auditable Fluent TUI commands.
- 5. Use `iterate` for a defined iteration count; prefer a short smoke run before long runs.
- 6. Use `session_status` after suspicious behavior or long operations.
- 7. Use `write_case_data` before closing if the state should be preserved.
- 8. Use `exit_fluent` at the end of the workflow unless the user explicitly wants the session left open.
- If a tool returns an error, stop the automation sequence, summarize the failure, read `references/error-recovery.md` if relevant, and propose the smallest safe recovery.
README.md · README · 77 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- # Fluent CFD Skill
- English | [简体中文](README.zh-CN.md)
- A Codex skill for Ansys Fluent, PyFluent, and CFD simulation workflows.
- This repository packages a research-oriented workflow skill for working with Fluent cases, solver setup, convergence diagnosis, and PyFluent MCP automation. It is designed as a judgment layer for agents: it does not replace the Fluent manuals, and it does not bundle a Fluent runtime.
- ## Highlights
- - Fluent workflow discipline from problem framing to validation.
- - PyFluent MCP tool-use guidance for safe, auditable Fluent automation.
- - Convergence checks that combine residuals, monitors, conservation, and physical plausibility.
- - Practical references for solver choice, boundary conditions, turbulence, numerics, validation, and error recovery.
- - Conservative defaults for research use: no arbitrary Python execution unless explicitly enabled in the local MCP server.
- ## Repository Layout
- ```text
- .
- +-- SKILL.md
- +-- agents/
- | +-- openai.yaml
- +-- references/
- +-- workflow.md
- +-- solver-selection.md
- +-- boundary-conditions.md
- +-- turbulence-and-wall-treatment.md
- +-- numerics-and-convergence.md
- +-- pyfluent-mcp.md
- +-- validation-checklist.md
- +-- error-recovery.md
- ```
- `SKILL.md` is intentionally compact. It routes the agent through the core CFD workflow and points to focused references only when needed.
- ## Use Cases
- - Plan a Fluent case setup before touching the solver.
- - Review boundary conditions, mesh quality, and physical assumptions.
- - Choose solver settings, turbulence models, wall treatment, and convergence criteria.
- - Diagnose residual stalls, reversed flow, divergence, and launch/license failures.
- - Guide PyFluent MCP workflows such as launch, read case, run TUI commands, iterate, save, and close.
- ## Prompt Templates
- Use the standard templates in [PROMPTS.md](PROMPTS.md) for full CFD reviews, short daily checks, PyFluent MCP runs, and convergence diagnosis.
- ## Installation
- Copy this folder to your Codex skills directory:
- ```powershell
- Copy-Item -Recurse . "$env:USERPROFILE\.codex\skills\fluent-cfd"
- ```
- After installation, Codex can trigger the skill when a task mentions Fluent, PyFluent, Fluent TUI, CFD simulation setup, mesh quality, boundary conditions, turbulence models, residual convergence, UDFs, or post-processing.
- ## Versioning
- Versions are managed with GitHub Releases and semantic version tags. Use the latest release for a stable skill snapshot, and use `main` for active edits.
- ## Safety Notes
- - Residual decrease alone is not convergence.
- - Mesh quality, units, boundary consistency, and wall-resolution checks should not be skipped.
- - Turbulence model changes should have a physical reason or validation goal.
- - The optional `execute_python` MCP tool should stay disabled unless the local workflow is trusted.
- - This repository contains only the skill. A separate local PyFluent MCP server is required for live Fluent control.
- ## Related Execution Layer
- The skill is designed to pair with a local `pyfluent` MCP server that exposes tools such as `server_info`, `launch_fluent`, `read_case`, `run_tui`, `iterate`, `write_case_data`, `session_status`, and `exit_fluent`.
- That execution layer is intentionally separate from this repository so this skill remains lightweight, portable, and safe to publish.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.