Jetson BSP Image Promoter
Sync Jetson customization overlays and build artifacts into a flash-ready staged BSP image.
The skill clearly limits itself to copying into a staged BSP image and forbids flashing or building; it lists prerequisites, scopes sudo to rootfs destinations, and discloses partial-failure behavior, lack of automatic rollback, and collision precedence. Points are deducted because there is no explicit user-confirmation step, copying changes external files, collision checking performs a fetch, partial failure can leave an intermediate state, and licensing is inconsistent across Apache-2.0, CC-BY-4.0, and repository NOASSERTION metadata.
The workflow, dependencies, path resolution, two-channel validation, idempotent copying, kernel mirroring, and initramfs refresh are described in substantial detail, with refusal paths and troubleshooting guidance. Points are deducted because this is an unexecuted static review; some implementation details depend on other skills or incomplete snippets, and there is no reproducible test evidence covering abnormal environments.
The audience, trigger phrase, normal deployment chain, standalone use case, and non-fit boundary of not building or flashing are clear. Points are deducted because it depends on Jetson BSP state, NVIDIA tools, git/yq/sudo, and specific directory contracts, without a complete fallback for missing dependencies or explicit Chinese-language and mainland-China environment support.
The documentation includes purpose, prerequisites, procedure, limitations, troubleshooting, references, versioning, and ownership, with layered reference files. Points are deducted because the frontmatter version is 0.0.1 while the body locks in a v0.2.0 specification; the benchmark reports missing recommended Instructions and Examples, the author format is nonconforming, license/terms are inconsistent, and there is no clear changelog.
The stated core task is coherent: diff-aware promotion of overlay and build artifacts into bsp_image, with initramfs refresh for kernel or module changes; the summary and next-step output are specified. Points are deducted because no execution or independent validation was performed, and the benchmark covers only two positive tasks with modest effectiveness results, so direct usability in representative environments is unproven.
The skill provides traceability through manifests, git HEADs, dirty-state checks, watermarks, and stdout summaries, plus a limited benchmark report. Points are deducted because there are no committed CI workflows or key-path test suites, no raw benchmark logs or independent reproduction, and only two positive cases with no negative-trigger samples; static evidence cannot justify a higher score.
- Execution modifies bsp_image and may modify rootfs through sudo; confirm the active profile, source files, and destination paths before running.
- There is no automatic rollback after copy failure, and licensing/skill-card terms are inconsistent; resolve both before publication.
- This assessment did not execute the skill; add reproducible tests for success, collisions, permission failures, stale manifests, and negative triggering.
What does this skill do, and when should you use it?
This skill handles the image-promotion stage of an NVIDIA Jetson Linux BSP deployment workflow. It reads Customize-* outputs from a Git overlay tracker and rebuilt artifacts from a build manifest, then copies them into the staged bsp_image. The copy pass is diff-aware, resumable, and defines manifest precedence for destination collisions; kernel or module changes also trigger kernel mirroring and initramfs refresh. It does not build source code or flash a device.
Resolves the active target-platform profile and source and bsp_image paths; validates the overlay Git state, build-manifest YAML, build-source freshness, and optional remote collision state; enumerates tracked overlay files and artifacts from .build-manifest.yaml; copies their union into bsp_image/Linux_for_Tegra with byte-identical skips and manifest-over-overlay precedence; mirrors kernel/Image to rootfs/boot/Image when needed; runs tools/l4t_update_initrd.sh when the kernel or modules changed, producing updated bootloader/l4t_initrd.img and rootfs/boot/initrd; reports scope, counts, copied paths, resolved paths, and the next workflow step.
- A Jetson BSP engineer has completed Customize-* edits and a source build and needs to update the staged image before flashing.
- A developer wants to inspect or statically validate the resolved bsp_image without flashing a device yet.
- A newly built Jetson kernel or module set must be included in the initramfs used at boot.
- A promotion stopped after a copy failure and the user needs to fix permissions or disk space and resume safely.
What are this skill's strengths and limitations?
- Combines Git overlay outputs and build-manifest artifacts in one promotion pass.
- Uses diff-aware copying and supports resumable reruns after partial failures.
- Mirrors the kernel and refreshes initramfs when kernel or module artifacts change.
- Provides explicit refusal conditions for dirty overlays, stale build sources, invalid manifests, and missing paths.
- Requires an initialized Jetson BSP workspace, Git, yq, cmp, sudo, and NVIDIA's initramfs update tool.
- There is no automatic rollback; a failed copy can leave bsp_image partially updated.
- Overlay scope is limited to the current Git HEAD; named tags and commit ranges are deferred.
- Only the latest build manifest is retained, so historical rollback requires rebuilding from an earlier state.
How do you install this skill?
Install the skill from the NVIDIA/skills catalog with the skills CLI:
npx skills add nvidia/skills --skill jetson-promote-image --yes
The README does not document additional manual folder-installation steps.
How do you use this skill?
Prepare an active target-platform profile with resolved source: and bsp_image: paths, then satisfy the skill's Jetson workspace, BSP image, manifest, and host-tool prerequisites. Ask the loaded agent with the trigger phrase: "promote bsp image". The skill performs promotion only when its validation gates pass; it does not build or flash. The typical next step is /jetson-flash-image.