agentleFS
NVIDIAKnown publisherNVIDIA/dgx-spark-playbooks/nvidia/station-ai-skills/assets/skills/dgx-station-diagnose/SKILL.md

dgx-station-diagnose

Skill1.5k starsChanged 2 months agoApache-2.0View on GitHub

Run and interpret the complete read-only dgx-assist diagnostic suite for NVIDIA DGX Station GB300, correlate findings with pinned NVIDIA playbooks, export a redacted support bundle, and apply one separately approved allowlisted fix. Use when the user reports a Station, CUDA, GPU health, coherency, vsloshd, Docker, CDI, MIG, cache, port, or owned inference-service failure.

Trending

More talk lately.about the whole repository

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

Who's talking about NVIDIA/dgx-spark-playbooks

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Search the pinned playbooks for each high or critical finding.

    line 14
  2. Distinctive:

    If no passage overlaps, say so and avoid inventing a platform fix.

    line 15
  3. Distinctive:

    Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a …

    line 25
  4. Very specific:

    Never stop a service without current dgx-assist ownership evidence.

    line 26
  5. Distinctive:

    Never use Fabric Manager as a routine Station check or remediation.

    line 27
  6. Distinctive:

    Never reveal secrets or unredacted home paths in a bundle.

    line 29
  7. Distinctive:

    Do not execute an unregistered remediation.

    line 30
  8. Very specific:

    Treat --yes only as approval already obtained.

    line 31
  9. Distinctive:

    Read references/findings.md before proposing a fix or support bundle.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

DGX Station diagnostics

Diagnose first. Do not mutate as part of diagnosis.

Workflow

  1. Run scripts/dgx-assist diagnose run --json.
  2. Report the detected compatibility profile, then findings in severity order with their stable IDs and evidence. Preserve unknown states. On Software 1.0, do not reinterpret intentionally skipped Software 2.0 service checks as faults.
  3. Search the pinned playbooks for each high or critical finding; cite the relevant URL, heading, lines, and commit.
  4. If no passage overlaps, say so and avoid inventing a platform fix.
  5. Offer diagnose bundle --report-id "<id>" when escalation is appropriate.
  6. Offer at most one automatic fix at a time, and only when fix_id is present.
  7. Preview with diagnose fix --report-id "<id>" --finding "<id>" --dry-run.
  8. Explain exact actions, impact, privilege, and reboot state. Obtain explicit approval.
  9. Repeat with --yes only after approval and report the action receipt.

Safety requirements

  • Keep diagnose run read-only.
  • Never install packages, rewrite Docker configuration, change power caps or driver parameters, kill workloads, or modify MIG through a diagnostic fix.
  • Never stop a service without current dgx-assist ownership evidence.
  • Never use Fabric Manager as a routine Station check or remediation.
  • Re-run diagnostics when finding evidence is stale.
  • Never reveal secrets or unredacted home paths in a bundle.
  • Do not execute an unregistered remediation.
  • Treat --yes only as approval already obtained.

Read references/findings.md before proposing a fix or support bundle. Read references/bringup.md when the problem concerns physical deployment, BMC or firmware verification, driver bring-up, power braking, or support escalation.

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.