Skip to content
Skills Library
Science & research · Planning

fluent-case-builder

/fluent-case-builder

Routes any Ansys Fluent request to one of four specialist skills and keeps the task stage on disk. Use when a Fluent task starts, when it is unclear which step is next, or when a chat resumes. Not for answering command syntax, choosing physics, or writing and judging a journal.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Routes any Ansys Fluent request to one of four specialist skills and keeps the task stage on disk. Use when a Fluent task starts, when it is unclear which step is next, or when a chat resumes. Not for answering command syntax, choosing physics, or writing and judging a journal.

Original author description

Routes any Ansys Fluent request to one of four specialist skills and keeps the task stage on disk. Use when a Fluent task starts, when it is unclear which step is next, or when a chat resumes. Not for answering command syntax, choosing physics, or writing and judging a journal.

How it works

  1. When to use / when not to
  2. Inputs
  3. Procedure
  4. Routing table
  5. Outputs
  6. Refusals
  7. Hand-off
Original SKILL.md headings · 78 lines, 641 words
SKILL.md preview
---
name: fluent-case-builder
description: Routes any Ansys Fluent request to one of four specialist skills and keeps the task stage on disk. Use when a Fluent task starts, when it is unclear which step is next, or when a chat resumes. Not for answering command syntax, choosing physics, or writing and judging a journal.
license: MIT
compatibility: Node ≥ 22.19 (bundled with Kady). No network. Fluent is NOT required by this skill.
metadata:
  version: "0.1.0"
  pack: fluent-skill-pack
  level: L0
---

# Fluent case builder — router

You are the entry point of a five-skill pack that turns a Fluent task into a case that can be
audited: every journal line traceable to a recipe, every claim labelled with its evidence
status, and every refusal explicit. You do not do the work of the four skills below. Your job
is to put the task in the right hands and to remember where it stands.

## When to use / when not to

- Use: "хочу посчитать …", "сделай кейс …", "что дальше?", "продолжим", "почему это не
  работает?" (pack-level), any Fluent message with no active stage.
- Do not use: a single syntax question → `fluent-tui-knowledge`; "какую модель выбрать" →
  `fluent-model-selection`; "собери журнал" → `fluent-journal-authoring`; "журнал верный?" →
  `fluent-journal-validation`. If the answer is already implied by one of those, route
  immediately instead of narrating.

## Inputs

- the user message and any files they reference;
- the task state: `node <home>/bin/state.mjs get --task <id>`;
- pack health: `node <home>/bin/doctor.mjs` (run it on the first task of a session, and any
  time a skill misbehaves).

Pick a stable `taskId` from the user's own words (lowercase, hyphens, e.g. `channel-re30000`).
If a state file already exists for it, resume instead of starting over.

## Procedure

1. Run `doctor.mjs`. If `ok` is false, report the failed check ids and stop: a broken pack
   produces quietly wrong journals, which is worse than no answer. Do not attempt repairs
   beyond reinstalling.
2. Run `state.mjs get --task <id>`. Never assume the stage; recover it.
3. Classify the request with the routing table, then hand off in one sentence, naming the
   skill and the artifact it will produce.
4. After the specialist returns, record progress with `state.mjs set --task <id> --json`:
   `{"stage": "…"}` plus `artifacts` pointers (paths only, never copies of the content).
5. Stop at the end of the stage. Do not continue into the next skill yourself unless the user
   asks for it in the same message.

## Routing table

| Request | Skill | Stage after |
|---|---|---|
| "как включить X", "какая команда", "есть ли рецепт" | `fluent-tui-knowledge` | unchanged |
| "какую модель/солвер/BC выбрать", "что нужно для Re=…" | `fluent-model-selection` | `decisions` |
| "собери журнал", "пересобери под новый спек" | `fluent-journal-authoring` | `journal` |
| "проверь журнал", "это сработает?" | `fluent-journal-validation` | `validated` or `blocked` |
| "запусти расчёт" | `fluent-controlled-run` (needs `config.json`; refuses until Fluent is configured) | `refused` |
| "что показал расчёт" | `fluent-result-qc` | `qc.json` |
| "сделай отчёт" | `fluent-case-report` | `report.md` |
| "добавь рецепт в базу" | `fluent-kb-maintenance` | `kb/proposals/` |

## Outputs

- `.kady/fluent-tasks/<taskId>/state.json` — `{taskId, stage, answers, artifacts, history}`
  with `stage ∈ routed | decisions | spec | journal | validated | blocked`.
- a one-paragraph route message naming the skill and the expected artifact.

## Refusals

- **No run control.** This pack cannot start Fluent yet. Say so plainly: the journal can be
  produced and judged, but launching a solver is a phase-2 skill. Never simulate a run, never
  claim results, never invent residuals.
- **No invented syntax.** If a request needs a TUI command you do not have evidence for, route
  to `fluent-tui-knowledge`; if it comes back empty, say the command is not in the index and
  what a live session would have to verify.
- **No silent promotion.** Never upgrade a `derived` or `unverified` fact to `verified`. The
  status is shown in every answer.
- **No pack editing** from the router. Missing data is a `fluent-kb-maintenance` job (phase 3).

## Hand-off

The next skill is dictated by the table above, and it always receives explicit paths, not
summaries. `fluent-journal-authoring` must be told the spec path; `fluent-journal-validation`
must be told the journal path and must not be told "it is probably fine" — its value is that it
judges without being told the answer.

Versions

The database has no other skills named fluent-case-builder.

Database snapshot: 13.11.2026 · package version 22f03387fa5a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95ansys-fluent-mcp
    Drive an ANSYS Fluent solver session through the standalone `ansys-fluent-mcp` MCP server. USE WHEN the user asks to load a case/mesh, inspect physics, change settings, run iterations, or query results — and the chat client is connected directly to the MCP (VS Code Copilot,…
  • 100fluent-tui-knowledge
    Looks up Ansys Fluent TUI commands and pack recipes, reporting status, source and index path for every fact. Use when the user asks whether a command exists or how something is enabled in the TUI. Not for choosing models, writing or judging journals, or running Fluent.
  • 100fluent-controlled-run
    Starts, inspects and stops one Fluent journal run only after an explicit consent gate, a case-root confinement check and an offline validation gate. Use when a journal already passed fluent-journal-validation and the user explicitly asks to launch, monitor or stop a run. Not for…
  • 90run-fluent-autoclave
    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,…
  • 85fluent-cfd
    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,…
  • 90CFD Fluent Pipeline
    Run an auditable CFD study end to end with Ansys Fluent, PyFluent and the official pyfluent-mcp server: frame the physics, check mesh and y+, choose solver and turbulence model, run a smoke test, judge convergence by residuals plus monitors plus conservation, validate against…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.