Jetson Target Switcher
Switch the active Jetson target among existing platform profiles.
The skill narrowly limits changes to the local active: line in active_target.yml, requires confirmation, verifies the selected profile exists, and preserves comments. It handles no sensitive data and performs no external service actions. Points are deducted because atomic writes, backups, and rollback are not specified.
The workflow and failure branches are fairly coherent, covering empty directories, unparseable YAML, ambiguous selections, and missing pointers. Points are deducted because there are no executable tests for this skill, no dependency notes, and no explicit diagnostics for write failures; static review therefore stays at or below 10.
Invocation conditions, accepted inputs, non-authoring boundary, and downstream relationship are clear for developers with existing Jetson profiles, and the core operation does not depend on overseas services. Points are deducted because Chinese-language interaction, detailed environment prerequisites, and broader non-fit cases are not addressed.
The skill includes frontmatter, version, Apache-2.0 licensing, ownership, references, limitations, troubleshooting, and a benchmark report; repository workflows also indicate maintenance and publication paths. Points are deducted for missing recommended Instructions and Examples sections, incomplete author formatting, and no explicit changelog or skill-specific maintenance responsibility.
The core task—selecting an existing profile and updating the active pointer—is clearly defined and the resulting file is directly usable; the benchmark supplies limited correctness and effectiveness signals. Points are deducted because only two tasks were evaluated, there were no negative-trigger cases, and static review cannot confirm actual file modification results.
The SKILL.md, evaluation tasks, expected behaviors, and benchmark report provide auditable material. Points are deducted because there is no skill-specific committed test suite or independent cross-source corroboration, and the benchmark results remain claims that cannot be independently reproduced from the supplied files.
- Before execution, confirm that the target profile exists; this skill only switches the pointer and does not create or repair profiles.
- Automatic rollback is unspecified for interrupted or failed writes; verify the active: line and preserved comments afterward.
- The benchmark covers only two positive tasks and does not establish negative-trigger behavior, write-failure handling, or real-environment compatibility.
What does this skill do, and when should you use it?
jetson-set-target switches the active Jetson target-platform pointer to an existing profile YAML on disk. It reads the current pointer, scans target-platform/ for profile files, presents selectable targets, and updates active_target.yml after selection. It never authors or edits profile YAML files; it changes only the active: line. If no profiles exist, it directs the user to jetson-init-target.
Reads target-platform/active_target.yml, lists and parses target-platform/*.yaml while excluding active_target.yml, sorts and displays profile summaries, accepts a number, bare filename, or product-name substring, verifies the selected file exists, and sets active: in active_target.yml while preserving the header comment block.
- A Jetson BSP developer needs to switch between multiple existing hardware-platform profiles.
- A downstream customization, build, or flash workflow reports no active target while target-platform/ already contains profile YAMLs.
- A user knows the desired Jetson product or profile filename and wants to activate it.
- A workflow needs to change target resolution without modifying the underlying platform profiles.
What are this skill's strengths and limitations?
- Changes only the active pointer, leaving profile YAMLs untouched.
- Verifies that the selected profile exists before writing.
- Supports numbered selection, bare filenames, and product-name substring matching.
- Can recreate a missing pointer file from the documented template while preserving its header.
- Requires at least one existing profile YAML and cannot create profiles itself.
- Product-name matching is limited to simple substring matching; ambiguous choices require another prompt.
- The source does not document a test suite or platform coverage.
- The skill version is 0.0.1.
How do you install this skill?
Install the skill from NVIDIA's collection with the skills CLI:
npx skills add nvidia/skills --skill jetson-set-target --yes
The source does not document the local installation directory. After installation, the client can use the skill when it loads relevant skills.
How do you use this skill?
Example trigger: "Switch the active Jetson target to jetson-agx-orin-32gb.yaml." The skill checks target-platform/ for profiles and shows a numbered list when multiple profiles exist. Selecting the current profile does not rewrite the pointer. If no profile YAML exists, run jetson-init-target first.
How does this skill compare with similar options?
The source explicitly positions jetson-init-target as the alternative for authoring a new profile YAML; jetson-set-target is limited to switching among existing profiles.