What does this skill do, and when should you use it?
This skill initializes the source-side workspace required by Jetson BSP customization and build skills. It manages the Linux_for_Tegra overlay tracker, the bsp_sources source tree, an NVIDIA Crosstool-NG cross-compile prefix, and extra user-defined repositories. It prefers local public_sources.tbz2 content, using source_sync.sh or a customer Git repository only when the configured precedence requires it. Its scope is limited to the active profile’s source: block and the on-disk source workspace.
Resolves the active target and workspace paths; verifies that the BSP contains Linux_for_Tegra; creates or mounts the Linux_for_Tegra Git tracker; materializes bsp_sources using the configured url, archive, local public_sources.tbz2, or source_sync.sh branches; discovers or extracts a Crosstool-NG toolchain, validates its gcc prefix, and records source.toolchain; clones extra repositories from source.repos:; and prints component status, branch evidence, toolchain details, and the gcc version.
- A Jetson BSP developer has initialized the image and needs a source workspace for kernel, OOT, GPU, display, or device-tree customization.
- A team needs pristine and customization commits tracked separately in a Linux_for_Tegra overlay repository.
- An air-gapped or Git-restricted environment has staged public_sources.tbz2 and optionally x-tools.tbz2 locally.
- A customer needs to use a BSP source fork while exposing the canonical source_sync.sh sub-path layout.
How do you install this skill?
- Branch B/C access user-specified external Git repositories; confirm URLs, refs, network scope, and supply-chain integrity before execution.
- Archive extraction may leave partial directory contents after failure; the document requires manual cleanup for non-empty targets but does not provide full transactional rollback.
- Mainland-China networks may not reach the overseas endpoints used by source_sync.sh; prepare and validate public_sources.tbz2 for the offline path.
- The two internal positive evaluation tasks do not replace end-to-end validation on a real target platform.
- Verify how the Apache-2.0 skill metadata relates to the repository's CC-BY-4.0/Apache-2.0 notice and NOASSERTION license metadata.
- Shell / CLI
- Network access
- Local filesystem
GitBashtarbzip2
Install the skill from NVIDIA/skills with the skills CLI: npx skills add nvidia/skills --skill jetson-init-source --yes. The CLI prompts for the installation destination; manual repository cloning or folder copying is not required.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/NVIDIA/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/jetson-init-source" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- bootstrap the Jetson BSP customization workspace
- init the BSP source workspace.
Run /jetson-init-image first so the BSP is extracted and bsp_image.version is recorded. Stage public_sources.tbz2 in Downloads/ and optionally x-tools.tbz2. Then ask the agent to “bootstrap the Jetson BSP customization workspace” or “init the BSP source workspace.” The supplied SKILL.md does not define a separate user-facing command that executes the entire workflow.
What are this skill's strengths and limitations?
- Prioritizes local source archives, which suits air-gapped and Git-egress-constrained setups.
- Uses canonical Linux_for_Tegra and bsp_sources paths and refuses ambiguous multiple toolchain matches.
- Supports an empty overlay tracker, local archives, source_sync.sh, and customer Git repositories.
- Validates the cross-compiler, source_sync.sh clone failures, and relevant path conflicts.
- Requires jetson-init-image and an active target/workspace configuration first.
- Branch B and Branch C require network access; Branch B may fail when NVIDIA Git egress is blocked.
- Requires an NVIDIA Crosstool-NG toolchain prefix and will not silently use a compiler from PATH.
- The supplied material contains no standalone test suite or platform-specific test results.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Jetson BSP Source Workspace Initializer this page ✓ NVIDIA · Official | 58 · Recommended | ★ 3.6k | 13d ago | Apache-2.0 |
| Jetson BSP Source Builder ✓ NVIDIA · Official | 58 · Recommended | ★ 3.6k | 13d ago | Apache-2.0 |
| Jetson Target Knowledge Base Generator ✓ NVIDIA · Official | 54 · Use with care | ★ 3.6k | 13d ago | Apache-2.0 |
| Jetson BSP Quick Start ✓ NVIDIA · Official | 56 · Use with care | ★ 3.6k | 13d ago | Apache-2.0 |
| Jetson PCIe Controller Customizer ✓ NVIDIA · Official | 57 · Use with care | ★ 3.6k | 13d ago | Apache-2.0 |
How did FollowSkills review this skill?
The skill limits ownership to the source profile block and the workspace beneath source.root_path, and refuses non-empty paths, invalid inputs, missing toolchains, and unpinned tag fallbacks. Branch A supports an offline path, with no credential access or covert exfiltration described. Deductions apply because Branch B/C perform network Git clones from user-supplied repositories without commit hashes, checksums, or finer-grained permission isolation; rollback after extraction or symlink creation is incomplete, and there is no uniform pre-execution confirmation step.
The document specifies branch precedence, toolchain discovery, unreliable source_sync.sh exit handling, failure counting, tag fallback, and ambiguity refusal. Deductions apply because this is a static review and cannot establish that key paths run; core extraction logic and shared contracts are not fully supplied, Branch C depends on grep -P and other environment assumptions, and interruption recovery and error handling remain limited in places.
Invocation conditions, prerequisites, default paths, inputs, downstream dependencies, and several non-fit boundaries are explicit, and the skill clearly does not own input downloads. Deductions apply because it targets a specialized Jetson BSP environment without evidence for Chinese-language interaction or mainland-China reachability; Branch B/C depend on overseas Git endpoints, although an offline Branch A recovery route is documented.
The documentation has strong structure, covering overview, triggers, procedure, branches, prerequisites, limitations, troubleshooting, references, version, and ownership; the skill card identifies Apache-2.0. Deductions apply because BENCHMARK records missing Instructions and Examples sections and a nonconforming author format; version 0.0.1 has no clear changelog or concrete maintenance update path, and the repository license metadata is NOASSERTION, leaving license presentation to verify.
The skill directly addresses overlay-tracker creation, bsp_sources materialization, Crosstool-NG toolchain resolution, extra repository cloning, and checkable summary output; the evaluation tasks and ground truth describe intended outcomes. The static calibration caps this dimension at 7, and the internal benchmark covers only two positive tasks with a reported Codex effectiveness of 35%, so broad, low-rework usefulness is not established.
The files provide concrete commands, branch precedence, failure checks, tag derivation, archive-shape details, and two evaluation tasks, giving the procedure some auditability; BENCHMARK also records static validation findings. Deductions apply because the evidence is primarily maintainer-authored documentation and a small internal evaluation, with no committed skill-specific test suite or independent corroboration; under static calibration, execution-level verification cannot be claimed.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →