[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787TT0NT378SCWZZ6JBDS37":3,"skill-same:01M787TT0NT378SCWZZ6JBDS37":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M787TT0NT378SCWZZ6JBDS37","jetson-download-bsp",null,"Download NVIDIA Jetson Linux BSP artifacts (BSP tarball, sample rootfs, public_sources, x-tools, guides) for the active target. Use for Auto Setup; not for extraction or profile edits.","Solizardking\u002Ftrain2earn","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786KDC5C3NPE4W44C5641EZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-download-bsp\ndescription: >-\n  Download NVIDIA Jetson Linux BSP artifacts (BSP tarball, sample\n  rootfs, public_sources, x-tools, guides) for the active target. Use\n  for Auto Setup; not for extraction or profile edits.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags: [setup, bootstrap, download]\n  domain: setup\n---\n\n# Download BSP Artifacts\n\n`jetson-download-bsp` owns network fetches for the Auto Setup path.\nIt does not extract archives, initialize source trees, register documents,\nor edit the active target profile. Those remain owned by\n`jetson-init-image`, `jetson-init-source`, and `jetson-link-docs`.\n\n## When to invoke\n\n- `\u002Fjetson-quick-start` selected `Auto Setup`.\n- The user wants NVIDIA BSP artifacts downloaded into the current\n  workspace before running setup skills.\n\n## Inputs and outputs\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse if no active profile exists.\n\nFollow the shared\n[`quick_start_prefill` contract](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#quick_start_prefill-contract).\nWhen invoked by `\u002Fjetson-quick-start`, this skill consumes\n`quick_start_prefill.mode` and `quick_start_prefill.download.bsp_release`\nas the requested release when present. Missing or invalid prefilled values\nare not fatal, but a concrete release is required before any download\nstarts.\n\nUse the workspace root as the parent of `target-platform\u002F`. Place files\nwhere downstream setup skills already search:\n\n| Artifact | Destination |\n|---|---|\n| Jetson Linux BSP tarball | `\u003Cbsp_image.root_path or workspace\u002FImage>\u002FJetson_Linux_R\u003Cver>_aarch64.tbz2` |\n| Sample rootfs tarball | `\u003Cbsp_image.root_path or workspace\u002FImage>\u002FTegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2` |\n| `public_sources.tbz2` | `\u003Cworkspace>\u002FDownloads\u002Fpublic_sources.tbz2` |\n| `x-tools.tbz2` | `\u003Cworkspace>\u002FDownloads\u002Fx-tools.tbz2` |\n| Developer Guide | `\u003Cdocuments.root_path or workspace\u002FDocuments>\u002F` |\n| User Guide | `\u003Cdocuments.root_path or workspace\u002FDocuments>\u002F` |\n\nDo not write `bsp_image:`, `source:`, or `documents:` blocks. The next\nsetup skills will register derived metadata after extraction or user\nconfirmation.\n\n## Procedure\n\n### Resolve target release\n\nFetch the release list from:\n\u003Chttps:\u002F\u002Fdeveloper.nvidia.com\u002Fembedded\u002Fjetson-linux-archive>\n\nFrom the archive and linked release pages, list concrete releases that\nexplicitly support the active platform. Let the user choose a concrete\nJetson Linux \u002F L4T release token (`R36.4.4`, `36.4.4`, `38.2`,\n`38.2.1`, `38.4`, etc.); do not proceed with a family placeholder such\nas `R38.x`. A concrete release token is an optional leading `R` followed\nby two or three numeric dotted components. Preserve the token exactly as\nthe official page presents it; do not add `.0`, remove a patch component,\nor otherwise normalize it. Sort release choices by dotted numeric order\ndescending (newest first), comparing the components that are present; keep\nsource-provided recommendations in descriptions.\n\nResolve `quick_start_prefill.download.bsp_release` as follows:\n\n- Concrete and supported: continue with that release.\n- Missing, `skip`, blank, or a family placeholder (`R38.x`, `38.x`): show\n  supported concrete releases and ask the user to choose one.\n- Concrete but unsupported or ambiguous: stop before artifact discovery and\n  show the active platform, requested BSP release, supported concrete\n  releases, and source archive or release page.\n\nNever auto-substitute the requested release with a supported release, even\nwhen there is only one supported option.\n\nFor unsupported or ambiguous prefill, ask with the shared\n[`User input prompt style`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#user-input-prompt-style),\nto choose exactly one click-to-select action:\n\n- `pick_supported_release` — user selects one supported concrete release.\n- `confirm_override` — user confirms the incompatible release and enters\n  an override reason.\n- `cancel` — stop with no downloads.\n\nDo not continue to \"Locate release artifacts\" until the selected release is concrete and\nsupported, or the user explicitly confirms override. Record any override\nreason in the final summary. If the user cancels, stop with no downloads.\nDo not claim support unless the archive or linked release page explicitly\nlists the active platform.\n\n### Discovery retries\n\nFor every artifact WebFetch in \"Resolve target release\" and \"Locate release artifacts\" (BSP, rootfs,\n`public_sources.tbz2`, `x-tools.tbz2`, Developer Guide, User Guide),\ntry 3 attempts before marking it missing:\n\n1. Focused prompt — artifact name + file type.\n2. Verbatim link dump on the same URL — *\"list every hyperlink, text\n   and href, no filtering\"*. Accept product-specific names and\n   `.html` indexes.\n3. Verbatim dump on a sibling page — Jetson Linux archive, JetPack\n   downloads, or `https:\u002F\u002Fdocs.nvidia.com\u002Fjetson\u002Farchives\u002Fr\u003Cver>\u002F`.\n\nOnly after all 3 fail, route to user-paste \u002F skip. Never fabricate\nURLs.\n\n### Locate release artifacts\n\nFollow links from the selected release page. Never construct NVIDIA\ndownload URLs by string concatenation.\n\nRequired artifacts:\n\n- Jetson Linux BSP image tarball.\n- Tegra Linux sample root filesystem tarball.\n- `public_sources.tbz2`.\n- `x-tools.tbz2` \u002F **Crosstool-NG Toolchain gcc** matching the selected\n  BSP release.\n- Developer Guide.\n- User Guide.\n\nIf a guide is not available as a direct file link, accept the release\ndocumentation URL as the artifact and record it in the final summary.\nIf the toolchain is listed on a JetPack downloads page instead of the\nrelease page, follow the official page link and match the selected BSP\nrelease; do not synthesize the URL from a release number.\nDo not proceed until each required artifact is downloaded, already\npresent at its destination, represented by a URL, or explicitly skipped\nby the user.\n\n### Show the fetch plan\n\nBefore changing the workspace, print a plan with:\n\n- selected release and release page URL;\n- active platform summary (`reference_devkit.name`, optional\n  `custom_carrier.name`, and `flash_config`);\n- source URL and destination path, or documentation URL, for every artifact;\n- any existing destination file that will be reused;\n- any artifact that requires browser\u002FEULA handling instead of `curl`.\n\nDefault to **Download all**. Do not ask an extra confirmation when every\nrequired artifact is downloadable, already present for reuse, or a\ndocumentation URL to record. Print the plan and continue to disk-space\nverification.\n\nStill stop and ask before side effects in any of these cases:\n\n- the release required an incompatibility override;\n- a required artifact is missing and needs user-paste \u002F skip;\n- a destination file would be overwritten rather than reused;\n- the artifact requires browser\u002FEULA handling;\n- disk-space verification fails or cannot be computed safely.\n\n### Verify disk space\n\nSum `Content-Length` across artifacts to download (`curl -sI \u003Curl>`);\nrefuse if `df -B1 --output=avail \u003Cworkspace>` headroom \u003C sum × 1.2.\nSkip URL-only artifacts.\n\n### Download safely\n\nCreate destination directories as needed. For direct file links, use a\ntemporary `.part` path and rename only after success:\n\n```bash\nmkdir -p \"\u003Cdestination-dir>\"\ncurl -fL --retry 3 --retry-all-errors --retry-delay 5 -o \"\u003Cdestination>.part\" \"\u003Cartifact-url>\"\nmv \"\u003Cdestination>.part\" \"\u003Cdestination>\"\n```\n\nIf a destination file already exists and is non-empty, reuse it by\ndefault after showing its path. Ask before overwriting. If an artifact\ndownload fails due to 404, 401\u002F403, EULA\u002Fbrowser authentication, or a\nnetwork error, stop and show the artifact URL plus expected destination\npath. Ask the user to download the file manually, skip that artifact, or\ncancel. Do not synthesize alternate NVIDIA URLs.\n\n### Validate filenames\n\nBefore finishing, verify the BSP and rootfs tarball filenames contain\nthe exact `R\u003Cver>` token from the official artifact URL or filename\ndiscovered in Step 2. `\u003Cver>` may have two or three numeric components\n(`R38.2`, `R38.2.1`, `R38.4`, etc.). Do not infer `R38.2.0` from\n`R38.2`, and do not assume that a selected two-component release maps to\na three-component tarball name:\n\n- `Jetson_Linux_R\u003Cver>_aarch64.tbz2`\n- `Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2`\n\nVerify `public_sources.tbz2` is a bzip2 tarball when it exists locally:\n\n```bash\nfile -b \"\u003Cworkspace>\u002FDownloads\u002Fpublic_sources.tbz2\" | grep -q \"bzip2 compressed\"\n```\n\nVerify `x-tools.tbz2` the same way when it exists locally:\n\n```bash\nfile -b \"\u003Cworkspace>\u002FDownloads\u002Fx-tools.tbz2\" | grep -q \"bzip2 compressed\"\n```\n\nWarn, but do not fail, if document filenames differ from the release\nversion; NVIDIA documentation naming is less consistent than tarballs.\n\n## Finish\n\nReport the selected release, downloaded\u002Freused\u002Fskipped artifacts, and\nexact local paths. Then hand back to the caller with:\n\n1. `\u002Fjetson-init-image`\n2. `\u002Fjetson-init-source`\n3. `\u002Fjetson-link-docs`\n\n## Gotchas\n\n- Keep this skill download-only; extraction belongs to\n  `jetson-init-image` and `jetson-init-source`.\n- Put image tarballs in the image root, not `Downloads\u002F`, because\n  `jetson-init-image` searches the image root, workspace root, and\n  current directory.\n- Put `public_sources.tbz2` in `Downloads\u002F` because\n  `jetson-init-source` auto-discovers that path for Branch A.\n- Put `x-tools.tbz2` in `Downloads\u002F` because `jetson-init-source`\n  auto-extracts that path and writes the resulting `source.toolchain`\n  prefix.\n- The User Guide maps to `documents.bsp_user_guide` in the profile\n  schema (alongside `bsp_developer_guide`). `jetson-link-docs` writes\n  it when the user confirms; this skill only stages the file or URL.\n\n## Purpose\n\nStage the four NVIDIA-shipped artifacts (BSP, sample rootfs,\npublic_sources, x-tools) plus the Developer \u002F User Guides at the exact\npaths the Setup skills look in, so `\u002Fjetson-init-image`,\n`\u002Fjetson-init-source`, and `\u002Fjetson-link-docs` can run offline once\nthis skill is done.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- Network access to `developer.nvidia.com` and the Jetson Linux archive\n  page.\n- Workspace layout with the expected `Image\u002F`, `Source\u002F`,\n  `Downloads\u002F`, and `Documents\u002F` roots (default workspace shape).\n\n## Limitations\n\n- Download-only; never extracts, runs `apply_binaries.sh`, mounts\n  sources, registers documents, or mutates the active profile.\n- Release selection is bounded to entries published on the official\n  Jetson Linux archive; pre-release or internal builds are out of\n  scope.\n- No retry \u002F mirror logic — failures are surfaced to the user, not\n  silently retried.\n\n## Troubleshooting\n\n- **Release page not reachable** — check VPN \u002F proxy; do not invent\n  fallback URLs. Stop and report.\n- **Archive name mismatch with active platform** — verify the release\n  declares the active reference devkit; if not, ask the user to pick a\n  supported release or switch target via `\u002Fjetson-set-target`.\n- **`public_sources.tbz2` missing on archive** — some releases ship it\n  as a separate page; follow the release-page link rather than\n  guessing the URL.\n- **Existing files in the destination** — refuse to overwrite without\n  confirmation; downloads must be idempotent at the user's discretion.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n- [`..\u002Fjetson-quick-start\u002FSKILL.md`](..\u002Fjetson-quick-start\u002FSKILL.md)\n- [`..\u002Fjetson-init-image\u002FSKILL.md`](..\u002Fjetson-init-image\u002FSKILL.md)\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md)\n- [`..\u002Fjetson-link-docs\u002FSKILL.md`](..\u002Fjetson-link-docs\u002FSKILL.md)\n- Jetson Linux archive: \u003Chttps:\u002F\u002Fdeveloper.nvidia.com\u002Fembedded\u002Fjetson-linux-archive>\n","# Download BSP Artifacts\n\n`jetson-download-bsp` owns network fetches for the Auto Setup path.\nIt does not extract archives, initialize source trees, register documents,\nor edit the active target profile. Those remain owned by\n`jetson-init-image`, `jetson-init-source`, and `jetson-link-docs`.\n\n## When to invoke\n\n- `\u002Fjetson-quick-start` selected `Auto Setup`.\n- The user wants NVIDIA BSP artifacts downloaded into the current\n  workspace before running setup skills.\n\n## Inputs and outputs\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse if no active profile exists.\n\nFollow the shared\n[`quick_start_prefill` contract](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#quick_start_prefill-contract).\nWhen invoked by `\u002Fjetson-quick-start`, this skill consumes\n`quick_start_prefill.mode` and `quick_start_prefill.download.bsp_release`\nas the requested release when present. Missing or invalid prefilled values\nare not fatal, but a concrete release is required before any download\nstarts.\n\nUse the workspace root as the parent of `target-platform\u002F`. Place files\nwhere downstream setup skills already search:\n\n| Artifact | Destination |\n|---|---|\n| Jetson Linux BSP tarball | `\u003Cbsp_image.root_path or workspace\u002FImage>\u002FJetson_Linux_R\u003Cver>_aarch64.tbz2` |\n| Sample rootfs tarball | `\u003Cbsp_image.root_path or workspace\u002FImage>\u002FTegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2` |\n| `public_sources.tbz2` | `\u003Cworkspace>\u002FDownloads\u002Fpublic_sources.tbz2` |\n| `x-tools.tbz2` | `\u003Cworkspace>\u002FDownloads\u002Fx-tools.tbz2` |\n| Developer Guide | `\u003Cdocuments.root_path or workspace\u002FDocuments>\u002F` |\n| User Guide | `\u003Cdocuments.root_path or workspace\u002FDocuments>\u002F` |\n\nDo not write `bsp_image:`, `source:`, or `documents:` blocks. The next\nsetup skills will register derived metadata after extraction or user\nconfirmation.\n\n## Procedure\n\n### Resolve target release\n\nFetch the release list from:\n\u003Chttps:\u002F\u002Fdeveloper.nvidia.com\u002Fembedded\u002Fjetson-linux-archive>\n\nFrom the archive and linked release pages, list concrete releases that\nexplicitly support the active platform. Let the user choose a concrete\nJetson Linux \u002F L4T release token (`R36.4.4`, `36.4.4`, `38.2`,\n`38.2.1`, `38.4`, etc.); do not proceed with a family placeholder such\nas `R38.x`. A concrete release token is an optional leading `R` followed\nby two or three numeric dotted components. Preserve the token exactly as\nthe official page presents it; do not add `.0`, remove a patch component,\nor otherwise normalize it. Sort release choices by dotted numeric order\ndescending (newest first), comparing the components that are present; keep\nsource-provided recommendations in descriptions.\n\nResolve `quick_start_prefill.download.bsp_release` as follows:\n\n- Concrete and supported: continue with that release.\n- Missing, `skip`, blank, or a family placeholder (`R38.x`, `38.x`): show\n  supported concrete releases and ask the user to choose one.\n- Concrete but unsupported or ambiguous: stop before artifact discovery and\n  show the active platform, requested BSP release, supported concrete\n  releases, and source archive or release page.\n\nNever auto-substitute the requested release with a supported release, even\nwhen there is only one supported option.\n\nFor unsupported or ambiguous prefill, ask with the shared\n[`User input prompt style`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#user-input-prompt-style),\nto choose exactly one click-to-select action:\n\n- `pick_supported_release` — user selects one supported concrete release.\n- `confirm_override` — user confirms the incompatible release and enters\n  an override reason.\n- `cancel` — stop with no downloads.\n\nDo not continue to \"Locate release artifacts\" until the selected release is concrete and\nsupported, or the user explicitly confirms override. Record any override\nreason in the final summary. If the user cancels, stop with no downloads.\nDo not claim support unless the archive or linked release page explicitly\nlists the active platform.\n\n### Discovery retries\n\nFor every artifact WebFetch in \"Resolve target release\" and \"Locate release artifacts\" (BSP, rootfs,\n`public_sources.tbz2`, `x-tools.tbz2`, Developer Guide, User Guide),\ntry 3 attempts before marking it missing:\n\n1. Focused prompt — artifact name + file type.\n2. Verbatim link dump on the same URL — *\"list every hyperlink, text\n   and href, no filtering\"*. Accept product-specific names and\n   `.html` indexes.\n3. Verbatim dump on a sibling page — Jetson Linux archive, JetPack\n   downloads, or `https:\u002F\u002Fdocs.nvidia.com\u002Fjetson\u002Farchives\u002Fr\u003Cver>\u002F`.\n\nOnly after all 3 fail, route to user-paste \u002F skip. Never fabricate\nURLs.\n\n### Locate release artifacts\n\nFollow links from the selected release page. Never construct NVIDIA\ndownload URLs by string concatenation.\n\nRequired artifacts:\n\n- Jetson Linux BSP image tarball.\n- Tegra Linux sample root filesystem tarball.\n- `public_sources.tbz2`.\n- `x-tools.tbz2` \u002F **Crosstool-NG Toolchain gcc** matching the selected\n  BSP release.\n- Developer Guide.\n- User Guide.\n\nIf a guide is not available as a direct file link, accept the release\ndocumentation URL as the artifact and record it in the final summary.\nIf the toolchain is listed on a JetPack downloads page instead of the\nrelease page, follow the official page link and match the selected BSP\nrelease; do not synthesize the URL from a release number.\nDo not proceed until each required artifact is downloaded, already\npresent at its destination, represented by a URL, or explicitly skipped\nby the user.\n\n### Show the fetch plan\n\nBefore changing the workspace, print a plan with:\n\n- selected release and release page URL;\n- active platform summary (`reference_devkit.name`, optional\n  `custom_carrier.name`, and `flash_config`);\n- source URL and destination path, or documentation URL, for every artifact;\n- any existing destination file that will be reused;\n- any artifact that requires browser\u002FEULA handling instead of `curl`.\n\nDefault to **Download all**. Do not ask an extra confirmation when every\nrequired artifact is downloadable, already present for reuse, or a\ndocumentation URL to record. Print the plan and continue to disk-space\nverification.\n\nStill stop and ask before side effects in any of these cases:\n\n- the release required an incompatibility override;\n- a required artifact is missing and needs user-paste \u002F skip;\n- a destination file would be overwritten rather than reused;\n- the artifact requires browser\u002FEULA handling;\n- disk-space verification fails or cannot be computed safely.\n\n### Verify disk space\n\nSum `Content-Length` across artifacts to download (`curl -sI \u003Curl>`);\nrefuse if `df -B1 --output=avail \u003Cworkspace>` headroom \u003C sum × 1.2.\nSkip URL-only artifacts.\n\n### Download safely\n\nCreate destination directories as needed. For direct file links, use a\ntemporary `.part` path and rename only after success:\n\n```bash\nmkdir -p \"\u003Cdestination-dir>\"\ncurl -fL --retry 3 --retry-all-errors --retry-delay 5 -o \"\u003Cdestination>.part\" \"\u003Cartifact-url>\"\nmv \"\u003Cdestination>.part\" \"\u003Cdestination>\"\n```\n\nIf a destination file already exists and is non-empty, reuse it by\ndefault after showing its path. Ask before overwriting. If an artifact\ndownload fails due to 404, 401\u002F403, EULA\u002Fbrowser authentication, or a\nnetwork error, stop and show the artifact URL plus expected destination\npath. Ask the user to download the file manually, skip that artifact, or\ncancel. Do not synthesize alternate NVIDIA URLs.\n\n### Validate filenames\n\nBefore finishing, verify the BSP and rootfs tarball filenames contain\nthe exact `R\u003Cver>` token from the official artifact URL or filename\ndiscovered in Step 2. `\u003Cver>` may have two or three numeric components\n(`R38.2`, `R38.2.1`, `R38.4`, etc.). Do not infer `R38.2.0` from\n`R38.2`, and do not assume that a selected two-component release maps to\na three-component tarball name:\n\n- `Jetson_Linux_R\u003Cver>_aarch64.tbz2`\n- `Tegra_Linux_Sample-Root-Filesystem_R\u003Cver>_aarch64.tbz2`\n\nVerify `public_sources.tbz2` is a bzip2 tarball when it exists locally:\n\n```bash\nfile -b \"\u003Cworkspace>\u002FDownloads\u002Fpublic_sources.tbz2\" | grep -q \"bzip2 compressed\"\n```\n\nVerify `x-tools.tbz2` the same way when it exists locally:\n\n```bash\nfile -b \"\u003Cworkspace>\u002FDownloads\u002Fx-tools.tbz2\" | grep -q \"bzip2 compressed\"\n```\n\nWarn, but do not fail, if document filenames differ from the release\nversion; NVIDIA documentation naming is less consistent than tarballs.\n\n## Finish\n\nReport the selected release, downloaded\u002Freused\u002Fskipped artifacts, and\nexact local paths. Then hand back to the caller with:\n\n1. `\u002Fjetson-init-image`\n2. `\u002Fjetson-init-source`\n3. `\u002Fjetson-link-docs`\n\n## Gotchas\n\n- Keep this skill download-only; extraction belongs to\n  `jetson-init-image` and `jetson-init-source`.\n- Put image tarballs in the image root, not `Downloads\u002F`, because\n  `jetson-init-image` searches the image root, workspace root, and\n  current directory.\n- Put `public_sources.tbz2` in `Downloads\u002F` because\n  `jetson-init-source` auto-discovers that path for Branch A.\n- Put `x-tools.tbz2` in `Downloads\u002F` because `jetson-init-source`\n  auto-extracts that path and writes the resulting `source.toolchain`\n  prefix.\n- The User Guide maps to `documents.bsp_user_guide` in the profile\n  schema (alongside `bsp_developer_guide`). `jetson-link-docs` writes\n  it when the user confirms; this skill only stages the file or URL.\n\n## Purpose\n\nStage the four NVIDIA-shipped artifacts (BSP, sample rootfs,\npublic_sources, x-tools) plus the Developer \u002F User Guides at the exact\npaths the Setup skills look in, so `\u002Fjetson-init-image`,\n`\u002Fjetson-init-source`, and `\u002Fjetson-link-docs` can run offline once\nthis skill is done.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- Network access to `developer.nvidia.com` and the Jetson Linux archive\n  page.\n- Workspace layout with the expected `Image\u002F`, `Source\u002F`,\n  `Downloads\u002F`, and `Documents\u002F` roots (default workspace shape).\n\n## Limitations\n\n- Download-only; never extracts, runs `apply_binaries.sh`, mounts\n  sources, registers documents, or mutates the active profile.\n- Release selection is bounded to entries published on the official\n  Jetson Linux archive; pre-release or internal builds are out of\n  scope.\n- No retry \u002F mirror logic — failures are surfaced to the user, not\n  silently retried.\n\n## Troubleshooting\n\n- **Release page not reachable** — check VPN \u002F proxy; do not invent\n  fallback URLs. Stop and report.\n- **Archive name mismatch with active platform** — verify the release\n  declares the active reference devkit; if not, ask the user to pick a\n  supported release or switch target via `\u002Fjetson-set-target`.\n- **`public_sources.tbz2` missing on archive** — some releases ship it\n  as a separate page; follow the release-page link rather than\n  guessing the URL.\n- **Existing files in the destination** — refuse to overwrite without\n  confirmation; downloads must be idempotent at the user's discretion.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md)\n- [`..\u002Fjetson-quick-start\u002FSKILL.md`](..\u002Fjetson-quick-start\u002FSKILL.md)\n- [`..\u002Fjetson-init-image\u002FSKILL.md`](..\u002Fjetson-init-image\u002FSKILL.md)\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md)\n- [`..\u002Fjetson-link-docs\u002FSKILL.md`](..\u002Fjetson-link-docs\u002FSKILL.md)\n- Jetson Linux archive: \u003Chttps:\u002F\u002Fdeveloper.nvidia.com\u002Fembedded\u002Fjetson-linux-archive>\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":30,"domain":27,"data-classification":31},[27,28,29],"setup","bootstrap","download","Jetson Team","public","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 11:52:53",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add Solizardking\u002Ftrain2earn --skill jetson-download-bsp",{"tool":46,"command":47},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill jetson-download-bsp",{"tool":49,"command":50},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill jetson-download-bsp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002FSKILL.md",true,[54,60,64,68],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"BENCHMARK.md","REFERENCE","参考文档",3821,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002FBENCHMARK.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"metadata.json",391,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002Fmetadata.json",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"skill-card.md",3616,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002Fskill-card.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"verification.json",1379,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-download-bsp\u002Fverification.json",[73,81,89,97,104,112],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78B94RSCAKMH1QS79VE6DG9","testing","For testing with Light Protocol programs and clients on localnet, devnet, and mainnet validation.","MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78B81BKY8RX12HETPG8YKWK","qedgen","Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions \"qedgen\", \"lean proof\", \"formal proof\", \"verify my code\", \"prove correctness\", \"formal verification\", or wants mathematical guarantees about their implementation.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M78B7Q7C5K54E01DN83A60KG","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl — \"what's the balance of \u003Cwallet>\", \"look up transaction \u003Csig>\", \"token balance for \u003Caccount>\", \"check this address on mainnet\u002Fdevnet\". End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, security checklists, and JSON-RPC curl lookups against public clusters. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M78B7HXD6N6GWKSVRQ8F6Q31","solana-common-errors","Diagnose and fix common Solana development errors — GLIBC mismatches, Anchor version conflicts, cargo build-sbf \u002F platform-tools failures, LiteSVM issues, edition2024 crate pins, RPC airdrops, and Anchor 0.29→0.32 migrations. Use when builds fail, Anchor CLI won't install, or CI breaks on Debian\u002FUbuntu.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-common-errors\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M78B6T7YSYWQ0N4DP40QDXEZ","skill-creator","Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M78B1VFT9X5AND7AE1HZPZGF","phantom-wallet-mcp","Execute wallet operations through the Phantom MCP server. Use when the user wants to interact with their Phantom wallet directly — get addresses, transfer SOL or SPL tokens, buy\u002Fswap tokens, sign transactions, and sign messages across Solana, Ethereum, Bitcoin, and Sui. Requires the @phantom\u002Fmcp-server to be configured as an MCP server.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fphantom-wallet-mcp\u002FSKILL.md",[],[]]