CD exec-remote-slurm
Remote SLURM cluster development via SSH. Use when running jobs, profiling, or developing on a remote SLURM cluster with pyxis/enroot containers. Covers SSH connection management, srun/sbatch/salloc job patterns, tmux-based allocation persistence, file transfer, and safe remote file access. Works with any SLURM cluster accessible via SSH.
Promises remote SLURM cluster development over SSH: connection management, srun/sbatch/salloc job patterns, tmux session persistence, and pyxis/enroot container support. Two modules and one script in the repo, but broken references exist—some links point nowhere. Code quality scores 73/100, process execution 47/100, which means instructions are incomplete or vague. No model runs conducted. No critical issues, minor findings present.
For those already familiar with SLURM and remote clusters, it can cut boilerplate time. Beginners will hit walls. Install if you're prepared to fill gaps yourself and verify documentation links.
Remote SLURM cluster development via SSH.
As a process D 47/100 · Unfinished process — References files that are not bundled: references/<cluster>.md, scripts/build.slurm
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9297 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/<cluster>.md - warning
missing-refreference to a missing file: scripts/build.slurm - note
edit-residuethe text marks something as outdated (lines 376): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 47/100
- 0Tools and files. 2 referenced file(s) missing: references/<cluster>.md, scripts/build.slurm
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 9297 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Steps. 39 steps
- 100Failures and branches. 8 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (66 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 340: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (50 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.