Agent skill · software engineering · nvidia
jetson-derive-carrier
Bootstrap a custom carrier board by forking carrier files and scaffolding a DT overlay from the reference devkit. Use after jetson-init-source; not for module-level or kernel-DTB changes.
Why this skill is useful
Provides specific commands and workflows for customizing carrier boards in NVIDIA Jetson environments that the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
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 customcarrier: block, or if <source.rootpath>/LinuxforTegra/.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 OVERLAYDTBFILE. Identifiers (from active profile): <chip> from referencedevkit.module.id via catalogue (unknown → warn, fallback tegra234); <module-id>/<module-sku> from referencedevkit.module; <carrier-id>/<carrier-sku> from referencedevkit.carrier; <custom-id>/<custom-sku>/ <custom-flash-conf> from customcarrier. <real-conf> = readlink <bspimage.rootpath>/LinuxforTegra/<referencedevkit.flashconfig> (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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/jetson-derive-carrier