Jetson BSP Quick Start
Choose a Jetson BSP customization path and hand validated intake answers to the right setup skills.
The skill requires an explicit disclaimer, AskUserQuestions confirmation, and non-inference of routing inputs, while stating that it does not itself download, write, or bind artifacts. It also warns about storage erasure during flashing. Points are deducted because downstream actions may still have external or destructive effects, with no unified rollback procedure, sensitive-data guidance, or complete data-flow boundary.
The workflow, stop conditions, input rules, and troubleshooting messages are relatively detailed, and benchmark material is included. Static review did not execute key paths; availability of AskUserQuestions, referenced files, and downstream skills was not reproduced, so the score is limited by the static ceiling and uncertainty.
The audience, three modes, four routing fields, and non-fit boundaries are clear. Points are deducted because Chinese-language interaction is not demonstrated, mainland-China reachability of the official archive is unverified, and trigger precision is supported only by two positive evaluations.
The skill includes versioning, license metadata, structured sections, references, limitations, troubleshooting, and benchmark documentation. Points are deducted for missing recommended Instructions and Examples sections, nonconforming author metadata, unclear maintenance/change ownership, and a license description in skill-card.md that is not fully consistent with the SKILL.md metadata.
As a dispatcher, it clearly gathers routing information and delegates work to specialized downstream skills; the benchmark reports 92% Codex correctness and 67% effectiveness. Points are deducted because there are only two positive tasks, no negative-trigger cases, and static review cannot verify actual outputs, downstream completion, or benefit over manual alternatives.
The fixed revision, evaluation tasks, ground truth, behavior checks, and static-validation findings provide limited auditability. Points are deducted because the reported evaluations lack reproducible execution artifacts or dedicated key-path test coverage, so independent multi-source verification is not established.
- The entrypoint may dispatch downstream download, initialization, document-binding, and flashing actions; confirm hardware, BSP version, paths, and backups before execution, and do not treat the entry skill's gates as a complete rollback guarantee for downstream work.
- Auto Setup depends on official Jetson Linux archive metadata and network access; mainland-China deployments should verify reachability in advance and retain the skip or typed-input fallback.
- The benchmark covers only two positive tasks, so it does not establish resistance to false triggering or prove that the complete downstream chain runs successfully.
What does this skill do, and when should you use it?
jetson-quick-start is an entry skill for Jetson and IGX BSP customization. It collects the routing-critical choices and dispatches downstream setup skills through Auto Setup, Guided Setup, or Use Existing Workspace modes. It requires separate disclaimer acceptance and a submitted core questionnaire before dispatching anything. The skill does not download, extract, materialize sources, bind documents, generate carrier files, or modify target profiles itself.
Prints the required BSP customization disclaimer and waits for explicit acceptance through AskUserQuestions; reads active target information and the BSP platform catalogue to prepare the platform list; fetches lightweight Jetson Linux archive metadata for release choices; opens one core questionnaire for mode, platform, BSP release, and custom-carrier intent; normalizes explicit answers into quick_start_prefill; plans and invokes downstream target setup, BSP download, image initialization, source initialization, document linking, knowledge-base generation, or carrier-derivation skills according to the selected mode and prerequisite checks; reports executed skills, skipped skills, remaining questions, workspace readiness, and eligible I/O customization suggestions.
- A Jetson engineer has a fresh workspace and network access and wants to enter an automated BSP setup flow.
- A developer already has BSP paths, repositories, or archives and needs a guided setup handoff.
- A team has prepared an image, source tree, and documentation and wants the existing workspace verified before knowledge-base generation.
- An engineering team is starting a custom-carrier BSP workflow and wants carrier-specific details routed to the downstream skills that own them.
What are this skill's strengths and limitations?
- Provides one entrypoint for three distinct BSP setup situations.
- Requires explicit UI submission for both disclaimer acceptance and routing-critical answers.
- Keeps image, source, document, and carrier mutations with the downstream skills that own those profile blocks.
- Can verify an existing workspace and suggest I/O customization paths when carrier-related documents are bound.
- Does not perform downloading, extraction, source materialization, document binding, or carrier-file generation itself.
- Depends on the AskUserQuestions UI, the BSP platform catalogue, and multiple downstream Jetson skills.
- Does not validate platform/BSP compatibility; that decision belongs to jetson-download-bsp.
- The supplied SKILL.md does not provide platform coverage, automated test results, or independent benchmark evidence.
How do you install this skill?
Install the individual skill from the NVIDIA/skills catalog with the documented skills CLI command:
npx skills add nvidia/skills --skill jetson-quick-start --yes
The README does not document additional per-skill installation methods or runtime version requirements.
How do you use this skill?
Trigger the skill in an agent that has loaded it:
/jetson-quick-start
First submit accept_disclaimer in the separate disclaimer form, then submit the core questionnaire. The selected mode determines downstream dispatch. Image paths, source paths, document paths, and detailed carrier information remain the responsibility of downstream skills. The supplied material does not document a complete standalone command-line execution procedure.