Jetson Device Info Snapshot
Capture a concise software, kernel, OS, and power-mode baseline from a running Jetson target.
The skill explicitly limits itself to local, read-only inspection of device-tree and version data plus standard CLIs; it does not access the network, change power settings, install packages, or modify files, and classifies the data as public. No clear overreach or red-line risk is present. Deducted 3 points because execution confirmation, runtime privilege boundaries, output-data protection, and rollback discussion are not explicit, even though the actions are read-only.
The ordered workflow, prerequisites, commands, and most missing-input fallbacks are clear, with a stable set of output fields. Static review cannot reproduce execution, and the nvpmodel pipeline may still exit successfully through awk, preventing the intended not-available fallback; output variation is also only printed verbatim. Deducted 3 points for an unverified failure-path defect and limited abnormal-input diagnostics.
Audience, Jetson-local environment, intended scenarios, and the non-Jetson host case are clearly stated, giving the trigger good semantic precision. R36/R39 examples and minimal-environment fallbacks improve fit. Deducted 5 points because there is no Chinese-language output or usage guidance, and container, SSH, and model-variation boundaries are only lightly covered.
SKILL.md provides structured metadata, version, license, prerequisites, inputs, outputs, examples, error handling, limitations, and troubleshooting; the skill card adds ownership and use-case information, while repository files provide licensing and publication/sync context. Deducted 6 points for version 0.0.1 without a changelog, nonspecific maintenance responsibility and update commitments, a low-level author-format finding, and an explicit demonstration-only positioning.
The core task is a six-field device baseline report with concrete labels, format, and examples, and the result should require only light review. The benchmark report records relevant task outcomes, but its source dataset is unavailable and static review cannot confirm actual execution. Deducted 1 point because the snippets do not fully show the final labeled-report assembly and the nvpmodel missing-command path may reduce completeness.
The source includes auditable commands, expected outputs, four evaluation tasks, and a reported evaluation summary, providing limited traceability. However, the evaluation dataset is unavailable and there is no committed test suite or independent reproduction record for this skill. Deducted 1 point because the evidence is mainly repository documentation and an opaque summary, with limited coverage.
- Run only on the Jetson target; the device-tree model and nvpmodel may be absent on a host PC or minimal container.
- Fix missing-command detection in the nvpmodel pipeline and add tests for final report assembly; the evaluation report does not expose a reproducible dataset.
- The skill is explicitly described as a demonstration and should not be treated as a production-grade or comprehensive hardware-health diagnostic.
- The output includes model, software-version, and uptime information; despite being classified as public, handle it according to organizational asset-information policy.
What does this skill do, and when should you use it?
Jetson Device Info Snapshot is a version 0.0.1 read-only Bash skill for producing a compact report from a live Jetson device. It reads the device-tree model, L4T release header, kernel version, uptime, and operating-system version, and queries the current power mode. It validates that execution is on a Jetson before collecting the report, while missing optional tools receive labeled fallbacks. The skill is best suited to baseline capture before performance, regression, or compatibility testing.
Reads and validates /proc/device-tree/model; reads the first line of /etc/nv_tegra_release; runs nvpmodel -q and joins its two output lines; runs uname -r and uptime -p; prefers lsb_release -ds and falls back to /etc/os-release; then prints a six-field report containing Model, L4T release, Power mode, Kernel, Uptime, and OS version.
- A Jetson performance engineer captures the device software stack and power mode before a benchmark run.
- A device-validation engineer checks whether a freshly flashed Jetson matches an expected L4T or JetPack version.
- A compatibility tester records model, kernel, OS, and power-mode details alongside test results.
- An operator managing Jetson devices over SSH needs a quick target-side baseline snapshot.
What are this skill's strengths and limitations?
- Read-only inspection does not change power mode, files, or installed packages.
- Captures key baseline fields covering hardware identity, L4T, kernel, uptime, OS, and power mode.
- Missing nvpmodel or release utilities receive clear fallback messages.
- The repository supplies an installation, synchronization, signing, and verification workflow.
- Full use requires a running Jetson target; execution on a host PC exits early.
- It does not inspect GPU/CPU clocks, thermal state, or per-rail power.
- nvpmodel output varies across L4T versions and is printed verbatim rather than parsed.
- The supplied material provides no test suite, platform coverage, or execution-validation record.
How do you install this skill?
Install the specific skill with the repository README's skills CLI flow: npx skills add nvidia/skills --skill jetson-print-device-info --yes. You can add --agent codex or --agent claude-code to target a client. The supplied README does not document a manual folder-copy procedure.
How do you use this skill?
After installation, ask the agent something like “Print the device information and create a baseline report on this running Jetson.” Run it on the Jetson target itself, not the host PC. The agent should follow the SKILL.md sequence and print the specified six-line report.