Jetson Derive Carrier
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The jetson-derive-carrier skill automates the initial setup for custom carrier boards in a Jetson BSP environment. It creates a new board-specific fileset by forking necessary configuration files from a reference devkit and scaffolding a device tree (DT) overlay. This approach ensures that carrier-specific deltas are isolated from the base kernel DTB, allowing for cleaner maintenance and easier updates when the reference BSP changes. The skill manages the creation of flash configurations, BCT files, power management settings, and system registration, while enforcing a strict commit-message preview gate for all changes.
What it does
- Forks and renames board-specific configuration files from a reference devkit to a custom carrier target.
- Scaffolds a new device tree overlay skeleton for the custom carrier board.
- Updates the Makefile to register the new device tree overlay for the build system.
- Configures system power management files including nvpmodel and nvfancontrol for the new hardware.
- Patches nvpower.sh to integrate the custom carrier into the system's power management cascade.
- Appends the new device tree overlay to the flash configuration to ensure it is applied during flashing.
When to use it
- When bringing up a new custom carrier board for a Jetson module.
- After initializing the BSP source code using jetson-init-source.
- When you need to isolate carrier-specific hardware changes from the base module configuration.
- When you want to ensure your custom board configuration follows the standard Jetson BSP customization workflow.
Advantages
- Maintains a clean separation between base module configurations and carrier-specific deltas.
- Automates repetitive file renaming and content substitution tasks.
- Ensures consistency across the boot chain and power management scripts.
- Provides a structured, verifiable process with commit-message previews for every change.
- Simplifies future BSP updates by keeping carrier changes in a dedicated DT overlay.
Usage examples
- “derive custom carrier”
- The agent identifies the custom_carrier block in the active profile and begins the discovery and fork process for the new board files.
- “bootstrap custom carrier”
- The agent verifies the environment, performs a single discovery pass, and prepares the staged commits for the new carrier board.
- “fork carrier board from reference devkit”
- The agent executes the fork plan, creating the necessary renamed files and the DT overlay skeleton while prompting for commit approval.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/jetson-derive-carrier/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-derive-carrier.zip -d .agents/skills
Documentation by Jetson Team
jetson-derive-carrier
Customize first-run gate for any customize-* skill on a custom
carrier. Resolve the active target per
target-platform-contract.md.
Refuse if no custom_carrier: block, or if
<source.root_path>/Linux_for_Tegra/.git is missing
(jetson-init-source first). Template file create/copy rows land in a
single overlay-tracker commit and copy directly to the
custom-carrier-renamed target path — reference-named pristine files
are never staged (see Fork plan for the local rule, which
overrides the standard pristine + customization split from the
workflow);
conf-chain discovery follows
per-board conf dispatch.
Kernel base DTB is not forked — carrier deltas layer as a DT
overlay wired via OVERLAY_DTB_FILE.
Identifiers (from active profile): <chip> from
reference_devkit.module.id via
catalogue (unknown →
warn, fallback tegra234); <module-id>/<module-sku> from
reference_devkit.module; <carrier-id>/<carrier-sku> from
reference_devkit.carrier; <custom-id>/<custom-sku>/
<custom-flash-conf> from custom_carrier. <real-conf> =
readlink <bsp_image.root_path>/Linux_for_Tegra/<reference_devkit.flash_config>
(NVIDIA convention <devkit>.conf → <carrier>-<module>-a<rev>.conf;
warn + treat top-level as real + skip symlink-wrapper row if not a
symlink).
<custom-id> is a custom carrier board token, not necessarily an
NVIDIA-style pNNNN ID. Use it verbatim in dash-form filenames and DT
compatible strings. When a target file family uses p-stripped numeric
tokens, derive <custom-id-file-token> as NNNN only if <custom-id>
matches ^p[0-9]{4}$; otherwise use <custom-id> unchanged. Do not
reject custom carrier IDs merely because they do not start with p.
Instructions
The fork plan below is the instruction set: one discovery pass, then a
row-by-row fork of the per-board fileset, gated by the commit-message
preview before each git commit.
Fork plan
Every git commit produced by this skill — in the overlay tracker
(Linux_for_Tegra/) or the hardware/ source repo — runs through
the
commit message preview gate.
Surface the staged file list + proposed message to the operator
and require accept / edit / cancel before each git commit; on
cancel leave the index staged for manual resolution.
Materialize renamed forks even when bytes do not change. For every accepted fork-plan row, create and track the custom-carrier target path; do not skip a missing target because the fork is only a rename/copy or is byte-identical to the reference. This includes BCT forks such as pinmux, GPIO/GPIOINT, padvoltage/PMC, misc, and MB2 misc. Skip only when the Acceptance column allows it, the source is an explicit warn-and-skip miss, or the expected target path is already tracked; in the last case, report it as already derived and do not create an empty commit.
Template file create/copy rows squash into one overlay-tracker
commit, and reference-named pristine files are never staged. All
rows that materialize a new (template-derived) file in the overlay
tracker — board flash-conf, flash-conf symlink, MB1 BCT (pinmux,
GPIO/GPIOINT, padvoltage/PMC, misc), MB2 BCT (misc), BPMP DTB (when
opted in), nvpmodel, nvfancontrol — copy directly from
<bsp_image.root_path>/Linux_for_Tegra/<rel>/<reference-name> to
<source.root_path>/Linux_for_Tegra/<rel>/<custom-name> with any
content edits applied before staging. The reference-named
(<carrier-id>-<carrier-sku>-keyed) filename is never staged or
committed in the overlay tracker — only the custom-carrier-renamed
file is tracked. This overrides the standard pristine + customization
split from
commit batching.
All such rows land in a single overlay-tracker commit that adds:
(i) the custom-carrier-named files at their target paths with content
already applied, (ii) the flash-conf symlink, and (iii) the targeted
flash-conf content rewrites inside the renamed flash-conf for
PINMUX_CONFIG / GPIO_CONFIG / GPIOINT_CONFIG / PMC_CONFIG /
MISC_CONFIG / MB2_BCT (plus BPFDTB_FILE when BPMP DTB is opted
in). Rows that edit existing upstream files instead of creating
templates — the nvpower.sh patch — and the overlay wire-up
(OVERLAY_DTB_FILE+= append to the just-created flash-conf fork,
treated as a temporally distinct phase per
commit batching)
remain separate commits per their own rows. The DT overlay skeleton
commits in bsp_sources/hardware/, not the overlay tracker, so it is
unaffected. The commit message preview gate fires once on the
squashed commit; warn-and-skipped rows do not contribute, and if every
row in the bundle is already tracked the commit is omitted entirely.
Discovery (single batched pass)
Run one discovery pass; do not interleave with staging. Do not
truncate listings — every candidate filename in each scanned
directory must be visible to the matcher. head, tail, | head -N,
| tail -N, and any other row-limiting filter are out of bounds for
this step; use ls -1 / find unclipped, or grep on the full output.
Truncating risks false warn-and-skip calls when the matching file
sits past the cutoff. Capture:
Flash-conf vars:
DTB_FILE/TBCDTB_FILE/BPFDTB_FILE/PINMUX_CONFIG/PMC_CONFIG/GPIO_CONFIG/GPIOINT_CONFIG.DTB_FILE/TBCDTB_FILEare captured for reference only so the overlay wire-up can derive<dtb-stem>for the overlay filename — they are never rewritten by this skill.BCT
.dtsatbootloader/generic/BCT/;.dtsisiblings live one level up atbootloader/— NOT alongside.nvpmodel:
nvpmodel_<module-id>_<module-sku>*.conf. nvfancontrol:nvfancontrol_<module-id>_<module-sku>_<carrier-id>_<carrier-sku>.conf.nvpower.shanchors for (a)–(d):<carrier-id>cvb branch,<module-id>-<module-sku>SKUelif,tegra<chip>nvpmodel cascade,tegra<chip>nvfancontrol cascade.
| File / category | Discovery | Acceptance | Fork rule |
|---|---|---|---|
| Board flash conf | <real-conf> | Always | Filename sub <carrier-id>-<carrier-sku> → <custom-id>-<custom-sku>. Content sub is targeted, not blanket: rewrite RHS only for vars whose file this skill forks — PINMUX_CONFIG, PMC_CONFIG, GPIO_CONFIG / GPIOINT_CONFIG, MISC_CONFIG, MB2_BCT. Other carrier-keyed vars (DTB_FILE, TBCDTB_FILE, SCR_CONFIG, PMIC_CONFIG, DEVICEPROD_CONFIG, PROD_CONFIG, MINRATCHET_CONFIG, UPHY_CONFIG, dynamic OVERLAY_DTB_FILE+=) MUST stay at reference values — their files aren't forked here and a blanket sed would point them at nonexistent files. DTB_FILE / TBCDTB_FILE specifically: base DTB is not forked; the overlay row appends a new OVERLAY_DTB_FILE+= line instead. BPFDTB_FILE: opt-in extra commit. Never touch <chip>, <module-id>, xxxx. |
| Flash-conf symlink | Unconditional | Always (skip if <real-conf> not a symlink) | New symlink <custom-flash-conf> → flash-conf fork |
| MB1 BCT pinmux | PINMUX_CONFIG + #include follow ¶ | Always | Rename rule † |
| MB1 BCT GPIO | GPIO_CONFIG/GPIOINT_CONFIG + #include follow ¶ | Always | Rename rule † |
| MB1 BCT padvoltage | PMC_CONFIG + #include follow ¶ | Always | Rename rule † |
| MB1 BCT misc | MISC_CONFIG + #include follow ¶ | Always | Rename rule † |
| MB2 BCT misc | MB2_BCT + #include follow ¶ | Always | Rename rule † |
| Kernel DTB + source DTS | (reference only — see header) | Never forked | Base DTB stays at reference. No pristine binary copy in the overlay tracker; no source DTS fork in bsp_sources/hardware/. Carrier deltas live entirely in the DT overlay (next row). |
| DT overlay skeleton (NEW) | Unconditional | Always | Create <source.root_path>/hardware/nvidia/<chip>/nv-public/overlay/<chip>-<custom-id>-<custom-sku>+<module-id>-<module-sku>.dts (skeleton ‡); commit in hardware/, push to origin |
| Per-dir Makefile registration | <source.root_path>/bsp_sources/hardware/nvidia/<chip>/nv-public/overlay/Makefile | Always | Append dtbo-y += <chip>-<custom-id>-<custom-sku>+<module-id>-<module-sku>.dtbo after the last literal-named dtbo-y += entry (BEFORE the $(addprefix $(makefile-path)/,$(dtbo-y)) prefix block — inserting after dtbo-y += $(old-dtbo) silently drops the .dtbo). Same position-sensitive idiom and snippet as the composite slot's Makefile patch in ../jetson-build-source/references/composite-registration.md#makefile-patch-idempotent-position-sensitive. Commit in hardware/. Without this row, nvidia-dtbs never produces the .dtbo referenced by the next row's OVERLAY_DTB_FILE+= line and flash.sh aborts mid-flash on the missing file. |
| Overlay wire-up | Unconditional | Always | Append OVERLAY_DTB_FILE+=",<chip>-<custom-id>-<custom-sku>+<module-id>-<module-sku>.dtbo" to flash-conf fork (extra commit) |
| nvpmodel config | rootfs/etc/nvpmodel/nvpmodel_<module-id-num>_<module-sku>.conf | Always | Filename: append _<custom-id-file-token>_<custom-sku> |
| nvfancontrol config | rootfs/etc/nvpower/nvfancontrol/nvfancontrol_<module-id-num>_<module-sku>_<carrier-id-num>_<carrier-sku>.conf | Always | Filename: substitute carrier portion (append _<custom-id-file-token>_<custom-sku> if source is module-keyed only) |
nvpower.sh patch | rootfs/etc/systemd/nvpower.sh | Always | Pristine + single customization commit with 4 insertions: (a) cvb cascade elif [[ "${machine}" =~ "<custom-id>" ]]; then cvb="<custom-id-file-token>" before reference; (b) inside module-SKU branch set machine="<module-id>-<module-sku>-<custom-id>-<custom-sku>"; (c) nvpmodel cascade branch for composite machine key → conf_file= nvpmodel fork; (d) cvb-keyed nvfancontrol cascade branch → conf_file= nvfancontrol fork |
| BPMP DTB | prebuilt at bootloader/generic/<BPFDTB_FILE> (alt naming: no p prefix, xxxx SKU) | Opt-in y/N, default N — module-level, usually shared with reference | Fork binary: pristine + filename sub -<carrier-id-num>- → -<custom-id-file-token>- (content unchanged). Extra commit on flash-conf fork rewriting BPFDTB_FILE to the renamed binary. |
¶ #include follow. Scan each captured .dts for #include "..." directives anywhere in the file (NVIDIA BSPs put them
inside BCT node bodies); carrier-keyed includes join the fork list.
Stop at one level.
† Rename rule. Carrier-keyed source (e.g.
…-p3834-xxxx-p4071-0000.dts) → filename sub
<carrier-id>-<carrier-sku> → <custom-id>-<custom-sku>; rewrite the
flash-conf variable (e.g. PINMUX_CONFIG) to the renamed filename in
the same customization commit. Module portion is preserved
verbatim from pristine — if pristine has p3834-xxxx, fork keeps
p3834-xxxx; if pristine has p3834-0008, fork keeps p3834-0008.
Never pin module-SKU on your own. Same rule for any other xxxx
wildcard in the carrier-SKU position when pristine uses it (e.g.
p4071-xxxx → p1234-xxxx). Module-keyed
source (e.g. …-p3767-dp-a03.dtsi) → append
_<custom-id-file-token>_<custom-sku> (underscore-form) or
-<custom-id>-<custom-sku> (dash-form) plus an extra commit on
flash-conf fork rewriting the variable (e.g. PINMUX_CONFIG) to the
suffixed name. Content never substituted by default; prompt if
content holds a literal carrier-id-sku self-reference.
‡ Overlay skeleton. DT plugin overlay (/plugin/;) with one
fragment@0 at target-path = "/"; inside __overlay__ set
model = "<custom_carrier.name> carrier board" and compatible = "nvidia,<custom-id>-<custom-sku>+<module-id>-<module-sku>", "nvidia,<chip>". nvpower.sh machine narrowing reads compatible.
Edit verification
Re-grep after every sed / patch. sed silently no-ops on miss;
exit code 0 proves nothing. Multi-line replacements: use Python
str.replace(old, new), not multi-line sed (brittle to whitespace
drift, silent no-ops). Refuse to commit on verification miss.
Summary. Print forks per repo (count + commit SHAs), BPMP-DTB decision, warn-and-skipped rows (mandatory source file missing on this BSP — don't fail the run), overlay path written.
Examples
Trigger phrases the operator might use:
derive custom carrier
bootstrap custom carrier
fork carrier board from reference devkitMinimal custom_carrier: block in the active profile that the skill
expects to find:
custom_carrier:
id: p1234 # any token; need not be NVIDIA pNNNN style
sku: 0000
flash_config: p1234.conf
name: Acme Custom CarrierPurpose
Customize the per-board fileset for a new carrier board so downstream
customize-* skills, nvpower.sh, and the boot chain land on the
custom carrier instead of the reference devkit. Base DTB stays at the
reference; carrier deltas live in a DT overlay so a re-derive against
a new reference BSP only needs to re-run this skill.
Prerequisites
Active profile resolved per
target-platform-contract.mdwith acustom_carrier:block (id, sku, flash-conf, friendly name).source.root_path/Linux_for_Tegra/.gitinitialized — run/jetson-init-sourcefirst; this skill refuses if the overlay tracker is missing.bsp_image.root_pathpopulated by/jetson-init-imageso the reference flash-conf symlink can be resolved.reference_devkit:populated (module + carrier) so the rename rule has carrier-id/sku tokens to substitute away from.
Limitations
Kernel base DTB and its source DTS are not forked — carrier deltas must layer through the DT overlay wired via
OVERLAY_DTB_FILE.BPMP DTB fork is opt-in (default OFF). Most carrier swaps share the reference BPMP DTB; only opt in when board power/clock topology diverges.
Flash-conf content substitution is targeted, not blanket. Vars whose files this skill does not fork (
DTB_FILE,TBCDTB_FILE,SCR_CONFIG,PMIC_CONFIG,DEVICEPROD_CONFIG,PROD_CONFIG,MINRATCHET_CONFIG,UPHY_CONFIG, dynamicOVERLAY_DTB_FILE+=) stay at reference values — rewriting them would point at files that do not exist.Custom-carrier IDs need not follow NVIDIA
pNNNNstyle; the p-stripped numeric token is derived only when the ID matches^p[0-9]{4}$.Does not customize module-level files. Use the relevant
jetson-customize-*skill for pinmux, clocks, fan curves, nvpmodel, PCIe, UPHY, USB, MGBE, or camera deltas.
Troubleshooting
Refuses with "no
custom_carrier:block" — declare the block in the active profile before re-running; the skill will not infer it.Refuses with ".git missing in
Linux_for_Tegra/" — overlay tracker not initialized. Run/jetson-init-sourcefirst."
<real-conf>not a symlink" — NVIDIA convention is a<devkit>.confsymlink to<carrier>-<module>-a<rev>.conf; if the top-level is the real conf, the skill warns, treats it as real, and skips the symlink-wrapper row. Not an error.sedreported success but the edit is missing —sedsilently no-ops on miss. The skill re-greps after every patch and refuses to commit on verification miss; for multi-line replacements switch to Pythonstr.replace."chip: unknown" / fallback to
tegra234— module ID is not in the catalogue; update the catalogue rather than override in the profile.Commit message preview prompt blocks the run — expected gate per commit-batching; accept, edit, or cancel. On cancel the index is left staged for manual resolution.
A mandatory source file is missing on this BSP — the row is recorded as warn-and-skipped in the summary; the rest of the run still completes.
Files
- ATTRIBUTION.mdAdded by AutoGineer926 B
- BENCHMARK.md3.5 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md16.6 KiB
- evals/evals.json5.4 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.
Needs: Needs Node.js
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-derive-carrier · 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-derive-carrier.zip