hf-jobs
Skill0 starsChanged 4 months agoApache-2.0View on GitHub
Submit and manage Hugging Face Jobs, cloud GPU or CPU runs for training, fine-tuning, and batch inference. Use before any hf-jobs run, for hardware selection, cost estimates, GPU sandbox smoke tests, or when a job fails.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- garri333/Skillstheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- garri333/Skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- dataset-auditSkill
- hf-doctorSkill
- ml-autopilotSkill
- ml-internSkill
- trackioSkill
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
- Very specific: line 25
Never pass a local machine path as the job script reference.
- Distinctive: line 32
Write the script locally with Write.
- Distinctive: line 37
If you skip the GPU smoke test, state why before running the job.
- Distinctive: line 39
Every training script fails fast before expensive work:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Discipline for HF cloud compute. The hf-jobs executable is the only submission path; a PreToolUse guard prices every run and a background monitor reports state changes and failures back to you, so submitted jobs never need manual polling loops.
Authenticated namespace: !"${CLAUDE_PLUGIN_ROOT}/bin/hf-whoami" --brief
Current hardware catalog (USD per hour):
"${CLAUDE_PLUGIN_ROOT}/bin/hf-jobs" hardware 2>/dev/null || echo '{"ok": false, "error": "catalog unavailable, run hf-jobs hardware manually"}'Submission contract
hf-jobs run refuses to submit unless all of these hold, so do them in order:
--timeoutis explicit. Set it from model size, minimum 2h for any training. The 30 minute default has killed real training runs; that is why the flag is mandatory.--confirm-costmatches or exceeds the estimate for billable hardware. Get the number first:hf-jobs estimate --flavor a10g-large --timeout 4h.- The script contains no placeholder sentinels (
<username>,<model-name>, and friends). Resolve the real namespace before writing the script.
Never pass a local machine path as the job script reference. Jobs run in a fresh cloud environment where local files do not exist. Submit inline source (--inline reads stdin), a --script whose content is uploaded, or a public --url.
For a job that needs a specific container rather than a UV script, swap the source for --image <docker-image> --command "<cmd>"; the same --timeout and --confirm-cost rules still apply, and it works for immediate and scheduled runs alike.
Exact-source workflow
For any non-trivial job script:
- Write the script locally with Write.
- Validate syntax and imports.
- Smoke test the exact script: one training step plus one eval step when evaluation is part of the workflow. GPU code paths (CUDA, bf16/fp16, quantization, flash attention kernels, torch.compile, model loading) need a GPU smoke test:
hf-sandbox create --hardware t4-smallminimum, Ampere or newer (never T4) when a flash-attention kernel is involved. GPU sandboxes are billable, sohf-sandbox createrefuses billable hardware without--confirm-cost <USD>at or above the estimate, exactly likehf-jobs run; freecpu-basicneeds no confirmation. CPU sandboxes cannot test GPU paths. - Submit the exact tested source. Do not reconstruct a similar script from memory.
If you skip the GPU smoke test, state why before running the job.
Every training script fails fast before expensive work:
- print package versions for torch, transformers, trl, accelerate, datasets, trackio, and kernels when used
- assert required dataset columns exist
- assert
push_to_hub=Trueandhub_model_idis set with no placeholder - include every imported third-party package in
--dep, plus the core stack: torch, transformers, trl, accelerate, datasets, trackio, andkernels~=0.12.0when using Hub kernels
Preflight, stated before every run
- Reference implementation: [which example this is based on]
- Dataset format verified: [columns confirmed via hf-dataset-inspect]
- GPU sandbox smoke test: [hardware and result, or why not applicable]
- push_to_hub and hub_model_id: [set, no placeholders]
- timeout: [value] based on [model size] on [hardware]
- estimated cost: [from hf-jobs estimate]
- trackio: [space id, public dashboard]
Cannot fill an item: stop and complete it first.
Hardware sizing
- 1-3B params: a10g-largex2
- 7-13B params: a100-large
- 30B+ params: l40sx4 or a100x4
- 70B+ params: a100x8
a10g-small and a10g-large have the same 24GB GPU memory; the difference is CPU and RAM only.
Batches, scheduled jobs, failures
Ablations and sweeps: submit ONE job, watch the monitor confirm it reaches training, then submit the rest. Prefer one sweep script over ten manual submissions.
Scheduled jobs always require human approval; their recurring cost is unbounded. Auto permission modes refuse them by design; ask the user to approve in default mode.
On failure the monitor prints the log tail. Diagnose from hf-jobs logs <id>, fix the actual cause, and follow the OOM ladder from /ml-intern rather than shrinking the task. Cancelling: hf-jobs cancel <id>; the ledger reconciles actual cost when the terminal state lands.
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.

