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

serve-model

Skill1.5k starsChanged 10 days agoBSD-3-ClauseView on GitHub

Use when serving a cached model on one GPU with vLLM, checking a local completion endpoint, or diagnosing startup and inference failures in the single-node quickstart.

1 other project uses a version of this.

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.

Most recently taken up by

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run from the repository root on the allocated serving node.

    line 8
  2. Very specific:

    Keep the whole Hub cache read-only, including blobs.

    line 25
  3. Very specific:

    Follow quickstart steps 1–2.

    line 30
  4. Distinctive:

    Use quickstart step 3 unchanged for the public example: local snapshot and tokenizer, offline loading, one GPU, foreground process, …

    line 33
  5. Distinctive:

    Wait for startup; use another shell in the same allocation and namespace to validate.

    line 37
  6. Distinctive:

    Stop only your own foreground server with Ctrl-C.

    line 55

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

Serve a model on one node

Run from the repository root on the allocated serving node. Read the vLLM quickstart for the exact installation and foreground launch commands. This skill does not allocate a GPU or authorize a workload.

Preconditions

  • Confirm permission for the node, one isolated GPU, package installation, server startup and the validator's inference request. Record the allocation and the process you own. Never use a login shell outside that allocation or override scheduler device isolation.
  • Confirm model license, immutable revision, complete file list, reader identity, cache mount and served alias. Use manage-model-cache for missing files; do not make consumers download them.
  • Require Python 3.12 and a fresh private serving environment using examples/vllm/requirements.txt. Check wheel/driver compatibility against the quickstart; do not change drivers or the cache writer's environment.
  • Keep the whole Hub cache read-only, including blobs. Keep authentication, HF_HOME, Xet and framework caches private. Pause snapshot writes during use.

Procedure and success gate

  1. Follow quickstart steps 1–2. Require cache validator exit 0 and ok: true as the actual reader before startup. Config alone is not a complete model; name every required weight shard and tokenizer file.
  2. Use quickstart step 3 unchanged for the public example: local snapshot and tokenizer, offline loading, one GPU, foreground process, loopback only. Never enable remote model code. HF_HUB_OFFLINE=1 is not a firewall and belongs only on the loading process, not globally on clients.
  3. Wait for startup; use another shell in the same allocation and namespace to validate. This submits inference, not just a read-only health check:
python3 scripts/validation/validate_vllm.py --json \
  --base-url http://127.0.0.1:8000 --model deepops-gpt2 \
  --cache-dir /shared/hf-cache/hub \
  --repo-id openai-community/gpt2 \
  --revision 607a30d783dfa663caf39e06633721c8d4cfcd7e \
  --require-file config.json --require-file tokenizer.json --require-file model.safetensors
  1. Require exit 0 and ok: true. Schema version 1 checks cache, health, advertised model and bounded completion in order. Exit 1 fails validation; exit 2 is a command syntax error without guaranteed JSON. A false check can mean skipped; inspect the first error stage. Preserve the invocation, package versions and private startup log. Success does not prove loaded revision, GPU use, quality or throughput; an alias alone is not revision attestation.
  2. Stop only your own foreground server with Ctrl-C. Confirm exit before releasing the allocation. Do not kill another listener or prune the shared cache.

Stop and recovery

ObservationAction
Missing files or unreadable cacheStop; designated writer repairs the pinned snapshot, then reader revalidates. Never loosen permissions globally.
Full cacheStop downloads; request operator-reviewed retention, not automatic deletion.
Port occupied or endpoint ownership unclearStop; identify the owner. Do not validate or kill it without permission.
Startup/health failureInspect private logs for compatibility, memory and files; rerun validation only after startup is confirmed.
Authentication required / HTTP 401Stop; use the site's approved authenticated workflow. Never disable controls for this example.
Model/completion failureCompare alias, full file list and server log. Health alone is not success.
Multi-node, remote access or production service requestedStop; unsupported here. Do not widen the bind address or improvise distributed flags.

Offline fixtures test the validator, not real cache reuse, GPU inference or agent decision-making. Those require separate verification.

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.