Jetson Set Target
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Workflow
- Automation and integrations
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The jetson-set-target skill manages the active target platform configuration for Jetson development environments. It acts as a switcher, allowing users to select from existing profile YAML files located in the target-platform directory. The skill ensures that the active_target.yml file is updated correctly while preserving existing file headers, and it provides a clear summary of the selected profile to ensure the user is aware of the current configuration before proceeding with downstream tasks like building or flashing.
What it does
- Lists available Jetson target platform profiles from the target-platform directory.
- Displays a summary of each profile, including hardware details and flash configurations.
- Updates the active_target.yml file to point to the user-selected profile.
- Preserves the existing comment header in the active_target.yml file during updates.
- Validates that the selected profile exists before modifying the pointer.
- Provides a mechanism to recreate the active_target.yml file if it is missing.
When to use it
- When you need to switch between different Jetson hardware targets that already have profile files.
- When a downstream Jetson skill reports that no active target is set.
- When you want to verify which Jetson target profile is currently active.
- When you have multiple target profiles and need to change the active one before a build or flash operation.
Advantages
- Prevents accidental configuration errors by verifying profile existence before switching.
- Maintains consistency in the development environment by centralizing target selection.
- Provides clear visibility into the current active target and available alternatives.
- Safeguards existing file metadata by preserving headers in the configuration pointer.
Usage examples
- “Switch my active target to the Orin Nano profile.”
- The agent lists the available profiles, identifies the Orin Nano match, confirms the selection, and updates active_target.yml to point to the corresponding YAML file.
- “Which Jetson target is currently active?”
- The agent reads active_target.yml and reports the currently active profile name and its associated hardware details.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/jetson-set-target/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-set-target.zip -d .agents/skills
Documentation by Jetson Team
Set Target Platform
Overview
This skill is the switcher side of the target-platform contract in
../../context/target-platform-contract.md. It only
edits target-platform/active_target.yml; it never authors a new
profile YAML. To author a new profile, use the sibling skill
jetson-init-target.
Single output: target-platform/active_target.yml updated to point at
the user's chosen existing profile.
When to invoke
The user asks to switch / change / activate a different target platform among profiles that already exist.
A downstream skill refused with "no active target" and
target-platform/already contains one or more profile YAMLs.The user names a target by filename or product, and that profile YAML is already on disk.
If target-platform/ is missing, empty, or contains only
active_target.yml, stop and tell the user to run jetson-init-target
first.
Procedure
Survey the profiles directory
Read
target-platform/active_target.yml(treat a missing file asactive: NAfor the purposes of this skill — the file will be created in the "Update the active pointer" step if needed, preserving the template header).List
target-platform/*.yaml, excludingactive_target.ymlitself.
| Situation | Action |
|---|---|
| No profile YAMLs exist | Refuse. Tell the user to run jetson-init-target to author one. |
| Exactly one profile, already active | Tell the user it is already active; no change needed. Stop. |
| Exactly one profile, not active | Confirm with the user, then jump to the "Update the active pointer" step with that profile selected. |
| Multiple profiles | Proceed to the "Show the list" step. |
Show the list
Print the profiles in alphabetical order, numbered. Mark the current
active selection with (active) so the user knows what they're
switching from. For each profile, parse its YAML and show a one-line
summary so the user can identify it without opening files: the
reference_devkit.name (or custom_carrier.name if present) plus the
flash_config.
Sample shape:
Profiles in target-platform/:
1) acme-vision-x1.yaml — Acme Vision X1 (custom carrier on AGX Thor T5000) — acme-vision-x1.conf
2) jetson-agx-orin-32gb.yaml — Jetson AGX Orin 32GB — jetson-agx-orin-devkit.conf
3) jetson-agx-thor-devkit.yaml — Jetson AGX Thor T5000 — jetson-agx-thor-devkit.conf (active)
4) jetson-orin-nano-8gb.yaml — Jetson Orin Nano 8GB — jetson-orin-nano-devkit.confIf a profile YAML fails to parse or is missing the expected fields,
show the bare filename with a (unparseable — fix or remove) marker
and skip to the next; do not refuse the whole skill over one bad file.
Prompt for selection
Prompt:
Pick a number, the bare filename, the product name (substring match), or
cancel.
Resolve to a single profile filename. If the user picks the currently active profile, tell them so and stop without rewriting the pointer. If ambiguous, list candidates and ask again.
Update the active pointer
Edit target-platform/active_target.yml:
Set
active: <chosen-filename>.yaml.Preserve the header comment block verbatim — only modify the
active:line.If the file does not exist (it can be missing if the user hand-set up
target-platform/without the bootstrap step), create it from../../references/active_target_template.yamland then setactive:.
Confirm
Print a summary: the previous active value, the new active value, the
chosen profile's reference_devkit.name (and custom_carrier.name if
present), and a reminder that downstream skills (jetson-customize-clocks,
jetson-customize-nvpmodel, jetson-customize-fan,
jetson-optimize-memory) will now resolve to this target.
If a downstream skill triggered this run, tell the user to re-issue their original request; do not silently re-trigger it.
Prerequisites
target-platform/exists and contains at least one*.yamlprofile (excludingactive_target.yml).target-platform/active_target.ymlis present, or the template at../../references/active_target_template.yamlis available so this skill can recreate the pointer.
Limitations
Edits only the
active:line inactive_target.yml; never writes profile YAMLs.Refuses when no profile YAMLs exist — routes the user to
jetson-init-targetinstead.Does not resolve fuzzy product names beyond simple substring match; ambiguous selections are re-prompted.
Troubleshooting
"no profiles found" refusal — the directory has no
*.yamlother than the pointer; run/jetson-init-targetfirst.Pointer rewritten to a missing profile — should not happen because the chosen filename is verified before writing; if seen, hand-edit
active_target.ymlback to a valid filename or rerun with the right selection.Active pointer reads
NA— legitimate "no selection" state; pick any listed profile and the pointer will be set.
Gotchas
No authoring here. If the user names a target whose profile YAML is not on disk, refuse and route them to
jetson-init-target. Do not silently fall through to authoring.Don't edit
active_target.ymlto point at a missing profile. Verify the chosen filename exists intarget-platform/before writing.Preserve
active_target.yml's comment block when editing — only theactive:line should change.Exclude
active_target.ymlfrom the profile list. It lives in the same directory but is the pointer, not a profile.active: NAis the legitimate "no selection" state. Treat it the same as a fresh pointer — don't refuse, just show the list and let the user pick.One-profile shortcut. If only one profile exists, do not skip user confirmation — still confirm before flipping the pointer.
References
../../context/target-platform-contract.md— the contract this skill writes to.../../references/active_target_template.yaml— schema starter for the active-target pointer (used to recreate it if the file is missing).../jetson-init-target/SKILL.md— sibling skill: author a new profile YAML.
Files
- ATTRIBUTION.mdAdded by AutoGineer914 B
- BENCHMARK.md3.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md6.8 KiB
- evals/evals.json3.5 KiB
- skill-card.md3.7 KiB
- skill.oms.sig4.5 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Jetson Team
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/jetson-set-target · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-set-target.zip