jetson-diagnostic

Captures read-only Jetson health snapshots covering identity, memory, GPU, thermal, power, and services.

2|Updated Aug 20, 2026
One-click install
npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill jetson-diagnostic-atomicrajat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-diagnostic
Source: https://github.com/atomicrajat/industry_safety_monitoring_system/tree/main/.claude/skills/jetson-diagnostic
Command: npx skills add https://github.com/atomicrajat/industry_safety_monitoring_system --skill jetson-diagnostic-atomicrajat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Jetson diagnostics are scattered across tegrastats, jtop, procrank, nvpmodel, NvMap debugfs, and systemctl, each reporting a different slice of device state. This Skill replaces that guesswork with a single read-only snapshot so agents can answer identity, memory, GPU, thermal, power, and service questions from live data instead of assumptions. ## Core Features & Use Cases - All-in-one JSON snapshot: scripts/snapshot.sh emits SKU, variant, L4T version, memory, thermal zones, power mode, disk usage, top processes, GPU memory attribution, and candidate services in one structured payload. - Correct GPU memory source per driver stack: a capability probe picks nvidia-smi --query-compute-apps on the unified nvidia.ko stack (Thor) and falls back to /sys/kernel/debug/nvmap/iovmm/clients on the nvgpu stack (Orin), with gpu_source naming exactly which datum was used. - Quick human-readable summary: scripts/mem_summary.sh prints a one-line RAM/GPU/swap summary with an optional watch mode. - Use Case: A user says their Jetson feels slow and hot. The agent runs the snapshot, reports thermal zone temperatures alongside the top memory and GPU consumers, then hands off to an action skill like jetson-memory-audit or jetson-headless-mode without mutating anything itself. ## Quick Start Ask the agent to run the jetson-diagnostic snapshot script and summarize this Jetson's SKU, memory, thermal, and top processes.

Frequently Asked Questions about jetson-diagnostic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a full health snapshot of a Jetson device?

Run scripts/snapshot.sh on the Jetson host to emit one JSON payload with SKU, variant, L4T version, memory, thermal zones, power mode, disk usage, top processes, and GPU memory attribution. Use the --human flag for pretty-printed output.

How do I check GPU memory usage per process on Jetson Orin?

On Orin the nvgpu driver makes nvidia-smi a stub, so the authoritative source is /sys/kernel/debug/nvmap/iovmm/clients, which usually requires root. The snapshot script detects this automatically and reports per-process sizes under nvmap.top_clients with gpu_source set to nvmap:iovmm-clients.

Does this skill work on both Jetson Thor and Orin?

Yes. A capability probe checks whether nvidia-smi returns real data; Thor uses nvidia-smi compute-apps for per-process GPU memory while Orin falls back to NvMap debugfs. Variant detection covers thor-t5000, thor-t4000, and all Orin AGX, NX, and Nano memory configurations.

Why does the snapshot show gpu_source as none or missing NvMap data?

NvMap debugfs under /sys/kernel/debug requires root, so unprivileged runs report gpu_source as none and empty nvmap fields. Rerun with sudo to populate per-process GPU memory, or run on the Jetson host if the sandbox lacks host visibility.

Can this skill change power modes or stop services to free memory?

No, the skill is strictly read-only and never runs nvpmodel changes, jetson_clocks, drop_caches, or systemctl stop. It reports observed state and hands off to action skills such as jetson-headless-mode or jetson-memory-audit for any mutation.