Agent skill · NVIDIA
jetson-init-target
Author a new Jetson target-platform profile (reference_devkit + optional custom_carrier) and update the active pointer. Use to create a target; not for switching existing profiles.
What it needs
About 10k tokens when loaded.
What this skill does
Initialize Target Platform Overview This skill authors a new target-platform profile YAML — the write-side of the contract in ../../context/target-platform-contract.md. It uses ../../references/bsp-platforms-catalogue.md as the canonical product / flash-config catalogue and ../../references/platformtemplate.yaml as the field schema. Flow is linear: pick a reference product + flash config, then optionally add custom-carrier details. The two contract cases — reference-only vs reference + custom carrier — are distinguished only by whether the user provides custom-carrier details; there is no up-front mode prompt. Scope is referencedevkit: and customcarrier: only. Sibling skills own the other blocks: bspimage: → jetson-init-image; source: → jetson-init-source; documents: → jetson-link-docs. Outputs: a new target-platform/<name>.yaml and (by default) an updated activetarget.yml pointing at it. To switch among already-authored profiles, use sibling jetson-set-target. When to invoke The user asks to create / author / add a new target platform profile. A downstream skill refused with "no active target" and target-platform/ contains no profile YAML files yet (otherwise prefer jetson-set-target). The user wants a target whose profile does not yet exist on disk. Procedure Quick-start prefill mapping Follow the shared quickstartprefill contract. This skill consumes: quickstartprefill.target.activeplatform as the selected catalogue row when it resolves to exactly one product. quickstartprefill.target.customcarrier as the custom-carrier intent. If activeplatform resolves to one catalogue row, use it directly. Do not re-ask reference-product or flash-config questions; use the row's default flash config unless the prefill names a catalogue variant. Ask only when the prefill is missing, invalid, ambiguous, or names an unknown variant. How the skill consumes the template Load ../../references/platformtemplate.yaml once at skill startup and treat it as the schema for prompted blocks. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/jetson-init-target