owns network fetches for the Auto Setup path. It does not extract archives, initialize source trees, register documents, or edit the active target profile. Those remain owned by , , and .

Resolve the active profile per

../../context/target-platform-contract.md

. Refuse if no active profile exists.

Follow the shared

quick_start_prefill

contract. When invoked by , this skill consumes and as the requested release when present. Missing or invalid prefilled values are not fatal, but a concrete release is required before any download starts.

Use the workspace root as the parent of . Place files where downstream setup skills already search:

<bsp_image.root_path or workspace/Image>/Jetson_Linux_R<ver>_aarch64.tbz2

<bsp_image.root_path or workspace/Image>/Tegra_Linux_Sample-Root-Filesystem_R<ver>_aarch64.tbz2

public_sources.tbz2

<workspace>/Downloads/public_sources.tbz2

x-tools.tbz2

<workspace>/Downloads/x-tools.tbz2

<documents.root_path or workspace/Documents>/

<documents.root_path or workspace/Documents>/

Do not write , , or blocks. The next setup skills will register derived metadata after extraction or user confirmation.

Fetch the release list from: https://developer.nvidia.com/embedded/jetson-linux-archive

From the archive and linked release pages, list concrete releases that explicitly support the active platform. Let the user choose a concrete Jetson Linux / L4T release token (, , , , , etc.); do not proceed with a family placeholder such as . A concrete release token is an optional leading followed by two or three numeric dotted components. Preserve the token exactly as the official page presents it; do not add , remove a patch component, or otherwise normalize it. Sort release choices by dotted numeric order descending (newest first), comparing the components that are present; keep source-provided recommendations in descriptions.

Resolve as follows:

Never auto-substitute the requested release with a supported release, even when there is only one supported option.

For unsupported or ambiguous prefill, ask with the shared

User input prompt style

, to choose exactly one click-to-select action:

Do not continue to "Locate release artifacts" until the selected release is concrete and supported, or the user explicitly confirms override. Record any override reason in the final summary. If the user cancels, stop with no downloads. Do not claim support unless the archive or linked release page explicitly lists the active platform.

For every artifact WebFetch in "Resolve target release" and "Locate release artifacts" (BSP, rootfs, , , Developer Guide, User Guide), try 3 attempts before marking it missing:

Only after all 3 fail, route to user-paste / skip. Never fabricate URLs.

Follow links from the selected release page. Never construct NVIDIA download URLs by string concatenation.

Required artifacts:

If a guide is not available as a direct file link, accept the release documentation URL as the artifact and record it in the final summary. If the toolchain is listed on a JetPack downloads page instead of the release page, follow the official page link and match the selected BSP release; do not synthesize the URL from a release number. Do not proceed until each required artifact is downloaded, already present at its destination, represented by a URL, or explicitly skipped by the user.

Before changing the workspace, print a plan with:

Default to Download all. Do not ask an extra confirmation when every required artifact is downloadable, already present for reuse, or a documentation URL to record. Print the plan and continue to disk-space verification.

Still stop and ask before side effects in any of these cases:

Sum across artifacts to download (); refuse if headroom < sum × 1.2. Skip URL-only artifacts.

Create destination directories as needed. For direct file links, use a temporary path and rename only after success:

mkdir -p "<destination-dir>"
curl -fL --retry 3 --retry-all-errors --retry-delay 5 -o "<destination>.part" "<artifact-url>"
mv "<destination>.part" "<destination>"

If a destination file already exists and is non-empty, reuse it by default after showing its path. Ask before overwriting. If an artifact download fails due to 404, 401/403, EULA/browser authentication, or a network error, stop and show the artifact URL plus expected destination path. Ask the user to download the file manually, skip that artifact, or cancel. Do not synthesize alternate NVIDIA URLs.

Before finishing, verify the BSP and rootfs tarball filenames contain the exact token from the official artifact URL or filename discovered in Step 2. may have two or three numeric components (, , , etc.). Do not infer from , and do not assume that a selected two-component release maps to a three-component tarball name:

Verify is a bzip2 tarball when it exists locally:

file -b "<workspace>/Downloads/public_sources.tbz2" | grep -q "bzip2 compressed"

Verify the same way when it exists locally:

file -b "<workspace>/Downloads/x-tools.tbz2" | grep -q "bzip2 compressed"

Warn, but do not fail, if document filenames differ from the release version; NVIDIA documentation naming is less consistent than tarballs.

Report the selected release, downloaded/reused/skipped artifacts, and exact local paths. Then hand back to the caller with:

Stage the four NVIDIA-shipped artifacts (BSP, sample rootfs, public_sources, x-tools) plus the Developer / User Guides at the exact paths the Setup skills look in, so , , and can run offline once this skill is done.