agentleFS
NVIDIAKnown publisherNVIDIA/deepops/skills/finetune-model/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the NVIDIA/deepops repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about NVIDIA/deepops

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

19 more on GitHub

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
  1. Distinctive:

    Read the readiness guide. Run from the repository root as the intended model consumer on the selected compute host, not the login node.

    line 15
  2. Distinctive:

    Run from the repository root as the intended model consumer on the selected compute host, not the login node.

    line 16
  3. Very specific:

    Follow manage-model-cache for an approved shared cache, immutable revision and complete reviewed required-file list.

    line 22
  4. Distinctive:

    Keep credentials private, mount shared inputs read-only in any future reviewed recipe, and keep outputs/checkpoints outside the input cache.

    line 60

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json plus 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
ResultNext action
Exit 0, status: ready, ok: trueReport readiness only, including that container execution and training remain unproven.
Exit 1, status: not_readyReport 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_inputCorrect 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.