finetune-model
Skill1.5k starsChanged 10 days agoBSD-3-ClauseView on GitHub
Use when checking whether one DeepOps Slurm GPU node is prepared for fine-tuning, diagnosing missing cached training inputs or container prerequisites, or distinguishing readiness from actual training success.
Trending
Quiet since June.about the whole repository
Who's talking about NVIDIA/deepops
- kubeflow/kubeflow“Add support to display different GPU types, specifically NVIDIA Multi-Instance GPUs”GitHub · Oct 8, 2020 · 6 reactions
- kubeflow/website“Really need a Kubeflow Ecosystem Section to the Website, (Note list is attached I found who are in the …”GitHub · Jun 28, 2020 · 4 reactions
- PyTorchKR/landscape“[Add] NVIDIA DeepOps (NVIDIA/deepops)”GitHub · Jun 6, 2026
- glotzerlab/hoomd-blue“Allow dynamic loading of slurm_conf on Anvil.”GitHub · Jul 19, 2024
- hashicorp/vagrant“Error with provider libvirt”GitHub · Mar 24, 2024
The biggest 5 of 24 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 24
Talked about on GitHub (24 times).
On GitHub · 24
- Oct 8, 2020Add support to display different GPU types, specifically NVIDIA Multi-Instance GPUs — kubeflow/kubeflow6 reactions · 13 comments
- Jun 28, 2020Really need a Kubeflow Ecosystem Section to the Website, (Note list is attached I found who are in the Ecosystem) — kubeflow/website4 reactions · 11 comments
- Jun 6, 2026[Add] NVIDIA DeepOps (NVIDIA/deepops) — PyTorchKR/landscape0 reactions
- Jul 19, 2024Allow dynamic loading of slurm_conf on Anvil. — glotzerlab/hoomd-blue0 reactions
- Mar 24, 2024Error with provider libvirt — hashicorp/vagrant0 reactions · 1 comment
19 more on GitHub
- Aug 13, 2023Set HPA(Horizontal Pod Autoscaler) of Triton Inference Server with Prometheus metric — MrSyee/SAM-remove-background0 reactions
- Apr 4, 2023Configuration issues with containerd failing Kubespray install with "unknown service runtime.v1alpha2.ImageService" error — kubernetes-sigs/kubespray0 reactions · 6 comments
- Nov 10, 2022Prometheus metric gpu_capacity is not found. — NTHU-LSALAB/KubeShare0 reactions · 4 comments
- Feb 26, 2022SLURM gpus-per-task issue — NVIDIA/pyxis0 reactions · 5 comments
- Sep 5, 2021feature(GPU): kubespray install NVIDIA GPU — k8sli/kubeplay0 reactions · 1 comment
- Aug 12, 2021Ensure systemd unit reloaded when restarting — NVIDIA/ansible-role-nvidia-docker0 reactions
- May 18, 2021Super huge log messages from journald - misconfigured filter_concat? — kokuwaio/helm-charts0 reactions · 2 comments
- Mar 22, 2021Add var to allow skipping reload of Docker daemon — NVIDIA/ansible-role-nvidia-docker0 reactions
- Dec 18, 2020Multiple Pods stucks in CrashLoopBackOff — kubeflow/kubeflow0 reactions · 9 comments
- Oct 19, 2020Update PPA URL — DeepOps/ansible-maas0 reactions
- Oct 7, 2020enroot-nsenter: failed to create user namespace: Invalid argument — NVIDIA/enroot0 reactions · 2 comments
- Aug 20, 2020Istio Dex Manifest v1.0.2 is "Unable to fetch Nodes", centraldashboard throwing 504 — kubeflow/community-distribution0 reactions · 2 comments
- Jul 16, 2020Multi-GPU workloads hang in Jupyter Notebooks launched through Kubeflow — kubeflow/kubeflow0 reactions · 3 comments
- Jun 16, 2020update_ood_portal may not work on Ubuntu — OSC/ood-ansible0 reactions · 1 comment
- May 18, 2020details = "failed to connect to all addresses" in "helm" module — ansible/ansible0 reactions · 8 comments
- Jan 22, 2020Failed to fetch https://s3-eu-west-1.amazonaws.com/coreos-charts/stable/index.yaml : 403 Forbidden — prometheus-operator/kube-prometheus0 reactions · 4 comments
- Sep 14, 2019ambassador always CrashLoopBackOff — kubeflow/kubeflow0 reactions · 8 comments
- Aug 9, 2019"Copy kubectl binary to ansible host" sometimes fails with memory error due to known issue with 'fetch' module. — kubernetes-sigs/kubespray0 reactions · 8 comments
- Nov 13, 2018Tiller init command failing on primary master — kubernetes-sigs/kubespray0 reactions
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- deploy-airgappedSkill
- deploy-k8s-gpu-clusterSkill
- deploy-runai-kaiSkill
- deploy-slurm-clusterSkill
- diagnose-driver-installSkill
- manage-model-cacheSkill
- model-workflowsSkill
- provision-with-maasSkill
- serve-modelSkill
- validate-gpu-clusterSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the readiness guide. Run from the repository root as the intended model consumer on the selected compute host, not the login node.
- Distinctive: line 16
Run from the repository root as the intended model consumer on the selected compute host, not the login node.
- Very specific: line 22
Follow manage-model-cache for an approved shared cache, immutable revision and complete reviewed required-file list.
- Distinctive: line 60
Keep credentials private, mount shared inputs read-only in any future reviewed recipe, and keep outputs/checkpoints outside the input cache.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Check fine-tuning readiness
This skill checks preparation only. It provides no training recipe. A
ready result always has training_validated: false. Multi-node training is
unsupported here; do not invent a distributed command or report a successful
fine-tune from this check.
Preconditions
- Read the readiness guide. Run from the repository root as the intended model consumer on the selected compute host, not the login node. The validator checks local host identity against the scheduler record; do not bypass a mismatch.
- Obtain authorization for the target and read-only scheduler queries. Specify one node and one partition. An IDLE node with an unallocated GPU is required; this conservative check does not accept mixed, draining or flagged nodes.
- Follow manage-model-cache for an approved
shared cache, immutable revision and complete reviewed required-file list.
Supported inputs are Hugging Face
tokenizer.jsonplus safetensors weights; list every extra model-specific asset. Indexed weights require every shard. - Select a site-reviewed fine-tuning image pinned by digest, using Pyxis syntax
registry#repository@sha256:<digest>. Do not use mutable tags, credentials in the reference, or substitute an unreviewed image to get a pass.
Readiness check
Set the variables to reviewed values. For sharded weights, replace the final
file argument with model.safetensors.index.json; the validator follows its
weight map. Add every additional file needed by the selected model.
python3 scripts/validation/validate_finetune.py --json \
--node "$NODE" --partition "$PARTITION" \
--container-image "$TRAINING_IMAGE" \
--cache-dir "$HF_HUB_CACHE" --repo-id "$MODEL_REPO" --revision "$MODEL_REVISION" \
--require-file config.json --require-file tokenizer.json \
--require-file tokenizer_config.json --require-file model.safetensors| Result | Next action |
Exit 0, status: ready, ok: true | Report readiness only, including that container execution and training remain unproven. |
Exit 1, status: not_ready | Report every errors[] stage. Repair the named prerequisite through its approved procedure; do not drain nodes, install software or download models implicitly. |
Exit 2, status: bad_input | Correct explicit inputs or unsupported flags using --help. No scheduler commands run for bad input. |
Optional one-GPU probe
Off by default. Only with explicit authorization to allocate a GPU and run the
reviewed image, repeat the command with --gpu-smoke. This can download the
container image and submits one bounded, single-node, single-GPU nvidia-smi
job after all readiness gates pass. It does not load the model or train.
gpu_smoke_ok: true proves only the container GPU probe, not cache access
inside the container, framework compatibility, learning or checkpoint recovery.
Keep credentials private, mount shared inputs read-only in any future reviewed recipe, and keep outputs/checkpoints outside the input cache. A readable cache, a pinned image string, and a GPU probe cannot certify a training outcome.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

