Individual skill

fep-agent-hub

Orchestrate and validate evidence-first CAE workflows through the independent FreeCAD, Elmer FEM, and ParaView MCP servers in FEP Agent Hub. Use for FEP repository setup or diagnostics; CAD-to-mesh-to-solver-to-postprocessing automation; steady or transient heat transfer; 2D harmonic transformer induction; 2D plane-stress beams; 2D steady laminar channel flow; 2D transient eddy-current and Lenz-law studies; regression, acceptance reports, or scientifically honest CAE videos built from these verified profiles.

Skill/fep-agent-hub/SKILL.md

Read pinned source

Source commit 56705e07ce6e99f0d5a0d0c7b5e28b6b2c0bc973

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,299
Repository last updated: Oct 27, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

legal Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 5,688 bytes
agents/openai.yamlasset · 236 bytes
references/case-catalog.mddoc · 5,327 bytes
references/orchestration.mddoc · 4,378 bytes
references/validation-and-claims.mddoc · 4,917 bytes

Read excerpt


# FEP Agent Hub

Run the three MCP servers as independent stages joined by manifests, semantic IDs, native solver artifacts, and explicit physics gates. Preserve auditability over convenience.

## Establish the run contract

1. Locate the FEP Agent Hub repository and read its `AGENTS.md`, root README, relevant prompt, and relevant report before changing a workflow.
2. Resolve native executables through `OPEN_CAE_CONFIG`, environment variables, or `configs/open-cae.local.toml`. Treat public paths as placeholders.
3. Choose a unique project name beneath the configured workspace. Keep FCStd, STEP, mesh, SIF, logs, VTU/PVD, images, tables, and evidence inside that project.
4. Probe all three MCP environments before modeling. Stop if a required native executable or server is unavailable.
5. Never expose arbitrary shell, Python, executable, macro, MATC, or raw SIF input. Use only fixed runners, structured parameters, and allowlisted analysis profiles.

## Select a verified profile