Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 18 of 23 test cases with the skill, and 7 of 23 without it.
and 13 more in the full report
12 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
If all target files in the overlay-tracker template bundle already exist and are tracked in git, what action should be taken for that commit step?
| Checked | Without skill | With skill |
|---|---|---|
| The response omits the commit entirely if all files in the bundle are already tracked. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
The fork plan below is the instruction set: one discovery pass, then a
test cases passed, vs 7 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.