/jetson-quick-start

name: jetson-quick-start
description: >-
  Entry skill for Jetson / IGX BSP customization. Asks one core
  click-to-select setup questionnaire and passes prefilled answers to
  downstream setup skills.
version: 0.0.1
license: "Apache-2.0"
metadata:
  data-classification: public
  author: "Jetson Team"
  tags: [setup, bootstrap, download]
  domain: setup

Quick Start — BSP customization entrypoint

`jetson-quick-start` is a dispatcher and intake form. It does not download, extract, materialize sources, bind documents, or derive carrier files. It chooses the setup path, gathers core answers, then hands those answers to the skills that own the actual work.

Modes

Do not ask setup mode in a separate prompt. Include it as the first field in the core quick-start questionnaire, with choices shown in this fixed order:

1. `Auto Setup` 2. `Guided Setup` 3. `Use Existing Workspace`

Offer `cancel` separately as an exit action, not as a setup mode.

| Mode | Use when | Planned skills | |---|---|---| | `Auto Setup` | Fresh workspace, network available | target setup, `/jetson-download-bsp`, `/jetson-init-image`, `/jetson-init-source`, `/jetson-link-docs`, `/jetson-generate-kb`, optional `/jetson-derive-carrier` | | `Guided Setup` | User already has paths, repos, or archives | target setup, `/jetson-init-image`, `/jetson-init-source`, `/jetson-link-docs`, `/jetson-generate-kb`, optional `/jetson-derive-carrier` | | `Use Existing Workspace` | BSP image, source tree, and docs are already prepared | target setup, workspace verification, `/jetson-generate-kb`, optional `/jetson-derive-carrier`; route to init skills only for missing prerequisites |

Target setup means keep the active profile, switch via `/jetson-set-target`, or create one via `/jetson-init-target`.

Procedure

Print Disclaimer

Before opening the core questionnaire or inspecting setup inputs, print this disclaimer block exactly once:

================================================================================
DISCLAIMER
These skills help automate Jetson BSP setup and customization, but they do not
replace NVIDIA official documentation or engineering review. Review generated
plans, commands, diffs, and commit messages before accepting them.

Flashing can erase device storage or leave a target temporarily unbootable.
Keep backups and verify the active target, BSP release, and hardware setup
before deploy steps.
================================================================================

Disclaimer Acceptance Gate

Immediately after printing the disclaimer, open a separate one-question `AskUserQuestions` disclaimer form and wait for the user's submitted answer before doing anything else. Do not collect disclaimer acceptance with a plain-text chat reply, inferred default, prior run state, active profile, cached answer, or any other non-UI signal.

The form must contain exactly one question:

1. `accept_disclaimer` — prompt: "Accept the disclaimer and continue quick-start?" Choices: `accept_disclaimer` and `cancel`.

Treat only a submitted `accept_disclaimer` choice as acceptance. The disclaimer form is separate from the core questionnaire and does not replace any of the four routing-critical core questions.

If the form cannot be opened, is unavailable, is cancelled, returns no submitted answer set, or returns any answer other than `accept_disclaimer`, stop immediately and report that quick-start cannot continue until the disclaimer is accepted through `AskUserQuestions`.

Mandatory Questionnaire Gate

After the disclaimer has been accepted, `jetson-quick-start` MUST open the core `AskUserQuestions` questionnaire and wait for the user's submitted answers before doing any setup dispatch. If the questionnaire cannot be opened, is unavailable, is cancelled, or returns no submitted answer set, stop immediately and report that quick-start cannot continue without the questionnaire.

Do not continue by using existing active profiles, workspace state, tarball names, cached answers, release compatibility, or "obvious" defaults. Do not call downstream skills until this gate has a submitted `mode` answer and normalized `quick_start_prefill`.

Survey State

Inspect `target-platform/active_target.yml` and existing `target-platform/*.yaml` profiles. If an active profile exists, show `reference_devkit.name`, optional `custom_carrier.name`, and active `flash_config`. Do not infer platform identity from tarballs, repo names, or document titles.

Read [`../../references/bsp-platforms-catalogue.md`](../../references/bsp-platforms-catalogue.md) and parse every row in the product / chip / SKU / flash-config table. This catalogue is the source for the full `active_platform` questionnaire list. If the list is incomplete, update the catalogue; do not duplicate or patch the platform list inside quick-start. Do not read `jetson-init-target/SKILL.md` or run the init-target flow during quick-start preprocessing; downstream target creation remains owned by `jetson-init-target`.

Keep this survey lightweight so the core questionnaire appears quickly: read target profile pointers/summaries, perform cheap path existence checks when useful, and fetch only lightweight Jetson Linux release metadata from the official archive needed to populate `bsp_release` choices. Parse all current release sections, not only the section that appears to match the selected platform. Do not scan large BSP / source / document trees, inspect archives, generate KB content, or run setup tools before the user submits the core questionnaire. Prepare the possible plans for all three modes; choose the actual downstream plan only after the form is submitted.

Print Platform Reference List

Before opening the `AskUserQuestions` UI, print the full platform list parsed from `bsp-platforms-catalogue.md` with stable numeric indexes for this run:

Available platforms:
T234 - Orin
  1. Jetson AGX Orin 64GB | CVM P3701-0005 | CVB P3737-0000 |