[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787SJ3HJS13Q9YDC5FSGNMC":3,"skill-same:01M787SJ3HJS13Q9YDC5FSGNMC":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":14,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M787SJ3HJS13Q9YDC5FSGNMC","jetson-customize-pinmux",null,"Per-pin SFIO \u002F direction \u002F initial-state configurator for a Jetson Orin or Thor custom carrier from the pinmux XLSM. Do NOT use for kernel-DT overlay or ODMDATA edits.","Solizardking\u002Ftrain2earn","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786KDC5C3NPE4W44C5641EZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-customize-pinmux\ndescription: >-\n  Per-pin SFIO \u002F direction \u002F initial-state configurator for a Jetson\n  Orin or Thor custom carrier from the pinmux XLSM. Do NOT use for\n  kernel-DT overlay or ODMDATA edits.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - bsp\n    - phase-2\n    - io\n    - pinmux\n  domain: meta\n---\n\n# Customize pinmux (per-pin SFIO \u002F direction \u002F state)\n\n## Overview\n\nThe Tegra pinmux spreadsheet (`.xlsm`) is the ground truth for every\nCVM ball: SoC pin name, supported SFIOs, customer-selected function,\ndirection, and initial state. This skill parses that XLSM, runs a\nper-pin Q1–Q6 interactive loop, and emits the three BCT DTSIs\n(`pinmux`, `gpio`, `padvoltage`) in one shot into the overlay tracker\nat `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F`.\n\nUnlike sibling skills `jetson-customize-uphy` \u002F `jetson-customize-pcie` \u002F\n`jetson-customize-camera`, **pinmux has no kernel-DT overlay surface and no\nODMDATA edit**. The XLSM is the source of truth; the three emitted\nDTSIs land at flash time via the carrier conf's\n`PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` references (which\n`\u002Fjetson-derive-carrier` set up).\n\n**Pad classification (silicon-fixed):** only `BD*` and `BI*` pads have\nconfigurable pull \u002F drive \u002F open-drain attributes. `LP5XA_*`,\n`UPHYDS_*`, `DP_SINGLE_*`, `BDMIPI16X_*`, `BDUSB2_*`, `OSCI27_*` are\nfixed-function and **skip Q4–Q6** (`configurable: no`).\n\nThe bundled `scripts\u002Fmodify_pinmux.py` is the workhorse: it parses\nthe XLSM via `openpyxl>=3.1`, builds the per-carrier pinmap JSON,\ncaptures pin edits into a session shim, and (on `generate`) writes\nthe three DTSIs.\n\n## When to invoke\n\n- The user says \"configure pin\", \"set SFIO\", \"edit pinmux DTSI\",\n  \"set pin direction\", \"set initial state\", or asks to repurpose a\n  CVM ball (e.g. flip a pin between GPIO and a peripheral function).\n- A sibling skill (`jetson-customize-camera`, `jetson-customize-pcie`,\n  `jetson-customize-usb`, `jetson-customize-mgbe`) reports an HSIO pin mismatch\n  via `pin_verifier.py` and the user wants to fix it.\n- The user pre-derived a custom carrier with `\u002Fjetson-derive-carrier`\n  and now wants to author the pinmux from a freshly-edited `.xlsm`.\n\n**Prerequisites:**\n\n- Active profile selected (`target-platform\u002Factive_target.yml` →\n  `\u003Cprofile>.yaml` with `reference_devkit:` AND `custom_carrier:`).\n- `\u003Csource.root_path>\u002FLinux_for_Tegra\u002F` exists as a git repo\n  (`\u002Fjetson-init-source`).\n- `\u002Fjetson-derive-carrier` has run — the three pinmux-side BCT DTSIs\n  (`PINMUX_CONFIG`, `GPIOINT_CONFIG`, `PMC_CONFIG` references in the\n  carrier conf) exist in the overlay tracker.\n- A pinmux `.xlsm` is registered in the active profile at\n  `documents.custom_carrier_pinmux_xls` (preferred when custom-carrier-\n  specific) or `documents.ref_devkit_pinmux_xls` (fallback). The\n  bundled `modify_pinmux.py` requires `openpyxl>=3.1`.\n\n## Procedure\n\nSee [`references\u002Fprocedure.md`](references\u002Fprocedure.md) for the full\nstep-by-step procedure (Steps 1–8). Summary:\n\n1. **Resolve active target + XLSM.** Validate active profile,\n   `custom_carrier:`, overlay-tracker prerequisites; resolve the\n   pinmux `.xlsm` path from\n   `documents.custom_carrier_pinmux_xls` →\n   `documents.ref_devkit_pinmux_xls` → single XLSM under\n   `documents.root_path` → user prompt.\n2. **Probe.** Run `modify_pinmux.py probe` to parse the XLSM into the\n   per-skill scratch `\u003CKB>\u002Fpinmap\u002F\u003Ccustom-carrier>.json` plus\n   `session.json` shim.\n3. **Lookup.** Resolve a free-form user query (CVM ball, Verilog\n   name, signal, DT pin) via `modify_pinmux.py lookup`; surface\n   supported SFIO list, defaults, and `configurable: yes\u002Fno`.\n4. **Set-pin (HARD GATE — Q1–Q6 via `AskUserQuestion`).** Q1–Q3\n   (`sfio` \u002F `direction` \u002F `initial_state`) always asked; Q4–Q6\n   (`pull` \u002F `drive_type` \u002F `open_drain`) only when\n   `configurable: yes`. `tristate` and `e_input` are derived from\n   `direction`, never asked.\n5. **Generate.** `modify_pinmux.py generate --out-dir\n   \u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F` (root, **not**\n   `bootloader\u002Fgeneric\u002FBCT\u002F` — derive-carrier `.dts` forks live there,\n   do not colocate). Emits:\n   `tegra\u003Csoc>-mb1-bct-{pinmux,gpio,padvoltage}-\u003Ccarrier-key>.dtsi`.\n   **`\u003Ccarrier-key>` comes from the carrier conf's `PINMUX_CONFIG=`\n   reference, NOT the kebab-cased carrier name.**\n6. **Commit (single batched commit per workflow rule).** All three\n   DTSIs are one logical edit → one customization commit. Run the\n   commit-preview gate before each commit.\n7. **Run-state sidecar + session shim.** Write the user-facing\n   `\u003Cprofile-stem>.jetson-customize-pinmux.json` sidecar and the\n   transient `session.json` shim under\n   `\u003Cworkspace>\u002Ftarget-platform\u002F`.\n8. **Summary.** Emit the standard one-line + table summary.\n\n## Gotchas\n\n- **No kernel-DT overlay; no `OVERLAY_DTB_FILE` edit; no\n  `render_conf.py` hand-off.** This skill ends at the three BCT\n  DTSIs — the carrier conf already references them via\n  `PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` (set up by\n  `\u002Fjetson-derive-carrier`).\n- **Re-point the `.dts` wrapper's `#include` after `generate`.**\n  `\u002Fjetson-derive-carrier` forks the `.dts` wrappers at\n  `bootloader\u002Fgeneric\u002FBCT\u002F`, but their `#include` lines may still\n  pull the upstream devkit `.dtsi` (e.g.\n  `…-p3834-xxxx-p4071-0000.dtsi`). After `generate` writes the new\n  `\u003CCARRIER_KEY>.dtsi` to `bootloader\u002F` root, edit each wrapper's\n  `#include` to the new filename — by **bare basename**\n  (`#include \"tegra\u003Csoc>-mb1-bct-pinmux-\u003CCARRIER_KEY>.dtsi\"`), not\n  `..\u002F..\u002F…` filesystem-relative. The BCT build's `cpp -I bootloader\u002F`\n  resolves bare basenames; that's the convention every other BCT\n  include in the tree follows. Roll the wrapper edits into the same\n  customization commit as the three DTSIs. See `references\u002Fprocedure.md`\n  Step 5 (\"Sanity-check the carrier `.dts` wrapper\").\n- **Q4–Q6 gated on `configurable: yes`.** Asking pull \u002F drive_type \u002F\n  open_drain on a fixed-function pad (`LP5XA_*`, `UPHYDS_*`,\n  `BDMIPI16X_*`, etc.) is silently dropped by the script and confuses\n  the user. `lookup` prints `configurable: yes\u002Fno` — always check it\n  before prompting Q4–Q6.\n- **`tristate` and `e_input` are derived, never asked.** `unused` →\n  tristate=ENABLE; `input` \u002F `bidirectional` → enable-input=ENABLE.\n  Exposing them as separate prompts produces inconsistent DTSIs.\n- **`sfio=gpio` requires a parseable `gpio=GPIOn_PD.NN` entry in the\n  pinmap row's `sfio` list.** Pins without one are GPIO-incapable\n  silicon; `set-pin` rejects the call. Surface the rejection — don't\n  silently fall back to a non-GPIO SFIO.\n- **Marker idempotency.** Every per-pin edit carries\n  `\u002F\u002F custom-bsp: pinmux` on the closing brace; gpio default-state\n  entries carry the same marker as a trailing comment. Re-running\n  `generate` must detect and update — never duplicate.\n- **`modify_pinmux.py` is unchanged from the original framework** —\n  it reads its own `session.json` shim under `--kb-dir`. The shim\n  is regenerated each run from the active profile + the user-facing\n  sidecar. Do not hand-edit the shim; it's transient.\n- **Multiple pinmux DTSI variants per Thor module SKU.** Some carrier\n  pins live in a different DTSI variant than the one the carrier\n  conf references. `modify_pinmux.py commit` (legacy patch-in-place\n  flow) tolerates missing per-pin blocks via\n  `pinmux.warnings[]` rather than failing. Surface the warning;\n  point at the alternate DTSI variant.\n- **Don't touch the upstream BSP at `\u003Cbsp_image.root_path>`.** All\n  edits land in `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F` under\n  the pristine + customization commit pattern.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fmodify_pinmux.py` | XLSM parser + per-pin DTSI generator. Invoked via `run_script()` from Steps 3-6 with the subcommand of the current phase. | `probe \\| lookup \\| set-pin \\| apply \\| generate \\| commit [...]` (see `--help`) |\n| `scripts\u002Fgenerate_dtsi.py` | Renders pinmux\u002FGPIO\u002Fpadvoltage DTSI fragments from the bundled session state. Called by `modify_pinmux.py generate`. | `--session \u003Cpath> --out-dir \u003Cdir>` |\n\nInvoke from the skill body as a subprocess via `run_script()`:\n\n```bash\n# run_script: probe the carrier pinmux XLSM and write a session state\nscripts\u002Fmodify_pinmux.py probe --xlsm carrier.xlsm --session .pinmux-session.json\n\n# run_script: render DTSI fragments from the final session state\nscripts\u002Fmodify_pinmux.py generate --session .pinmux-session.json --out-dir bsp_sources\u002Fpinmux\u002F\n```\n\n## References\n- [`references\u002Fprocedure.md`](references\u002Fprocedure.md) — full Step 1–8\n  procedure prose.\n- [`questions.json`](questions.json) — Q1–Q6 prompt schema consumed\n  by Step 4.\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml) — `documents:` block (`ref_devkit_pinmux_xls`, `custom_carrier_pinmux_xls`).\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) — overlay edit protocol (single-commit per DTSI fork).\n- [`..\u002Fjetson-derive-carrier\u002FSKILL.md`](..\u002Fjetson-derive-carrier\u002FSKILL.md) — must run first; produces the pinmux \u002F gpio \u002F padvoltage DTSI forks this skill edits, and rewrites the carrier conf's `PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` lines to point at them.\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md) — produces the overlay tracker this skill commits into.\n- [`..\u002Fjetson-link-docs\u002FSKILL.md`](..\u002Fjetson-link-docs\u002FSKILL.md) — author the profile's `documents:` block, including the pinmux XLSM bindings.\n","# Customize pinmux (per-pin SFIO \u002F direction \u002F state)\n\n## Overview\n\nThe Tegra pinmux spreadsheet (`.xlsm`) is the ground truth for every\nCVM ball: SoC pin name, supported SFIOs, customer-selected function,\ndirection, and initial state. This skill parses that XLSM, runs a\nper-pin Q1–Q6 interactive loop, and emits the three BCT DTSIs\n(`pinmux`, `gpio`, `padvoltage`) in one shot into the overlay tracker\nat `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F`.\n\nUnlike sibling skills `jetson-customize-uphy` \u002F `jetson-customize-pcie` \u002F\n`jetson-customize-camera`, **pinmux has no kernel-DT overlay surface and no\nODMDATA edit**. The XLSM is the source of truth; the three emitted\nDTSIs land at flash time via the carrier conf's\n`PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` references (which\n`\u002Fjetson-derive-carrier` set up).\n\n**Pad classification (silicon-fixed):** only `BD*` and `BI*` pads have\nconfigurable pull \u002F drive \u002F open-drain attributes. `LP5XA_*`,\n`UPHYDS_*`, `DP_SINGLE_*`, `BDMIPI16X_*`, `BDUSB2_*`, `OSCI27_*` are\nfixed-function and **skip Q4–Q6** (`configurable: no`).\n\nThe bundled `scripts\u002Fmodify_pinmux.py` is the workhorse: it parses\nthe XLSM via `openpyxl>=3.1`, builds the per-carrier pinmap JSON,\ncaptures pin edits into a session shim, and (on `generate`) writes\nthe three DTSIs.\n\n## When to invoke\n\n- The user says \"configure pin\", \"set SFIO\", \"edit pinmux DTSI\",\n  \"set pin direction\", \"set initial state\", or asks to repurpose a\n  CVM ball (e.g. flip a pin between GPIO and a peripheral function).\n- A sibling skill (`jetson-customize-camera`, `jetson-customize-pcie`,\n  `jetson-customize-usb`, `jetson-customize-mgbe`) reports an HSIO pin mismatch\n  via `pin_verifier.py` and the user wants to fix it.\n- The user pre-derived a custom carrier with `\u002Fjetson-derive-carrier`\n  and now wants to author the pinmux from a freshly-edited `.xlsm`.\n\n**Prerequisites:**\n\n- Active profile selected (`target-platform\u002Factive_target.yml` →\n  `\u003Cprofile>.yaml` with `reference_devkit:` AND `custom_carrier:`).\n- `\u003Csource.root_path>\u002FLinux_for_Tegra\u002F` exists as a git repo\n  (`\u002Fjetson-init-source`).\n- `\u002Fjetson-derive-carrier` has run — the three pinmux-side BCT DTSIs\n  (`PINMUX_CONFIG`, `GPIOINT_CONFIG`, `PMC_CONFIG` references in the\n  carrier conf) exist in the overlay tracker.\n- A pinmux `.xlsm` is registered in the active profile at\n  `documents.custom_carrier_pinmux_xls` (preferred when custom-carrier-\n  specific) or `documents.ref_devkit_pinmux_xls` (fallback). The\n  bundled `modify_pinmux.py` requires `openpyxl>=3.1`.\n\n## Procedure\n\nSee [`references\u002Fprocedure.md`](references\u002Fprocedure.md) for the full\nstep-by-step procedure (Steps 1–8). Summary:\n\n1. **Resolve active target + XLSM.** Validate active profile,\n   `custom_carrier:`, overlay-tracker prerequisites; resolve the\n   pinmux `.xlsm` path from\n   `documents.custom_carrier_pinmux_xls` →\n   `documents.ref_devkit_pinmux_xls` → single XLSM under\n   `documents.root_path` → user prompt.\n2. **Probe.** Run `modify_pinmux.py probe` to parse the XLSM into the\n   per-skill scratch `\u003CKB>\u002Fpinmap\u002F\u003Ccustom-carrier>.json` plus\n   `session.json` shim.\n3. **Lookup.** Resolve a free-form user query (CVM ball, Verilog\n   name, signal, DT pin) via `modify_pinmux.py lookup`; surface\n   supported SFIO list, defaults, and `configurable: yes\u002Fno`.\n4. **Set-pin (HARD GATE — Q1–Q6 via `AskUserQuestion`).** Q1–Q3\n   (`sfio` \u002F `direction` \u002F `initial_state`) always asked; Q4–Q6\n   (`pull` \u002F `drive_type` \u002F `open_drain`) only when\n   `configurable: yes`. `tristate` and `e_input` are derived from\n   `direction`, never asked.\n5. **Generate.** `modify_pinmux.py generate --out-dir\n   \u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F` (root, **not**\n   `bootloader\u002Fgeneric\u002FBCT\u002F` — derive-carrier `.dts` forks live there,\n   do not colocate). Emits:\n   `tegra\u003Csoc>-mb1-bct-{pinmux,gpio,padvoltage}-\u003Ccarrier-key>.dtsi`.\n   **`\u003Ccarrier-key>` comes from the carrier conf's `PINMUX_CONFIG=`\n   reference, NOT the kebab-cased carrier name.**\n6. **Commit (single batched commit per workflow rule).** All three\n   DTSIs are one logical edit → one customization commit. Run the\n   commit-preview gate before each commit.\n7. **Run-state sidecar + session shim.** Write the user-facing\n   `\u003Cprofile-stem>.jetson-customize-pinmux.json` sidecar and the\n   transient `session.json` shim under\n   `\u003Cworkspace>\u002Ftarget-platform\u002F`.\n8. **Summary.** Emit the standard one-line + table summary.\n\n## Gotchas\n\n- **No kernel-DT overlay; no `OVERLAY_DTB_FILE` edit; no\n  `render_conf.py` hand-off.** This skill ends at the three BCT\n  DTSIs — the carrier conf already references them via\n  `PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` (set up by\n  `\u002Fjetson-derive-carrier`).\n- **Re-point the `.dts` wrapper's `#include` after `generate`.**\n  `\u002Fjetson-derive-carrier` forks the `.dts` wrappers at\n  `bootloader\u002Fgeneric\u002FBCT\u002F`, but their `#include` lines may still\n  pull the upstream devkit `.dtsi` (e.g.\n  `…-p3834-xxxx-p4071-0000.dtsi`). After `generate` writes the new\n  `\u003CCARRIER_KEY>.dtsi` to `bootloader\u002F` root, edit each wrapper's\n  `#include` to the new filename — by **bare basename**\n  (`#include \"tegra\u003Csoc>-mb1-bct-pinmux-\u003CCARRIER_KEY>.dtsi\"`), not\n  `..\u002F..\u002F…` filesystem-relative. The BCT build's `cpp -I bootloader\u002F`\n  resolves bare basenames; that's the convention every other BCT\n  include in the tree follows. Roll the wrapper edits into the same\n  customization commit as the three DTSIs. See `references\u002Fprocedure.md`\n  Step 5 (\"Sanity-check the carrier `.dts` wrapper\").\n- **Q4–Q6 gated on `configurable: yes`.** Asking pull \u002F drive_type \u002F\n  open_drain on a fixed-function pad (`LP5XA_*`, `UPHYDS_*`,\n  `BDMIPI16X_*`, etc.) is silently dropped by the script and confuses\n  the user. `lookup` prints `configurable: yes\u002Fno` — always check it\n  before prompting Q4–Q6.\n- **`tristate` and `e_input` are derived, never asked.** `unused` →\n  tristate=ENABLE; `input` \u002F `bidirectional` → enable-input=ENABLE.\n  Exposing them as separate prompts produces inconsistent DTSIs.\n- **`sfio=gpio` requires a parseable `gpio=GPIOn_PD.NN` entry in the\n  pinmap row's `sfio` list.** Pins without one are GPIO-incapable\n  silicon; `set-pin` rejects the call. Surface the rejection — don't\n  silently fall back to a non-GPIO SFIO.\n- **Marker idempotency.** Every per-pin edit carries\n  `\u002F\u002F custom-bsp: pinmux` on the closing brace; gpio default-state\n  entries carry the same marker as a trailing comment. Re-running\n  `generate` must detect and update — never duplicate.\n- **`modify_pinmux.py` is unchanged from the original framework** —\n  it reads its own `session.json` shim under `--kb-dir`. The shim\n  is regenerated each run from the active profile + the user-facing\n  sidecar. Do not hand-edit the shim; it's transient.\n- **Multiple pinmux DTSI variants per Thor module SKU.** Some carrier\n  pins live in a different DTSI variant than the one the carrier\n  conf references. `modify_pinmux.py commit` (legacy patch-in-place\n  flow) tolerates missing per-pin blocks via\n  `pinmux.warnings[]` rather than failing. Surface the warning;\n  point at the alternate DTSI variant.\n- **Don't touch the upstream BSP at `\u003Cbsp_image.root_path>`.** All\n  edits land in `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Fbootloader\u002F` under\n  the pristine + customization commit pattern.\n\n## Available Scripts\n\n| Script | Purpose | Arguments |\n|---|---|---|\n| `scripts\u002Fmodify_pinmux.py` | XLSM parser + per-pin DTSI generator. Invoked via `run_script()` from Steps 3-6 with the subcommand of the current phase. | `probe \\| lookup \\| set-pin \\| apply \\| generate \\| commit [...]` (see `--help`) |\n| `scripts\u002Fgenerate_dtsi.py` | Renders pinmux\u002FGPIO\u002Fpadvoltage DTSI fragments from the bundled session state. Called by `modify_pinmux.py generate`. | `--session \u003Cpath> --out-dir \u003Cdir>` |\n\nInvoke from the skill body as a subprocess via `run_script()`:\n\n```bash\n# run_script: probe the carrier pinmux XLSM and write a session state\nscripts\u002Fmodify_pinmux.py probe --xlsm carrier.xlsm --session .pinmux-session.json\n\n# run_script: render DTSI fragments from the final session state\nscripts\u002Fmodify_pinmux.py generate --session .pinmux-session.json --out-dir bsp_sources\u002Fpinmux\u002F\n```\n\n## References\n- [`references\u002Fprocedure.md`](references\u002Fprocedure.md) — full Step 1–8\n  procedure prose.\n- [`questions.json`](questions.json) — Q1–Q6 prompt schema consumed\n  by Step 4.\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml) — `documents:` block (`ref_devkit_pinmux_xls`, `custom_carrier_pinmux_xls`).\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) — overlay edit protocol (single-commit per DTSI fork).\n- [`..\u002Fjetson-derive-carrier\u002FSKILL.md`](..\u002Fjetson-derive-carrier\u002FSKILL.md) — must run first; produces the pinmux \u002F gpio \u002F padvoltage DTSI forks this skill edits, and rewrites the carrier conf's `PINMUX_CONFIG=` \u002F `GPIOINT_CONFIG=` \u002F `PMC_CONFIG=` lines to point at them.\n- [`..\u002Fjetson-init-source\u002FSKILL.md`](..\u002Fjetson-init-source\u002FSKILL.md) — produces the overlay tracker this skill commits into.\n- [`..\u002Fjetson-link-docs\u002FSKILL.md`](..\u002Fjetson-link-docs\u002FSKILL.md) — author the profile's `documents:` block, including the pinmux XLSM bindings.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":31,"domain":32,"data-classification":33},[27,28,29,30],"bsp","phase-2","io","pinmux","Jetson Team","meta","public","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 11:52:53",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-pinmux",{"tool":48,"command":49},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-pinmux",{"tool":51,"command":52},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-pinmux","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002FSKILL.md",true,[56,62,66,70,74,80,84,88,92,96],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"BENCHMARK.md","REFERENCE","参考文档",3965,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002FBENCHMARK.md",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"metadata.json",386,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fmetadata.json",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"questions.json",2560,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fquestions.json",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fprocedure.md",17035,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Freferences\u002Fprocedure.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002F_pinmux_common.py","SCRIPT","脚本",8447,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fscripts\u002F_pinmux_common.py",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002F_pinmux_dt.py",9117,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fscripts\u002F_pinmux_dt.py",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fgenerate_dtsi.py",33607,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fscripts\u002Fgenerate_dtsi.py",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fmodify_pinmux.py",30061,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fscripts\u002Fmodify_pinmux.py",{"path":93,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":94,"sourceHtmlUrl":95},"skill-card.md",3632,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fskill-card.md",{"path":97,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":98,"sourceHtmlUrl":99},"verification.json",2363,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-pinmux\u002Fverification.json",[101,109,117,125,132,140],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M78B94RSCAKMH1QS79VE6DG9","testing","For testing with Light Protocol programs and clients on localnet, devnet, and mainnet validation.","MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Ftesting\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M78B81BKY8RX12HETPG8YKWK","qedgen","Formally verify programs by writing Lean 4 proofs. Trigger this skill whenever the user wants to formally verify code, generate Lean 4 proofs, prove properties about algorithms or smart contracts, verify invariants, convert program logic into formal specifications, or anything involving Lean 4 and formal verification. Also trigger when the user mentions \"qedgen\", \"lean proof\", \"formal proof\", \"verify my code\", \"prove correctness\", \"formal verification\", or wants mathematical guarantees about their implementation.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-formal-verification\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M78B7Q7C5K54E01DN83A60KG","solana-dev","Use when user asks to \"build a Solana dapp\", \"write an Anchor program\", \"create a token\", \"debug Solana errors\", \"set up wallet connection\", \"test my Solana program\", \"deploy to devnet\", or \"explain Solana concepts\" (rent, accounts, PDAs, CPIs, etc.). Also use for quick on-chain lookups via public RPC + curl — \"what's the balance of \u003Cwallet>\", \"look up transaction \u003Csig>\", \"token balance for \u003Caccount>\", \"check this address on mainnet\u002Fdevnet\". End-to-end Solana development playbook covering wallet connection, Anchor\u002FPinocchio programs, Codama client generation, LiteSVM\u002FMollusk\u002FSurfpool testing, security checklists, and JSON-RPC curl lookups against public clusters. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana\u002Fclient + @solana\u002Freact-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana\u002Fkit for client\u002FRPC code, and @solana\u002Fweb3-compat for legacy boundaries.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-dev\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M78B7HXD6N6GWKSVRQ8F6Q31","solana-common-errors","Diagnose and fix common Solana development errors — GLIBC mismatches, Anchor version conflicts, cargo build-sbf \u002F platform-tools failures, LiteSVM issues, edition2024 crate pins, RPC airdrops, and Anchor 0.29→0.32 migrations. Use when builds fail, Anchor CLI won't install, or CI breaks on Debian\u002FUbuntu.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fsolana-common-errors\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":136,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M78B6T7YSYWQ0N4DP40QDXEZ","skill-creator","Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":105,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":19},"01M78B1VFT9X5AND7AE1HZPZGF","phantom-wallet-mcp","Execute wallet operations through the Phantom MCP server. Use when the user wants to interact with their Phantom wallet directly — get addresses, transfer SOL or SPL tokens, buy\u002Fswap tokens, sign transactions, and sign messages across Solana, Ethereum, Bitcoin, and Sui. Requires the @phantom\u002Fmcp-server to be configured as an MCP server.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fskills\u002Fphantom-wallet-mcp\u002FSKILL.md",[],[]]