Skip to main content
skill CX Codex

jetson-print-device-info — Claude Code skill: how it works

Gathers baseline hardware and OS details from a running NVIDIA Jetson board before performance or regression testing.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add NVIDIA/skills --skill jetson-print-device-info -a claude-code
Open on GitHub

What jetson-print-device-info does

The skill performs read-only checks directly on the Jetson target rather than a host workstation. It inspects /proc/device-tree/model to verify the hardware and exits immediately if the device string does not contain "Jetson". This baseline captures the software stack and power state before running performance runs.

Under the hood, it queries standard tools like uname, uptime, and /etc/nv_tegra_release, along with nvpmodel -q for power mode data. If nvpmodel is missing inside a container, the script prints a fallback label without breaking the report. The skill does not monitor thermal sensors, clock rates, or per-rail power consumption.

What it helps with

  • capture a software and power baseline before performance tests
  • verify L4T release details on a freshly flashed device
  • check active nvpmodel power modes on Jetson hardware
  • inspect kernel version and uptime via agent commands

Example prompts for the agent

  • Inspect this Jetson board and report its model, L4T release, and power mode.
  • Capture the system baseline before we start regression benchmarks.
  • Check the current OS version and nvpmodel setting on the target.

How to install jetson-print-device-info

1Skills CLI (Vercel)

npx skills add NVIDIA/skills --skill jetson-print-device-info -a claude-code

2Manually: put the files in place

~/.claude/skills/jetson-print-device-info/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/jetson-print-device-info/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about jetson-print-device-info

How to install jetson-print-device-info in Claude Code?

Run npx skills add NVIDIA/skills --skill jetson-print-device-info -a claude-code in your terminal.

What does jetson-print-device-info do?

It prints a concise summary of a Jetson device, covering module model, L4T release, kernel, uptime, OS version, and active power mode.

Can you run jetson-print-device-info on a host PC?

No, it must run directly on the Jetson target. If run on a host PC, the check for /proc/device-tree/model fails and halts execution.

Source text

SKILL.md · Apache-2.0
---
name: jetson-print-device-info
description: Use when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target. This is an example skill.
version: 0.0.1
license: "Apache-2.0"
metadata:
  author: "Jetson Team"
  tags: [jetson, device, info]
  languages: [bash]
  data-classification: public
---

# jetson-print-device-info

Prints a concise summary of the Jetson device this skill runs on.

This skill is intended as a reference example for the `jetson-device-skills` repo and the NVIDIA-wide skills CI. It runs on the Jetson target (not the host PC) and performs read-only inspection — useful as a baseline capture before running performance tests.

## Purpose

Capture a baseline snapshot of a Jetson target's software stack and power mode before running performance, regression, or compatibility tests.

## When to use

- Starting a performance run and you want a captured baseline of the device's software stack and power mode.
- Verifying that a freshly flashed Jetson matches an expected L4T / JetPack version.

## Prerequisites

- Running on a Jetson target (not the host PC).
- Standard CLIs available: `tr`, `cat`, `uname`, `uptime`, `lsb_release` (or `/etc/os-release`).
- `nvpmodel` available for power mode (optional — skill falls back gracefully).

## Inputs

None. The skill reads only from the local Jetson filesystem and standard CLIs.

## Instructions

Run each step in order and print the captured values into the report shown under [Output format](#output-format).

1. **Capture** the module model and **validate** it is a Jetson target — exit early otherwise:
   ```bash
   # Device-tree strings are null-terminated, so strip NULs before printing.
   model=$(tr -d '\0' < /proc/device-tree/model 2>/dev/null)
   case "$model" in
     *Jetson*) ;;
     *) echo "Not running on a Jetson target (model: '${model:-unknown}')"; exit 1 ;;
   esac
   echo "$model"
   ```
2. **Extract** the L4T release header line — skip the rest of the file (long list of library SHAs):
   ```bash
   head -1 /etc/nv_tegra_release 2>/dev/null || echo "L4T release info not found"
   # Equivalent: grep -m1 '^# R' /etc/nv_tegra_release
   ```
3. **Run** `nvpmodel -q` and **join** its two output lines (`NV Power Mode: <name>` and the mode number) onto one line. `paste -sd` only uses the first char of its delimiter, so use `awk` to insert the literal ` / ` separator:
   ```bash
   nvpmodel -q 2>/dev/null | awk 'NR==1{a=$0; next} {print a" / "$0}' \
     || echo "nvpmodel not available"
   ```
4. **Print** the kernel version and uptime:
   ```bash
   uname -r
   uptime -p
   ```
5. **Print** the OS version (prefer `lsb_release`, fall back to `/etc/os-release`):
   ```bash
   lsb_release -ds 2>/dev/null || (. /etc/os-release && echo "$PRETTY_NAME") || echo "OS version not found"
   ```

## Output format

Print a short report with these sections, one line each where possible:

```text
Model:           <device-tree model string>
L4T release:     <release header line>
Power mode:      <nvpmodel name> / <mode number>
Kernel:          <uname -r>
Uptime:          <uptime -p>
OS version:      <lsb_release / /etc/os-release output>
```

## Examples

Example output on an Orin AGX dev kit (L4T R36 / Ubuntu 22.04):

```text
Model:           NVIDIA Jetson AGX Orin Developer Kit
L4T release:     # R36 (release), REVISION: 3.0
Power mode:      NV Power Mode: MAXN / 0
Kernel:          5.15.136-tegra
Uptime:          up 2 hours, 14 minutes
OS version:      Ubuntu 22.04.4 LTS
```

Example output on an AGX Thor (L4T R39 / Ubuntu 24.04):

```text
Model:           NVIDIA Jetson AGX Thor Developer Kit
L4T release:     # R39 (release), REVISION: 0.0
Power mode:      NV Power Mode: 120W / 1
Kernel:          6.8.0-tegra
Uptime:          up 12 minutes
OS version:      Ubuntu 24.04 LTS
```

## Error handling

Each command falls back to a clearly labeled `"... not found"` / `"... not available"` string if the underlying file or binary is missing — the skill never errors out mid-report. If `/proc/device-tree/model` is missing or does not contain a Jetson string, exit early with a clear "not running on a Jetson target" message.

## Limitations

- Read-only inspection only — does not detect GPU/CPU clocks, thermal state, or per-rail power.
- `nvpmodel` output format varies between L4T versions; the skill prints it verbatim rather than parsing.

## Troubleshooting

- **Error:** `/proc/device-tree/model: No such file or directory`
  **Cause:** Running on a host PC, not a Jetson target.
  **Solution:** Run the skill on the Jetson device directly (e.g. via SSH).

- **Error:** `nvpmodel: command not found`
  **Cause:** L4T BSP not installed, or running in a minimal container without `nvpmodel`.
  **Solution:** Expected on non-Jetson or stripped environments — the skill prints `"nvpmodel not available"` and continues.

## Notes

- Read-only. Do not change power mode, install packages, or modify any files.
- If the skill is invoked on a host PC by mistake, `/proc/device-tree/model` will not contain a Jetson model string — detect that and exit with a clear message rather than printing misleading info.

© Jetson Team · Apache-2.0 · NVIDIA/skills

Similar skills

Everything for DevOps and infrastructure →

From the same set178

jetson-download-bsp This skill downloads NVIDIA Jetson Linux BSP artifacts into your workspace: the BSP image, sample rootfs, public_sources, x-tools and guides. It runs during Auto Setup. CX Codex +1 1,100installs jetson-customize-usb Configures USB2 and USB3 SS ports on Jetson Orin and Thor boards via kernel DT overlays. Keeps host xHCI controller probes from failing when toggling ports. CX Codex +1 1,100installs jetson-customize-fan Edits nvfancontrol fan profiles for Jetson and Tegra targets, including curves and boot defaults. Use it when tuning cooling on Orin or Thor. CX Codex +1 1,100installs jetson-flash-image This skill flashes a promoted BSP image onto a Jetson board in recovery mode. Use it after building a custom image. CX Codex +1 1,100installs jetson-customize-nvpmodel Edits nvpmodel power profiles on Jetson/Tegra, including frequency caps, profile changes, and the mode selected at boot. CX Codex +1 1,100installs jetson-build-source Rebuilds kernel, DTBs and OOT modules from changes under bsp_sources/, then writes the manifest deploy reads. CX Codex +1 1,100installs jetson-customize-camera Enables MIPI and GMSL camera sensors on Jetson Thor or Orin custom carriers via kernel device tree overlays. Useful when v4l2-ctl shows no capture channels after boot. CX Codex +1 1,100installs cuopt-numerical-optimization-api A skill for NVIDIA cuOpt: it walks the agent through modeling LP, MILP and QP problems and picking the right interface — Python, C or CLI. CX Codex +1 1,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor