AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Hpc Elmerfem

skill-scimate-ai-hpc-skills-hpc-elmerfem · by SciMate-AI

Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver input files, mesh directories, equation and material blocks, multiphysics coupling, boundary conditions, transient controls, or ElmerSolver execution and output issues.

↗ Repository
— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-scimate-ai-hpc-skills-hpc-elmerfem

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-scimate-ai-hpc-skills-hpc-elmerfem)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Hpc Elmerfem? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

HPC ElmerFEM

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills