[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M787S0AWS3RJRKP04CJ0W2RN":3,"skill-same:01M787S0AWS3RJRKP04CJ0W2RN":73},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":14,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M787S0AWS3RJRKP04CJ0W2RN","jetson-customize-fan",null,"Use when you need to add, remove, edit, list, or change the boot default of an nvfancontrol fan profile on a Jetson\u002FTegra (Orin, Thor) target. Triggers: edit fan profile, tune fan curve.","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-fan\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-customize-fan\ndescription: >-\n  Use when you need to add, remove, edit, list, or change the boot\n  default of an nvfancontrol fan profile on a Jetson\u002FTegra (Orin,\n  Thor) target. Triggers: edit fan profile, tune fan curve.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - thermal\n    - fan\n    - nvfancontrol\n    - profile\n  domain: thermal\n---\n\n# Modify nvfancontrol Fan Profile (BSP-side)\n\n## Purpose\n\nEdit the per-board nvfancontrol configuration so the device boots\nwith the desired fan curve \u002F control mode \u002F governor \u002F default\nprofile. BSP-side only — all writes land in the overlay tracker,\nthe upstream `bsp_image` copy is read-only.\n\nThis skill handles BSP-side edits to the per-board nvfancontrol configuration file: adding profiles, removing profiles, editing the temp → PWM \u002F RPM curves, changing the boot default profile \u002F control mode \u002F governor, and listing defined profiles. Applies on Jetson \u002F Tegra platforms (T234 Orin, T264 Thor).\n\n## File format (canonical, per the BSP file header)\n\n```\nPOLLING_INTERVAL \u003Cseconds>\n\n\u003CFAN \u003Cindex>>\n    TMARGIN \u003CENABLED|DISABLED>\n    FAN_GOVERNOR \u003Ctype> {\n        STEP_SIZE \u003Cint>\n    }\n    FAN_CONTROL \u003Cclose_loop|open_loop> {\n        RPM_TOLERANCE \u003Crpm>\n    }\n    FAN_PROFILE \u003Cname> {\n        # TEMP HYST PWM RPM\n        \u003CT0> \u003CH0> \u003CP0> \u003CR0>\n        ...\n    }\n    FAN_PROFILE \u003Cname> { ... }       # one or more profiles\n    THERMAL_GROUP \u003Cid> {\n        GROUP_MAX_TEMP \u003CC>\n        # zone-name \u003Ccoeffs csv> \u003Cmax-temp>\n        \u003Czone> \u003Ccoeffs> \u003Cmax-temp>\n        ...\n    }\n    FAN_DEFAULT_CONTROL  \u003Cclose_loop|open_loop>\n    FAN_DEFAULT_PROFILE  \u003Cname>\n    FAN_DEFAULT_GOVERNOR \u003Ctype>\n    KICKSTART_PWM \u003C0..255>\n```\n\nRules:\n\n- **Profile curve tuples are 4-column**: `TEMP HYST PWM RPM`. Sort points by ascending `TEMP`; the daemon interpolates between them.\n- **`PWM` is `0..255`** (8-bit duty cycle); **`RPM`** is the close-loop target speed. A trailing `0 0` row at the high end pins the fan off above `GROUP_MAX_TEMP`.\n- **`HYST`** is hysteresis (°C) at that point — the controller waits `HYST` degrees of cooling before stepping the curve down.\n- **`FAN_DEFAULT_PROFILE`** must reference an existing `FAN_PROFILE` block in the same `\u003CFAN N>`. nvfancontrol fails to start if the default names a missing profile.\n- **`FAN_DEFAULT_CONTROL`** = `close_loop` (drives toward target RPM, requires tach) or `open_loop` (writes PWM directly).\n- **`FAN_DEFAULT_GOVERNOR`** = `cont` (continuous interpolation) and other family-specific values; copy verbatim from existing per-board files when introducing one.\n- **`THERMAL_GROUP`** maps thermal zones to the controller's input. Coefficients are a 20-element CSV — copy verbatim from existing entries; values vary by chip family and zone.\n- **`\u003CFAN N>`** is one block per fan index (typical: `\u003CFAN 1>`). Block boundaries `\u003C...>` and `{...}` are strict; preserve indentation matching neighboring lines.\n- **Curves are characterised, not invented.** Add or edit curves from real thermal-acoustic data for the platform; do not interpolate from neighbouring profiles or copy across chip families.\n\n## Prerequisites\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse and route in these cases:\n\n| Condition | Refuse with |\n|---|---|\n| No active profile, or `active: NA` | Route to `\u002Fjetson-set-target` or `\u002Fjetson-init-target`. |\n| Profile lacks `bsp_image:` block | Route to `\u002Fjetson-init-image`. |\n| `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F` missing | Route to `\u002Fjetson-init-image`. |\n| `\u003Csource.root_path>\u002FLinux_for_Tegra\u002F` missing or not a git repo | Route to `\u002Fjetson-init-source`. |\n\nResolve paths:\n\n- `\u003Cbsp_image.root_path>` from `bsp_image.root_path:` if present, else `\u003Cworkspace>\u002FImage`.\n- `\u003Csource.root_path>` from `source.root_path:` if present, else `\u003Cworkspace>\u002FSource`.\n\n`\u003Cbsp_image.root_path>` is **read-only** for this skill; every write lands\nunder `\u003Csource.root_path>` (the overlay tracker). This is the workflow\ninvariant in\n[`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) —\nhand-editing upstream silently destroys the diff trail and makes\n`\u002Fjetson-promote-image` a noop.\n\n## The per-board file\n\nThe conf this skill edits has the relative path:\n\n```\nLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002Fnvfancontrol_\u003Cactive-sku>.conf\n```\n\nIt lives in **two** roots; the skill walks both:\n\n| Role | Location | Skill writes? |\n|---|---|---|\n| Detection + pristine source | `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` | no — read-only |\n| Overlay edit target + git commit | `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` | yes |\n\nSubsequent sections refer to **the per-board file** to mean the overlay copy\nunder `\u003Csource.root_path>`. Operations 1–4 all read, edit, and save against\nthat overlay copy. The `\u003Cbsp_image.root_path>` copy is read once during the\n\"Resolving `\u003Cactive-sku>`\" detection step and once during the\n[Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation)'s\npristine-import step, then never touched again.\n\n### Resolving `\u003Cactive-sku>` — which file to edit\n\nFilename conventions vary per product family:\n\n- `nvfancontrol_\u003Cmodule.id>_\u003Cmodule.sku>.conf` — most Orin parts (e.g. `nvfancontrol_p3767_0000.conf`, `nvfancontrol_p3701_0008.conf`).\n- `nvfancontrol_\u003Cmodule.id>_\u003Cmodule.sku>_\u003Ccarrier.id>_\u003Ccarrier.sku>.conf` — Thor variants where the carrier disambiguates (e.g. `nvfancontrol_p3834_0008_p4071_0000.conf`).\n- `nvfancontrol_\u003Ccarrier>_\u003Csku>_\u003Crev>.conf` — IGX revision variants (e.g. `nvfancontrol_p3740_0002_b01.conf`).\n\nThe nvfancontrol daemon resolves the right file at startup based on the booted hardware's DT compatible plus board IDs (no helper script — it's done inside the binary). To map BSP-side without a running target, against `\u003Cbsp_image.root_path>`:\n\n1. List `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F`.\n2. Filter to filenames that contain `\u003Cmodule.id>_\u003Cmodule.sku>` from the active profile.\n3. If multiple candidates remain, refine with `\u003Ccarrier.id>_\u003Ccarrier.sku>` and (when relevant) the carrier revision tag.\n4. If still ambiguous, run the per-board flash conf dispatch chain to read the kernel DTB's `compatible` and pick the file whose name aligns with the resolved board \u002F carrier.\n5. Verify the chosen file actually exists under `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F`.\n\nDon't blindly compose a filename — the naming convention varies by product family.\n\n### Propagation set — confs to keep in sync\n\nThe active-SKU file is rarely the only conf that should carry a customization. After editing it, **apply the same edit to every sibling in the propagation set** so the change survives regardless of which module \u002F baseboard SKU is booted:\n\n- **The reference platform's nvfancontrol conf** — the upstream conf the active file was forked from (resolve via `reference_devkit` in the active profile, or `jetson-derive-carrier` fork ancestry). For a BSP that contains only the reference (no derived carriers), this is the same file as the active and the rule reduces to a no-op.\n- **Every carrier-derived nvfancontrol conf** — each `nvfancontrol_*.conf` produced by `jetson-derive-carrier` for a custom carrier on top of the same module SKU.\n\n**\"Apply the same edit\" ≠ blanket file copy.** Port the changed `FAN_PROFILE` \u002F control lines into each sibling; preserve every other line. Sibling confs often hold carrier-specific deltas (different `THERMAL_GROUP` coefficients for a different thermal solution, different tach `RPM` ceilings) that must stay intact — a blanket overwrite would mis-tune the fan on those carriers. Blanket-copying is safe **only** when both confs were byte-identical before the edit.\n\n## Overlay edit recipe (apply before any Operation)\n\nFollow the canonical\n[Off-skill edits recipe](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#off-skill-edits)\nin the workflow doc — pristine import + customization commit pair, both\ngated by the preview gate. Apply once per run, covering every per-board\nfile the run touches (the active conf plus every sibling in the\n[Propagation set](#propagation-set--confs-to-keep-in-sync)).\n\nConcrete substitutions for this skill:\n\n- `\u003Crel>\u002F\u003Cfile>` is `rootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`.\n- Suggested pristine-import message:\n  `import pristine: \u003Ccomma-separated rel paths of imported confs>`,\n  body `Source: \u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F (BSP \u003Cbsp_image.version>)`.\n- Suggested customization-commit header:\n  `jetson-customize-fan: \u003Csummary>`,\n  body lines like `nvfancontrol_p3767_0000.conf: added FAN_PROFILE static (open-loop, PWM=255 flat), FAN_DEFAULT_CONTROL close_loop -> open_loop, FAN_DEFAULT_PROFILE quiet -> static`.\n\n## Instructions\n\nPick the operation that matches the user's intent and follow the\nmatching subsection. All write-side operations (1–4) must first\napply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation).\n\n- Operation 1 — Add a new fan profile.\n- Operation 2 — Remove a fan profile.\n- Operation 3 — Edit an existing fan profile (curve, hysteresis).\n- Operation 4 — Change the boot default (control \u002F profile \u002F governor).\n- Operation 5 — List defined fan profiles (read-only).\n\nAfter any write-side operation, run the Deploy chain (`## Deploy`)\nto land the change on the device.\n\n## Examples\n\nAdd an aggressive profile to a P3767-0000 (Orin Nano dev kit) target\nand pin it as the boot default:\n\n```\n\u002Fjetson-customize-fan\n> add a profile called \"aggressive\" with the curve {0:255, 40:150, 80:0}\n> set FAN_DEFAULT_PROFILE to aggressive\n```\n\nSoften the fan ramp on the existing `quiet` profile (raise HYST,\nlower mid-PWM):\n\n```\n\u002Fjetson-customize-fan\n> edit FAN_PROFILE quiet — raise HYST to 5 from 30 °C up, drop PWM at 60 °C to 80\n```\n\nList which profiles the active SKU currently defines and which is\nthe boot default:\n\n```\n\u002Fjetson-customize-fan\n> list defined fan profiles\n```\n\n## Operation 1 — Add a new fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, inside the `\u003CFAN N>` block, add a new `FAN_PROFILE \u003Cname> { ... }` between existing profiles. Daemon parse order doesn't matter, but grouping with siblings keeps the file scannable.\n2. Pick `\u003Cname>` lowercase, no whitespace (e.g. `quiet`, `cool`, `aggressive`).\n3. Fill the curve table — 4-column `TEMP HYST PWM RPM` tuples, ascending `TEMP`. End with at least one row above `GROUP_MAX_TEMP` so behavior at over-temp is defined.\n\nExample skeleton:\n\n```\nFAN_PROFILE aggressive {\n    #TEMP HYST PWM RPM\n    0    0    255 6000\n    20   2    255 6000\n    40   2    150 3500\n    60   2    50  1500\n    80   0    0   0\n    105  0    0   0\n}\n```\n\nValidate (see Rules):\n\n- Every `TEMP` lies within `0..GROUP_MAX_TEMP` of the `THERMAL_GROUP`.\n- `PWM` ∈ `[0, 255]`; `RPM` ≤ the platform's tach-reported max (varies by fan part).\n- Tuples are sorted ascending by `TEMP`.\n\nIf you intend the new profile to be the boot default, follow Operation 4.\n\n## Operation 2 — Remove a fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, delete the entire `FAN_PROFILE \u003Cname> { ... }` block including all curve rows and the closing `}`.\n2. If the deleted `\u003Cname>` matches the trailing `FAN_DEFAULT_PROFILE`, point `FAN_DEFAULT_PROFILE` at a remaining profile — otherwise the daemon fails to start.\n3. Search for hard-coded references in the rootfs before declaring the change safe:\n   ```bash\n   grep -rn \"nvfancontrol.*profile\\|FAN_PROFILE\" \\\n     Linux_for_Tegra\u002Frootfs\u002Fetc 2>\u002Fdev\u002Fnull\n   ```\n\nThe remaining profiles do not need renaming.\n\n## Operation 3 — Edit an existing fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, modify the curve rows of the target `FAN_PROFILE \u003Cname>`. Keep the 4-column `TEMP HYST PWM RPM` shape.\n2. Maintain ascending `TEMP` ordering; insert or remove rows as needed.\n3. Adjust `HYST` to tune anti-oscillation: too low → fan thrashes near a curve point; too high → fan lags reality.\n4. Validate per Operation 1's rules.\n\nEdits to `KICKSTART_PWM`, `RPM_TOLERANCE` (inside `FAN_CONTROL`), or `STEP_SIZE` (inside `FAN_GOVERNOR`) sit outside the profiles but tune the same fan; same per-board file.\n\n## Operation 4 — Change the boot default\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\nEdit the trailing default lines inside the `\u003CFAN N>` block:\n\n```\nFAN_DEFAULT_CONTROL  \u003Cclose_loop|open_loop>\nFAN_DEFAULT_PROFILE  \u003Cname>\nFAN_DEFAULT_GOVERNOR \u003Ctype>\n```\n\n`FAN_DEFAULT_PROFILE` must reference an existing `FAN_PROFILE` in the same `\u003CFAN N>` block. `FAN_DEFAULT_CONTROL` and `FAN_DEFAULT_GOVERNOR` must reference values the binary supports — copy from existing per-board files when changing.\n\n## Operation 5 — List defined fan profiles\n\nThis is a read-only operation; no overlay-tracker setup is needed. Run\nagainst whichever copy you want to inspect (`\u003Cbsp_image.root_path>\u002F...`\nfor the pristine state, `\u003Csource.root_path>\u002F...` for the post-edit state):\n\n```bash\ngrep -E '^[[:space:]]*FAN_PROFILE ' \u003Cper-board file>\ngrep -E '^[[:space:]]*FAN_DEFAULT_'  \u003Cper-board file>\n```\n\nThe first prints every profile name in the file; the second prints the boot defaults (control \u002F profile \u002F governor).\n\n## Limitations\n\n- BSP-side scope only — this skill never touches a running target's\n  `\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` directly. Live tuning requires\n  reboot via Deploy, or the side-channel `scp + systemctl restart`\n  flow described in `## Deploy`.\n- Edits land in the overlay copy under `\u003Csource.root_path>` only;\n  the `\u003Cbsp_image.root_path>` copy is read-only and is rewritten by\n  `\u002Fjetson-promote-image`. Hand-editing `bsp_image` is silently lost\n  on the next `\u002Fjetson-init-image` re-extract.\n- Curve tuples must reflect characterised thermal-acoustic data for\n  the platform — this skill does not interpolate or copy curves\n  across chip families.\n- Propagation across sibling carriers (same module SKU) is partial\n  by design: only the changed `FAN_PROFILE` \u002F control lines are\n  ported, never a blanket file overwrite, since sibling confs may\n  hold carrier-specific `THERMAL_GROUP` \u002F RPM ceilings.\n- Curve point limits are family-specific; copy verbatim from existing\n  confs when introducing new `THERMAL_GROUP` coefficients or\n  `FAN_DEFAULT_GOVERNOR` values.\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|---|---|---|\n| nvfancontrol.service fails to start after edit | `FAN_DEFAULT_PROFILE` references a profile that was removed or renamed | Set `FAN_DEFAULT_PROFILE` to an existing `FAN_PROFILE \u003Cname>` in the same `\u003CFAN N>`. |\n| Fan thrashes near a curve point | `HYST` too low | Raise `HYST` on the affected row (typical 2–5 °C). |\n| Fan lags reality | `HYST` too high | Lower `HYST` on the affected row. |\n| Fan never spins up at high temp | Curve missing a row above `GROUP_MAX_TEMP`, or trailing `0 0` truncates above ambient | Add a high-temp tuple with non-zero PWM\u002FRPM; pin the over-temp row only above `GROUP_MAX_TEMP`. |\n| Daemon parse error referencing column count | Curve row not 4-column `TEMP HYST PWM RPM` | Restore 4-column shape; remove trailing whitespace and stray columns. |\n| `RPM` target never reached in close-loop | Target above tach-reported max, or `FAN_CONTROL` set to `open_loop` | Lower `RPM` to within the fan's mechanical max, or switch `FAN_DEFAULT_CONTROL` to `close_loop`. |\n| Change vanished after `\u002Fjetson-init-image` re-extract | Edit landed in `\u003Cbsp_image.root_path>` instead of `\u003Csource.root_path>` overlay | Re-apply via the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) so the change is committed in the overlay tracker. |\n| Sibling carrier boots with wrong tach ceiling after propagation | Blanket file copy clobbered carrier-specific `THERMAL_GROUP` \u002F `RPM` rows | Port only the changed lines per [Propagation set](#propagation-set--confs-to-keep-in-sync); restore the carrier's original `THERMAL_GROUP`. |\n\n## Deploy\n\nThe customization commit in the overlay tracker does not reach the device\non its own. The Deploy chain:\n\n1. **`\u002Fjetson-promote-image`** — copies every tracked file in the overlay\n   into `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`. Diff-aware (skip\n   byte-identical); uses `sudo cp -p` for `rootfs\u002F*` destinations.\n2. **`\u002Fjetson-flash-image`** — flashes the updated `bsp_image` to the\n   device.\n3. (Alternate, no flash) Copy `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`\n   directly to the running target's `\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`,\n   then `sudo systemctl restart nvfancontrol.service` (or reboot).\n\nEditing `\u003Csource.root_path>\u002F...` without committing — or editing\n`\u003Cbsp_image.root_path>\u002F...` directly — does nothing for `\u002Fjetson-promote-image`\nand is silently lost on the next `\u002Fjetson-init-image` re-extract.\n","# Modify nvfancontrol Fan Profile (BSP-side)\n\n## Purpose\n\nEdit the per-board nvfancontrol configuration so the device boots\nwith the desired fan curve \u002F control mode \u002F governor \u002F default\nprofile. BSP-side only — all writes land in the overlay tracker,\nthe upstream `bsp_image` copy is read-only.\n\nThis skill handles BSP-side edits to the per-board nvfancontrol configuration file: adding profiles, removing profiles, editing the temp → PWM \u002F RPM curves, changing the boot default profile \u002F control mode \u002F governor, and listing defined profiles. Applies on Jetson \u002F Tegra platforms (T234 Orin, T264 Thor).\n\n## File format (canonical, per the BSP file header)\n\n```\nPOLLING_INTERVAL \u003Cseconds>\n\n\u003CFAN \u003Cindex>>\n    TMARGIN \u003CENABLED|DISABLED>\n    FAN_GOVERNOR \u003Ctype> {\n        STEP_SIZE \u003Cint>\n    }\n    FAN_CONTROL \u003Cclose_loop|open_loop> {\n        RPM_TOLERANCE \u003Crpm>\n    }\n    FAN_PROFILE \u003Cname> {\n        # TEMP HYST PWM RPM\n        \u003CT0> \u003CH0> \u003CP0> \u003CR0>\n        ...\n    }\n    FAN_PROFILE \u003Cname> { ... }       # one or more profiles\n    THERMAL_GROUP \u003Cid> {\n        GROUP_MAX_TEMP \u003CC>\n        # zone-name \u003Ccoeffs csv> \u003Cmax-temp>\n        \u003Czone> \u003Ccoeffs> \u003Cmax-temp>\n        ...\n    }\n    FAN_DEFAULT_CONTROL  \u003Cclose_loop|open_loop>\n    FAN_DEFAULT_PROFILE  \u003Cname>\n    FAN_DEFAULT_GOVERNOR \u003Ctype>\n    KICKSTART_PWM \u003C0..255>\n```\n\nRules:\n\n- **Profile curve tuples are 4-column**: `TEMP HYST PWM RPM`. Sort points by ascending `TEMP`; the daemon interpolates between them.\n- **`PWM` is `0..255`** (8-bit duty cycle); **`RPM`** is the close-loop target speed. A trailing `0 0` row at the high end pins the fan off above `GROUP_MAX_TEMP`.\n- **`HYST`** is hysteresis (°C) at that point — the controller waits `HYST` degrees of cooling before stepping the curve down.\n- **`FAN_DEFAULT_PROFILE`** must reference an existing `FAN_PROFILE` block in the same `\u003CFAN N>`. nvfancontrol fails to start if the default names a missing profile.\n- **`FAN_DEFAULT_CONTROL`** = `close_loop` (drives toward target RPM, requires tach) or `open_loop` (writes PWM directly).\n- **`FAN_DEFAULT_GOVERNOR`** = `cont` (continuous interpolation) and other family-specific values; copy verbatim from existing per-board files when introducing one.\n- **`THERMAL_GROUP`** maps thermal zones to the controller's input. Coefficients are a 20-element CSV — copy verbatim from existing entries; values vary by chip family and zone.\n- **`\u003CFAN N>`** is one block per fan index (typical: `\u003CFAN 1>`). Block boundaries `\u003C...>` and `{...}` are strict; preserve indentation matching neighboring lines.\n- **Curves are characterised, not invented.** Add or edit curves from real thermal-acoustic data for the platform; do not interpolate from neighbouring profiles or copy across chip families.\n\n## Prerequisites\n\nResolve the active profile per\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md).\nRefuse and route in these cases:\n\n| Condition | Refuse with |\n|---|---|\n| No active profile, or `active: NA` | Route to `\u002Fjetson-set-target` or `\u002Fjetson-init-target`. |\n| Profile lacks `bsp_image:` block | Route to `\u002Fjetson-init-image`. |\n| `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F` missing | Route to `\u002Fjetson-init-image`. |\n| `\u003Csource.root_path>\u002FLinux_for_Tegra\u002F` missing or not a git repo | Route to `\u002Fjetson-init-source`. |\n\nResolve paths:\n\n- `\u003Cbsp_image.root_path>` from `bsp_image.root_path:` if present, else `\u003Cworkspace>\u002FImage`.\n- `\u003Csource.root_path>` from `source.root_path:` if present, else `\u003Cworkspace>\u002FSource`.\n\n`\u003Cbsp_image.root_path>` is **read-only** for this skill; every write lands\nunder `\u003Csource.root_path>` (the overlay tracker). This is the workflow\ninvariant in\n[`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#workflow-invariants) —\nhand-editing upstream silently destroys the diff trail and makes\n`\u002Fjetson-promote-image` a noop.\n\n## The per-board file\n\nThe conf this skill edits has the relative path:\n\n```\nLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002Fnvfancontrol_\u003Cactive-sku>.conf\n```\n\nIt lives in **two** roots; the skill walks both:\n\n| Role | Location | Skill writes? |\n|---|---|---|\n| Detection + pristine source | `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` | no — read-only |\n| Overlay edit target + git commit | `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` | yes |\n\nSubsequent sections refer to **the per-board file** to mean the overlay copy\nunder `\u003Csource.root_path>`. Operations 1–4 all read, edit, and save against\nthat overlay copy. The `\u003Cbsp_image.root_path>` copy is read once during the\n\"Resolving `\u003Cactive-sku>`\" detection step and once during the\n[Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation)'s\npristine-import step, then never touched again.\n\n### Resolving `\u003Cactive-sku>` — which file to edit\n\nFilename conventions vary per product family:\n\n- `nvfancontrol_\u003Cmodule.id>_\u003Cmodule.sku>.conf` — most Orin parts (e.g. `nvfancontrol_p3767_0000.conf`, `nvfancontrol_p3701_0008.conf`).\n- `nvfancontrol_\u003Cmodule.id>_\u003Cmodule.sku>_\u003Ccarrier.id>_\u003Ccarrier.sku>.conf` — Thor variants where the carrier disambiguates (e.g. `nvfancontrol_p3834_0008_p4071_0000.conf`).\n- `nvfancontrol_\u003Ccarrier>_\u003Csku>_\u003Crev>.conf` — IGX revision variants (e.g. `nvfancontrol_p3740_0002_b01.conf`).\n\nThe nvfancontrol daemon resolves the right file at startup based on the booted hardware's DT compatible plus board IDs (no helper script — it's done inside the binary). To map BSP-side without a running target, against `\u003Cbsp_image.root_path>`:\n\n1. List `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F`.\n2. Filter to filenames that contain `\u003Cmodule.id>_\u003Cmodule.sku>` from the active profile.\n3. If multiple candidates remain, refine with `\u003Ccarrier.id>_\u003Ccarrier.sku>` and (when relevant) the carrier revision tag.\n4. If still ambiguous, run the per-board flash conf dispatch chain to read the kernel DTB's `compatible` and pick the file whose name aligns with the resolved board \u002F carrier.\n5. Verify the chosen file actually exists under `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F`.\n\nDon't blindly compose a filename — the naming convention varies by product family.\n\n### Propagation set — confs to keep in sync\n\nThe active-SKU file is rarely the only conf that should carry a customization. After editing it, **apply the same edit to every sibling in the propagation set** so the change survives regardless of which module \u002F baseboard SKU is booted:\n\n- **The reference platform's nvfancontrol conf** — the upstream conf the active file was forked from (resolve via `reference_devkit` in the active profile, or `jetson-derive-carrier` fork ancestry). For a BSP that contains only the reference (no derived carriers), this is the same file as the active and the rule reduces to a no-op.\n- **Every carrier-derived nvfancontrol conf** — each `nvfancontrol_*.conf` produced by `jetson-derive-carrier` for a custom carrier on top of the same module SKU.\n\n**\"Apply the same edit\" ≠ blanket file copy.** Port the changed `FAN_PROFILE` \u002F control lines into each sibling; preserve every other line. Sibling confs often hold carrier-specific deltas (different `THERMAL_GROUP` coefficients for a different thermal solution, different tach `RPM` ceilings) that must stay intact — a blanket overwrite would mis-tune the fan on those carriers. Blanket-copying is safe **only** when both confs were byte-identical before the edit.\n\n## Overlay edit recipe (apply before any Operation)\n\nFollow the canonical\n[Off-skill edits recipe](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md#off-skill-edits)\nin the workflow doc — pristine import + customization commit pair, both\ngated by the preview gate. Apply once per run, covering every per-board\nfile the run touches (the active conf plus every sibling in the\n[Propagation set](#propagation-set--confs-to-keep-in-sync)).\n\nConcrete substitutions for this skill:\n\n- `\u003Crel>\u002F\u003Cfile>` is `rootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`.\n- Suggested pristine-import message:\n  `import pristine: \u003Ccomma-separated rel paths of imported confs>`,\n  body `Source: \u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F (BSP \u003Cbsp_image.version>)`.\n- Suggested customization-commit header:\n  `jetson-customize-fan: \u003Csummary>`,\n  body lines like `nvfancontrol_p3767_0000.conf: added FAN_PROFILE static (open-loop, PWM=255 flat), FAN_DEFAULT_CONTROL close_loop -> open_loop, FAN_DEFAULT_PROFILE quiet -> static`.\n\n## Instructions\n\nPick the operation that matches the user's intent and follow the\nmatching subsection. All write-side operations (1–4) must first\napply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation).\n\n- Operation 1 — Add a new fan profile.\n- Operation 2 — Remove a fan profile.\n- Operation 3 — Edit an existing fan profile (curve, hysteresis).\n- Operation 4 — Change the boot default (control \u002F profile \u002F governor).\n- Operation 5 — List defined fan profiles (read-only).\n\nAfter any write-side operation, run the Deploy chain (`## Deploy`)\nto land the change on the device.\n\n## Examples\n\nAdd an aggressive profile to a P3767-0000 (Orin Nano dev kit) target\nand pin it as the boot default:\n\n```\n\u002Fjetson-customize-fan\n> add a profile called \"aggressive\" with the curve {0:255, 40:150, 80:0}\n> set FAN_DEFAULT_PROFILE to aggressive\n```\n\nSoften the fan ramp on the existing `quiet` profile (raise HYST,\nlower mid-PWM):\n\n```\n\u002Fjetson-customize-fan\n> edit FAN_PROFILE quiet — raise HYST to 5 from 30 °C up, drop PWM at 60 °C to 80\n```\n\nList which profiles the active SKU currently defines and which is\nthe boot default:\n\n```\n\u002Fjetson-customize-fan\n> list defined fan profiles\n```\n\n## Operation 1 — Add a new fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, inside the `\u003CFAN N>` block, add a new `FAN_PROFILE \u003Cname> { ... }` between existing profiles. Daemon parse order doesn't matter, but grouping with siblings keeps the file scannable.\n2. Pick `\u003Cname>` lowercase, no whitespace (e.g. `quiet`, `cool`, `aggressive`).\n3. Fill the curve table — 4-column `TEMP HYST PWM RPM` tuples, ascending `TEMP`. End with at least one row above `GROUP_MAX_TEMP` so behavior at over-temp is defined.\n\nExample skeleton:\n\n```\nFAN_PROFILE aggressive {\n    #TEMP HYST PWM RPM\n    0    0    255 6000\n    20   2    255 6000\n    40   2    150 3500\n    60   2    50  1500\n    80   0    0   0\n    105  0    0   0\n}\n```\n\nValidate (see Rules):\n\n- Every `TEMP` lies within `0..GROUP_MAX_TEMP` of the `THERMAL_GROUP`.\n- `PWM` ∈ `[0, 255]`; `RPM` ≤ the platform's tach-reported max (varies by fan part).\n- Tuples are sorted ascending by `TEMP`.\n\nIf you intend the new profile to be the boot default, follow Operation 4.\n\n## Operation 2 — Remove a fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, delete the entire `FAN_PROFILE \u003Cname> { ... }` block including all curve rows and the closing `}`.\n2. If the deleted `\u003Cname>` matches the trailing `FAN_DEFAULT_PROFILE`, point `FAN_DEFAULT_PROFILE` at a remaining profile — otherwise the daemon fails to start.\n3. Search for hard-coded references in the rootfs before declaring the change safe:\n   ```bash\n   grep -rn \"nvfancontrol.*profile\\|FAN_PROFILE\" \\\n     Linux_for_Tegra\u002Frootfs\u002Fetc 2>\u002Fdev\u002Fnull\n   ```\n\nThe remaining profiles do not need renaming.\n\n## Operation 3 — Edit an existing fan profile\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\n1. In the per-board file, modify the curve rows of the target `FAN_PROFILE \u003Cname>`. Keep the 4-column `TEMP HYST PWM RPM` shape.\n2. Maintain ascending `TEMP` ordering; insert or remove rows as needed.\n3. Adjust `HYST` to tune anti-oscillation: too low → fan thrashes near a curve point; too high → fan lags reality.\n4. Validate per Operation 1's rules.\n\nEdits to `KICKSTART_PWM`, `RPM_TOLERANCE` (inside `FAN_CONTROL`), or `STEP_SIZE` (inside `FAN_GOVERNOR`) sit outside the profiles but tune the same fan; same per-board file.\n\n## Operation 4 — Change the boot default\n\nApply the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) first.\n\nEdit the trailing default lines inside the `\u003CFAN N>` block:\n\n```\nFAN_DEFAULT_CONTROL  \u003Cclose_loop|open_loop>\nFAN_DEFAULT_PROFILE  \u003Cname>\nFAN_DEFAULT_GOVERNOR \u003Ctype>\n```\n\n`FAN_DEFAULT_PROFILE` must reference an existing `FAN_PROFILE` in the same `\u003CFAN N>` block. `FAN_DEFAULT_CONTROL` and `FAN_DEFAULT_GOVERNOR` must reference values the binary supports — copy from existing per-board files when changing.\n\n## Operation 5 — List defined fan profiles\n\nThis is a read-only operation; no overlay-tracker setup is needed. Run\nagainst whichever copy you want to inspect (`\u003Cbsp_image.root_path>\u002F...`\nfor the pristine state, `\u003Csource.root_path>\u002F...` for the post-edit state):\n\n```bash\ngrep -E '^[[:space:]]*FAN_PROFILE ' \u003Cper-board file>\ngrep -E '^[[:space:]]*FAN_DEFAULT_'  \u003Cper-board file>\n```\n\nThe first prints every profile name in the file; the second prints the boot defaults (control \u002F profile \u002F governor).\n\n## Limitations\n\n- BSP-side scope only — this skill never touches a running target's\n  `\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F` directly. Live tuning requires\n  reboot via Deploy, or the side-channel `scp + systemctl restart`\n  flow described in `## Deploy`.\n- Edits land in the overlay copy under `\u003Csource.root_path>` only;\n  the `\u003Cbsp_image.root_path>` copy is read-only and is rewritten by\n  `\u002Fjetson-promote-image`. Hand-editing `bsp_image` is silently lost\n  on the next `\u002Fjetson-init-image` re-extract.\n- Curve tuples must reflect characterised thermal-acoustic data for\n  the platform — this skill does not interpolate or copy curves\n  across chip families.\n- Propagation across sibling carriers (same module SKU) is partial\n  by design: only the changed `FAN_PROFILE` \u002F control lines are\n  ported, never a blanket file overwrite, since sibling confs may\n  hold carrier-specific `THERMAL_GROUP` \u002F RPM ceilings.\n- Curve point limits are family-specific; copy verbatim from existing\n  confs when introducing new `THERMAL_GROUP` coefficients or\n  `FAN_DEFAULT_GOVERNOR` values.\n\n## Troubleshooting\n\n| Error | Cause | Solution |\n|---|---|---|\n| nvfancontrol.service fails to start after edit | `FAN_DEFAULT_PROFILE` references a profile that was removed or renamed | Set `FAN_DEFAULT_PROFILE` to an existing `FAN_PROFILE \u003Cname>` in the same `\u003CFAN N>`. |\n| Fan thrashes near a curve point | `HYST` too low | Raise `HYST` on the affected row (typical 2–5 °C). |\n| Fan lags reality | `HYST` too high | Lower `HYST` on the affected row. |\n| Fan never spins up at high temp | Curve missing a row above `GROUP_MAX_TEMP`, or trailing `0 0` truncates above ambient | Add a high-temp tuple with non-zero PWM\u002FRPM; pin the over-temp row only above `GROUP_MAX_TEMP`. |\n| Daemon parse error referencing column count | Curve row not 4-column `TEMP HYST PWM RPM` | Restore 4-column shape; remove trailing whitespace and stray columns. |\n| `RPM` target never reached in close-loop | Target above tach-reported max, or `FAN_CONTROL` set to `open_loop` | Lower `RPM` to within the fan's mechanical max, or switch `FAN_DEFAULT_CONTROL` to `close_loop`. |\n| Change vanished after `\u002Fjetson-init-image` re-extract | Edit landed in `\u003Cbsp_image.root_path>` instead of `\u003Csource.root_path>` overlay | Re-apply via the [Overlay edit recipe](#overlay-edit-recipe-apply-before-any-operation) so the change is committed in the overlay tracker. |\n| Sibling carrier boots with wrong tach ceiling after propagation | Blanket file copy clobbered carrier-specific `THERMAL_GROUP` \u002F `RPM` rows | Port only the changed lines per [Propagation set](#propagation-set--confs-to-keep-in-sync); restore the carrier's original `THERMAL_GROUP`. |\n\n## Deploy\n\nThe customization commit in the overlay tracker does not reach the device\non its own. The Deploy chain:\n\n1. **`\u002Fjetson-promote-image`** — copies every tracked file in the overlay\n   into `\u003Cbsp_image.root_path>\u002FLinux_for_Tegra\u002F`. Diff-aware (skip\n   byte-identical); uses `sudo cp -p` for `rootfs\u002F*` destinations.\n2. **`\u002Fjetson-flash-image`** — flashes the updated `bsp_image` to the\n   device.\n3. (Alternate, no flash) Copy `\u003Csource.root_path>\u002FLinux_for_Tegra\u002Frootfs\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`\n   directly to the running target's `\u002Fetc\u002Fnvpower\u002Fnvfancontrol\u002F\u003Cconf>`,\n   then `sudo systemctl restart nvfancontrol.service` (or reboot).\n\nEditing `\u003Csource.root_path>\u002F...` without committing — or editing\n`\u003Cbsp_image.root_path>\u002F...` directly — does nothing for `\u002Fjetson-promote-image`\nand is silently lost on the next `\u002Fjetson-init-image` re-extract.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":31,"domain":27,"data-classification":32},[27,28,29,30],"thermal","fan","nvfancontrol","profile","Jetson Team","public","main","86cc27ffd16af6cb85948f1155578e6f3f61cc4c","skillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan","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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-fan",{"tool":47,"command":48},"bunx","bunx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-fan",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Solizardking\u002Ftrain2earn --skill jetson-customize-fan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan\u002FSKILL.md",true,[55,61,65,69],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"BENCHMARK.md","REFERENCE","参考文档",3571,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan\u002FBENCHMARK.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"metadata.json",396,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan\u002Fmetadata.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"skill-card.md",3630,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan\u002Fskill-card.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"verification.json",1385,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Ftrain2earn\u002Fblob\u002Fmain\u002Fskillhub\u002Fpublic\u002Fapi\u002Fskills\u002Fnvidia\u002Fjetson-customize-fan\u002Fverification.json",[74,82,90,98,105,113],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]