agentleFS
letscooktech-studioletscooktech-studio/outcomelab/skills/nvidia-accelerated-ai-systems-operator/SKILL.md

nvidia-accelerated-ai-systems-operator

Skill7 starsChanged 6 days agoMITView on GitHub

Safely plan, review, and operate NVIDIA-oriented or GPU-accelerated AI skill workflows covering AI-Q, cuOpt, DALI, Dynamo, NemoClaw, Omniverse, USD optimization, physical AI infrastructure, neural reconstruction, simulation-ready assets, and accelerated AI deployment. Use when adapting NVIDIA Agent Skills-style packs into OutcomeLab workflows or reviewing GPU/accelerated AI systems for setup, deployment, validation, scaling, security, cost, and production readiness.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    Create a validation plan: smoke test, health check, sample workload, performance baseline, logs, telemetry, rollback, and failure criteria.

    line 20
  2. Distinctive:

    Do not invent NVIDIA product commands, package names, endpoints, or compatibility claims.

    line 30
  3. Distinctive:

    Never expose private certs, service URLs, tokens, or cloud credentials.

    line 32
  4. Very specific:

    Do not run install/deploy/stop commands without explicit authorization.

    line 33

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

NVIDIA Accelerated AI Systems Operator

Developed by the LetsCookTech Open Source Team.

Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.

Operate GPU and NVIDIA-oriented AI workflows as production systems. This is an OutcomeLab adapter layer: it does not replace official vendor documentation or upstream skills. It adds classification, safety, validation, cost, security, and production-readiness review around accelerated AI tasks.

Workflow

  1. Classify the task domain: AI-Q deployment/research, cuOpt optimization, DALI data pipelines, Dynamo serving/routing/interconnect, NemoClaw sandboxing, Omniverse/USD workflows, physical AI infrastructure, neural reconstruction, or simulation asset pipelines.
  2. Identify required hardware, drivers, CUDA/runtime versions, containers, credentials, endpoints, environment variables, storage, network, and licensing constraints.
  3. Select the operating path: install, configure, run, validate, troubleshoot, scale, benchmark, secure, or decommission.
  4. Inspect safety boundaries: secrets, certificates, service URLs, cloud credentials, GPU access, production data, destructive commands, external network calls, and cost exposure.
  5. Create a validation plan: smoke test, health check, sample workload, performance baseline, logs, telemetry, rollback, and failure criteria.
  6. Review production risks: GPU capacity, interconnect, scheduling, data movement, storage bandwidth, version drift, observability, incident recovery, and vendor lock-in.
  7. Produce an evidence-backed plan or audit with exact commands only when authorization and environment details are supplied.

Output contract

Return task classification, required inputs, missing artifacts, selected workflow path, safety checklist, setup/review plan, validation checks, performance and cost risks, security risks, rollback plan, confidence level, and review gaps.

Quality gates

  • Do not invent NVIDIA product commands, package names, endpoints, or compatibility claims.
  • Require official docs, supplied files, or inspected scripts for version-specific steps.
  • Never expose private certs, service URLs, tokens, or cloud credentials.
  • Do not run install/deploy/stop commands without explicit authorization.
  • Mark output incomplete when hardware, driver, runtime, or endpoint evidence is missing.

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.