jetson-print-device-info
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.
Install / Use
npx skills add NVIDIA/skills --skill jetson-print-device-infoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of jetson-print-device-info
jetson-print-device-info scores 89/100 on our quality scale, 829th of 3,356 Development & Engineering skills we index (top 25%).
Its SKILL.md is 5.1 KB long, well organised into 12 sections with 3 code examples: a solid amount of guidance for an agent.
With 3,421 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 5 days ago, so jetson-print-device-info is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
jetson-print-device-info compared with similar skills
All 4 of these similar skills score higher than jetson-print-device-info; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| jetson-print-device-info (this skill)by NVIDIA | 89 | 3.4k | 5d ago | SKILL.md |
| ai-job-searchby MadsLorentzen | 100 | 44.4k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.7k | 2d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 6d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install jetson-print-device-info?
- Run
npx skills add NVIDIA/skills --skill jetson-print-device-info. The install tabs above show the steps for each supported agent. - Which AI agents does jetson-print-device-info work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is jetson-print-device-info safe to use?
- It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is jetson-print-device-info still maintained?
- The repository was last updated 5 days ago, so jetson-print-device-info is actively maintained.
Skill content
View source on GitHubname: 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). nvpmodelavailable 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.
- Capture the module model and validate it is a Jetson target — exit early otherwise:
# 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" - Extract the L4T release header line — skip the rest of the file (long list of library SHAs):
head -1 /etc/nv_tegra_release 2>/dev/null || echo "L4T release info not found" # Equivalent: grep -m1 '^# R' /etc/nv_tegra_release - Run
nvpmodel -qand join its two output lines (NV Power Mode: <name>and the mode number) onto one line.paste -sdonly uses the first char of its delimiter, so useawkto insert the literal/separator:nvpmodel -q 2>/dev/null | awk 'NR==1{a=$0; next} {print a" / "$0}' \ || echo "nvpmodel not available" - Print the kernel version and uptime:
uname -r uptime -p - Print the OS version (prefer
lsb_release, fall back to/etc/os-release):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:
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):
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):
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.
nvpmodeloutput format varies between L4T versions; the skill prints it verbatim rather than parsing.
Troubleshooting
-
Error:
/proc/device-tree/model: No such file or directoryCause: 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 foundCause: L4T BSP not installed, or running in a minimal container withoutnvpmodel. 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/modelwill not contain a Jetson model string — detect that and exit with a clear message rather than printing misleading info.
Related Skills
ai-job-search
44.4kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
