Jetson BSP Info Check
Verify Jetson BSP version, board configs, and rootfs state before flashing.
The skill explicitly limits itself to read-only inspection of a user-specified BSP tree; paths are quoted, there is no network access, credential handling, or destructive command. Deductions apply because it lacks explicit execution confirmation, privilege-boundary guidance, sensitive-path handling, and independent source attribution within the skill itself.
The ordered workflow, required artifacts, fallback paths, and diagnostic messages are internally coherent and statically plausible. Deductions apply because there is no standalone implementation, automated test coverage, or handling evidence for permissions and unusual filesystem cases; under static calibration this cannot exceed 10.
Audience, Linux host requirement, L4T_ROOT input, four-line output, and major non-fit boundaries are stated, and the core function does not depend on overseas services. Deductions apply because exclusion triggers, Chinese-language guidance, and compatibility evidence across BSP variants are limited.
The documentation includes purpose, prerequisites, inputs, procedure, output, examples, limitations, and troubleshooting, with a version field. Deductions apply because the skill-card license description is not fully consistent with SKILL.md, the benchmark notes an author-format schema finding, and changelog, maintainer contact, and update path are absent.
The skill directly produces the requested release, board-config, and rootfs summary in a defined format, and the supplied evaluation files report two positive task results. Deductions apply because the passwd-file check is only a weak rootfs proxy, and there are no negative cases or independently verifiable representative execution artifacts.
The skill supplies concrete commands, file locations, expected output, and failure branches; evals.json provides task-level behavioral criteria. Deductions apply because there is no committed test suite or CI coverage for this skill, and the two-task benchmark lacks raw logs and independent reproduction.
- rootfs/etc/passwd is only a coarse proxy and does not establish that the rootfs is complete or safe to flash.
- The instructions assume direct shell execution; confirm that L4T_ROOT is the intended BSP directory and reconcile the inconsistent license metadata.
- No negative-trigger evaluation is supplied, so misuse on a Jetson target, a non-BSP directory, or an unrelated request remains insufficiently tested.
What does this skill do, and when should you use it?
This is a read-only Agent Skill for inspecting a Jetson Linux_for_Tegra BSP tree on a Linux host. It validates the presence of flash.sh and nv_tegra/, reads the L4T release header, lists board configuration files, and checks whether the rootfs has been populated. It does not flash a device or modify the rootfs. It is suited to pre-flash sanity checks that catch an incorrect L4T version, an invalid BSP path, or an unpopulated rootfs.
Resolves the optional L4T_ROOT variable, defaulting to the current directory; validates flash.sh and nv_tegra/; reads the first line of nv_tegra/nv_tegra_release or rootfs/etc/nv_tegra_release; lists *.conf files in L4T_ROOT as a comma-separated line; checks rootfs/etc/passwd and reports populated or empty; and prints a short report containing L4T root, L4T release, Board configs, and Rootfs.
- A host-PC user has unpacked a Jetson BSP tarball and wants to verify the L4T release and supported board configs before flashing.
- An engineer needs to confirm that a Linux_for_Tegra/ directory contains the expected BSP anchor files.
- A developer wants to check whether apply_binaries.sh has populated the rootfs.
- A user is investigating a suspected wrong BSP path, missing release metadata, or pre-flash configuration issue.
What are this skill's strengths and limitations?
- Read-only workflow that performs no flashing or rootfs changes.
- Produces a focused pre-flash baseline for release, board configs, and rootfs state.
- Provides a clear early error for an invalid Linux_for_Tegra root and labeled fallbacks for missing release data.
- Uses common Linux command-line utilities.
- The rootfs check only tests for rootfs/etc/passwd and cannot detect a partially populated rootfs.
- It lists every *.conf file rather than selecting the intended target board.
- It does not validate signatures, kernel images, or device-tree overlays.
- The supplied materials do not document an independent test suite or platform test results for this skill.
How do you install this skill?
Install the specific skill with the skills CLI:
npx skills add nvidia/skills --skill jetson-print-bsp-info --yes
The README documents CLI installation but does not document a separate manual-copy path.
How do you use this skill?
On a Linux host, change to the Linux_for_Tegra/ directory or set an absolute path:
export L4T_ROOT=/absolute/path/to/Linux_for_Tegra
Then ask an agent to use the skill, for example: "Check this Jetson BSP's L4T version, board configs, and rootfs state, and print a concise report." The procedure validates the root, reads release information, lists *.conf files, and checks rootfs/etc/passwd.