Hpc Elmerfem
v0.1.0Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver input files, mesh directories, equation and material blocks,...
⭐ 0· 82·0 current·0 all-time
byfzj@fzj1214
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & 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.Like a lobster shell, security has layers — review code before you run it.
latestvk9769drsw2ek8bn92a50w36w7d839xf9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.