Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/jetson-customize-uphy
Configure Jetson UPHY lane allocation (uphy0/uphy1-config) on Orin/Thor custom carriers.
Passed 11 of 15 test cases with the skill, and 4 of 15 without it.
and 10 more in the full report
12 fixed4 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When adjusting UPHY lane allocations involving UFS storage controllers on Jetson Orin, which sub-skill should be dispatched to generate the UFS devicetree overlay?
| Checked | Without skill | With skill |
|---|---|---|
| Handles UFS overlay generation directly inline rather than dispatching to a standalone UFS sub-skill. | Missed | Passed |
The instructions your model reads when the skill loads.
Select a UPHY lane allocation on a Jetson custom carrier and edit the
carrier flash-conf fork's ODMDATA="..." to apply the chosen
uphyX-config-N token(s) (plus the UPHY_CONFIG="" clear required for
uphy0-config-6). Kernel-DT alignment per controller is not done
here — after the ODMDATA commit lands, this skill dispatches to the
per-controller skills (/jetson-customize-pcie,
/jetson-customize-mgbe, /jetson-customize-usb), each of which must
compare the chosen allocation against the reference kernel DTB
node-by-node and emit an overlay fragment only when the K-stock value
disagrees with the chosen allocation. Discovery is agentic: options,
lanes, and controllers come from the Adaptation Guide, carrier
schematic, and Module / SoC TRM at run time — never hard-coded. Every
user-visible step renders its data as a markdown table, and the final
summary includes a changes-summary table.
reference_devkit: and
custom_carrier:.<source.root_path>/Linux_for_Tegra/.git initialized
(/jetson-init-source)./jetson-derive-carrier).documents.adaptation_guide ->
documents.bsp_developer_guide -> web fetch -> Step-1 prompt
fallback.custom_carrier: is present, both
documents.custom_carrier_schematic AND
documents.custom_carrier_pinmux_xls are REQUIRED. The skill
refuses to run if either is missing — routing decisions for the
custom carrier cannot be guessed. Reference-devkit-only profiles
(no custom_carrier: block) do not require these.UPHY (unified PHY) is the shared high-speed PHY pool on Tegra264 (Thor)
and Tegra234 (Orin). Lane allocation is selected by ODMDATA tokens
test cases passed, vs 4 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.