Hpc Elmerfem

Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver input files, mesh directories, equation and material blocks,...

Security Scan

The skill is internally coherent for building and running ElmerFEM .sif workflows — it is instruction-only, contains helpful references and a harmless SLURM run-template, and does not request unrelated credentials or installs.

Purpose & Capability

Name/description match the provided files: detailed SIF workflow guidance, debugging references, and a SLURM run template — all appropriate for an ElmerFEM helper. One small mismatch: the skill assumes ElmerSolver (and a scheduler like SLURM) will be present at runtime but does not declare required binaries; this is a minor documentation omission rather than malicious behavior.

Instruction Scope

SKILL.md confines runtime actions to reading internal reference docs and producing SIF recommendations; it does not instruct reading unrelated system files, sending data to external endpoints, or accessing secrets. The only runtime command suggested is launching ElmerSolver via srun (in references and the template), which is consistent with the stated purpose.

Install Mechanism

No install spec is present (instruction-only), so nothing is downloaded or written to disk by an installer. The included shell template is small and benign.

Credentials

The skill requests no environment variables or credentials. It implicitly expects an HPC scheduler environment (e.g., SLURM_* variables) and ElmerSolver to be available; these are normal for HPC use but are not declared in requires.binaries — consider this a documentation gap rather than an unexplained secret request.

Persistence & Privilege

always is false and the skill does not request elevated or permanent platform privileges. It is user-invocable and may be invoked autonomously per platform defaults — this is normal and not by itself a concern.

Assessment

This skill appears to do what it says: guides creation/debugging of Elmer .sif workflows and includes a benign SLURM launch template. Before using: (1) verify ElmerSolver and your scheduler (SLURM) are installed and configured—templates assume SLURM env vars and Elmer are available; (2) review the provided elmerfem-solver-slurm.sh and any generated .sif before submitting production jobs (large runs can consume cluster resources); (3) there are no hidden network endpoints or credential requests, but if you integrate this with a broader orchestration skill (e.g., hpc-orchestration), inspect that skill for any storage/transfer or credential usage. Overall low-risk and coherent, with a minor documentation omission about required binaries.

Treat ElmerFEM as a solver-input workflow centered on the .sif file plus a mesh directory.

Start

1. Read references/sif-workflow-manual.md before creating or editing a .sif.
2. Read references/block-and-equation-matrix.md when mapping simulation, body, material, equation, solver, and boundary blocks.
3. Read references/mesh-boundary-and-output.md when working with mesh directories, body IDs, boundary IDs, and result files.
4. Read references/cluster-execution-playbook.md when staging an ElmerFEM workflow for scheduler-backed cluster execution.
5. Read references/error-recovery.md when ElmerSolver parsing, coupling, or solve behavior fails.

Additional References

Load these on demand:

• references/solver-controls-and-linear-systems.md for direct versus iterative settings and nonlinear or steady tolerances
• references/transient-and-timestep-control.md for transient simulation blocks and timestep policies
• references/elmergrid-and-mesh-conversion.md for mesh conversion and ElmerGrid workflows
• references/simulation-body-solver-matrix.md for block-responsibility and ID-mapping lookup tables
• references/physics-output-matrix.md for physics-to-solver-to-output selection tables
• references/error-pattern-dictionary.md for structured parse, ID-mapping, and solver-family failure signatures
• references/cluster-execution-playbook.md for mesh-directory staging, launch style, and cluster-side continuation planning

Reusable Templates

Use assets/templates/ when a concrete .sif scaffold is needed, especially:

• heat_steady.sif
• elasticity_static.sif
• heat_transient.sif
• stokes_minimal.sif
• elmerfem-solver-slurm.sh

Guardrails

• Do not invent SIF keys outside documented Elmer syntax.
• Do not mismatch Body, Material, Equation, and Boundary Condition IDs.
• Do not reuse a solver block blindly across unrelated physics.
• Do not treat mesh boundary IDs as self-explanatory; map them explicitly.

Outputs

Summarize:

• physics family
• mesh directory assumptions
• core solver and equation blocks
• body and boundary mapping
• expected result files