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.
SkillScore91Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/12/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill91%
Checks it passed that the model alone missed
Attempts lsb_release -ds first
Outputs a clear message stating the target is not running on a Jetson
Formats nvpmodel power mode output into a single line joined with ' / '
and 10 more in the full report
9 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+10%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/12/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
When formatting a text report for Jetson target hardware snapshotting, what exact key names should prefix each line of output?
What was checked, without and with the skill
Checked
Without skill
With skill
Uses field label prefixes Model:, L4T release:, Power mode:, Kernel:, Uptime:, and OS version:
Missed
Passed
case-14 · gemini-3.6-flash · 8/12/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md119 linessingle file
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.
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):