Jetson BSP Source Builder
Rebuild Jetson BSP device trees, kernels, and modules from source changes and produce a deployable artifact manifest.
The skill scopes build outputs to source.root_path and hands them to the promote stage through a manifest; it validates profiles, toolchains, prerequisites, and describes atomic writes plus Git-based recovery paths. However, it can copy files, modify Makefiles and flash configuration, and create commits, while explicit pre-execution confirmation and complete rollback procedures are mostly described as workflow conventions rather than enforced controls, so points are deducted.
The documentation covers multiple build modes, dependency checks, dirty-repository detection, routing on failure, and concrete troubleshooting messages. Static review cannot reproduce the make chain, referenced files, or workspace-dependent edge cases, and several key behaviors depend on external skills and state, so the score is reduced within the static ceiling.
Triggers, audience, modes, auto-selection rules, and non-applicable routing are reasonably clear for Jetson BSP workflows. However, Chinese-language interaction requirements and the full non-fit boundary are not specified, and reachability of all dependencies in mainland-China environments is not demonstrated, so points are deducted.
The skill has substantial information architecture, progressive references, parameters, examples, limitations, troubleshooting, version metadata, and an Apache-2.0 declaration in SKILL.md. Maintenance ownership is only a team label, no changelog or named update path is provided, repository license metadata is NOASSERTION, and governance descriptions are not fully consistent across files, so points are deducted.
The goal is concrete: select a build mode from repository changes, generate a promote-consumable manifest, and report the next action. Examples and evaluation files support plausible happy-path usefulness, but this static review cannot independently verify real build artifacts or complete result coverage; users still need review and subsequent promote/flash steps, so the static ceiling applies.
The source includes detailed commands, artifact mappings, state and manifest schemas, limitations, and an evaluation report, providing limited auditability. The reported evaluation results are not independently reproducible from the supplied material, and there is no real CI or committed test suite covering key paths, so the score remains at the static ceiling.
- Execution modifies workspace files and may create multiple Git commits; confirm the target profile, paths, branch, and commit batching before running, and preserve a recoverable working-tree state.
- Build commands, referenced documents, and the upstream environment file were not executed or verified in this static review; perform a controlled trial on the target BSP release first.
- The manifest relies on implicit contracts among source state, bsp_image, dirty-repository watermarks, and the promote skill; inconsistent state may cause omitted or incorrectly deployed artifacts.
- Chinese-language prompts and mainland-China network availability are not demonstrated; apt, NVIDIA documentation, and toolchain acquisition may require mirrors or offline preparation.
What does this skill do, and when should you use it?
This skill rebuilds kernel-side artifacts for an NVIDIA Jetson BSP, including DTBs, out-of-tree modules, in-tree modules, and the kernel Image. It reads the active target profile, toolchain, source layout, and NVIDIA build environment, then selects dt, oot, kernel, or full mode from the dirty-repository set. Outputs remain in the source tree, while a manifest records artifacts for jetson-promote-image. It is intended for workspaces that have already completed Jetson target, image, and source initialization.
Reads the active target profile, BSP build environment, source paths, and cross-toolchain; checks required host packages and repository layout; detects dirty repositories using commit watermarks and uncommitted changes; invokes NVIDIA's existing Makefile build primitives for DTBs, OOT modules, in-tree modules, and Image; registers the composite custom overlay in dt and full modes; writes traceable rebuilt artifacts to .build-manifest.yaml and updates .build-state.yaml after success.
- A Jetson developer has committed device-tree changes and needs an NVIDIA-DTB-only rebuild.
- A Jetson developer has changed OOT driver repositories and needs to rebuild the OOT module set.
- A kernel developer needs a new Image, in-tree modules, and kernel-side device trees after kernel-source changes.
- A BSP integrator has mixed changes across kernel-side repositories or needs the optional install-consolidation pass.
- A developer needs to rerun a build interrupted by automation or triggered by source changes pulled with git.
What are this skill's strengths and limitations?
- Provides four build modes and automatic mode selection from dirty repositories.
- Delegates to NVIDIA's existing BSP build primitives instead of duplicating their logic.
- Tracks source watermarks and rebuilt artifacts for an auditable deployment handoff.
- Includes checks for toolchain validity, source layout, host packages, and composite-overlay registration.
- Requires an initialized Jetson BSP workspace, expected source layout, and an ARM64 cross-toolchain; it does not resolve a missing toolchain itself.
- Manual oot mode requires previously built kernel headers.
- It does not write outputs directly into the BSP image or perform device flashing.
- Overlay-only configuration changes bypass this Build stage, and kernel device-tree changes must use the composite-overlay contract.
How do you install this skill?
Install it through the skills CLI documented by the repository README: npx skills add nvidia/skills --skill jetson-build-source --yes. The skill directory is skills/jetson-build-source; the README documents no additional skill-specific installation procedure.
How do you use this skill?
Run /jetson-init-image and /jetson-init-source first so the active target profile, BSP source tree, kernel_src_build_env.sh, and source.toolchain are available. Let the skill detect changes and choose a mode with /jetson-build-source. Force a mode with /jetson-build-source dt, /jetson-build-source oot, /jetson-build-source kernel, or /jetson-build-source full. After a successful build, continue with /jetson-promote-image.