[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPHVVZCGS1H7SK3F8F1JM2":3,"skill-same:01M7CPHVVZCGS1H7SK3F8F1JM2":61},{"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":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7CPHVVZCGS1H7SK3F8F1JM2","jetson-generate-kb",null,"Build a per-target knowledge-base markdown next to the active profile by walking the BSP root and source tree. Use after init-image \u002F init-source; not for editing profile fields.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-generate-kb\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: jetson-generate-kb\ndescription: >-\n  Build a per-target knowledge-base markdown next to the active\n  profile by walking the BSP root and source tree. Use after\n  init-image \u002F init-source; not for editing profile fields.\nversion: 0.0.1\nlicense: \"Apache-2.0\"\nmetadata:\n  data-classification: public\n  author: \"Jetson Team\"\n  tags:\n    - target-platform\n    - knowledge-base\n    - documentation\n    - meta\n  domain: meta\n---\n\n# Generate Target Knowledge Base\n\n## Overview\n\nThis skill produces a **per-profile** markdown reference at\n`target-platform\u002F\u003Cprofile-stem>.md` (sibling to the profile YAML). It\nbundles three things into one file so a future Claude session — or the\nuser — can see the shape of the active target without re-walking the\nfilesystem:\n\n1. **BSP image layout** — top-level directories under\n   `bsp_image.root_path`, presence of canonical subtrees (`rootfs\u002F`,\n   `bootloader\u002F`, `source\u002F`, …), and the nvpmodel variants matching\n   the active module SKU.\n2. **Source tree layout** — top-level subtrees under\n   `source.root_path` (`kernel-jammy-src\u002F`, `hardware\u002Fnvidia\u002F`,\n   `nvidia-oot\u002F`, etc.) and devicetree files matching the chip family.\n3. **Documents** — the `documents.*` references recorded in the\n   profile, with local-path existence checks and one-line descriptions.\n\nThe KB is a **snapshot**, dated in its header. Re-run this skill\nwhenever the underlying data changes — it is intentionally\nre-runnable and overwrites the previous KB on each run.\n\n## When to invoke\n\n- After `jetson-init-image` prepares the BSP for a freshly authored\n  profile.\n- After re-extracting a BSP archive or applying patches under\n  `bsp_image.root_path`.\n- After updating the source tree at `source.root_path`.\n- After editing `bsp_image.*` or `documents.*` in the profile YAML.\n- When a downstream skill asks \"where is X in this BSP?\" and you'd\n  rather check the KB than re-walk the tree.\n\n## Procedure\n\n### Resolve the active target\n\nResolve the active profile per the contract in\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md);\ncache it in memory — the rest of the skill consumes only this\nprofile. Record `\u003Cprofile-stem>` (the bare filename minus `.yaml`)\nas the KB output filename stem.\n\n### Validate inputs\n\n| Field | Required for KB? | If missing |\n|---|---|---|\n| `bsp_image.root_path` | **yes** | Refuse. A KB with no BSP root to scan is just a YAML restatement; tell the user to run `jetson-init-image` or hand-edit the profile. |\n| `source.root_path` | no | Skip the source-tree section; note \"source_root not recorded\" in the KB. |\n| `documents.*` | no | Render an empty Documents table with a \"no documents recorded\" note. |\n\nIf `bsp_image.root_path` is set but the directory does not exist on disk,\nrefuse with a clear message — do not fabricate a layout for a path\nthat isn't there.\n\n### BSP discovery (under `bsp_image.root_path`)\n\nRun **only** the following cheap operations — no recursive scans, no\nfile content reads beyond directory listings:\n\n1. `ls -1` of `bsp_image.root_path` (one level deep). Record which\n   directories are present.\n2. For each canonical subtree below, mark present\u002Fabsent:\n   `rootfs\u002F`, `bootloader\u002F`, `kernel\u002F`, `source\u002F`, `tools\u002F`,\n   `nv_tegra\u002F`.\n3. Verify the active `flash_config` file exists at\n   `\u003Cbsp_image.root_path>\u002F\u003Cflash_config>`. Record its path or\n   `(missing)`.\n4. List `rootfs\u002Fetc\u002Fnvpmodel\u002F` and filter to filenames matching\n   `nvpmodel_\u003Cmodule.id>_\u003Cmodule.sku>*.conf`. Record each match.\n   Use the lower-case module id (e.g. `p3767`) and the YAML-quoted\n   sku string (e.g. `0001`).\n\n### Source tree discovery (under `source.root_path`)\n\nSkip this step entirely if `source.root_path` is `NA` or missing.\nOtherwise, run only:\n\n1. `ls -1` of `source.root_path` (one level deep).\n2. For each canonical subtree below, mark present\u002Fabsent:\n   `kernel-jammy-src\u002F`, `hardware\u002Fnvidia\u002F`, `nvidia-oot\u002F`, `nvgpu\u002F`,\n   `nvethernetrm\u002F`, `nvdisplay\u002F`, `hwpm\u002F`, `kernel-devicetree\u002F`.\n3. If `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F` exists, list filenames\n   matching `tegra\u003Cchip>*` where `\u003Cchip>` is the chip-family numeric\n   prefix (see chip-family map below). Record up to 30 hits; if more,\n   record the count and a \"showing first 30\" note.\n\n#### Chip-family map (used in the \"BSP discovery\" and \"Source tree discovery\" steps)\n\nDerive `\u003Cchip>` from `module.id`:\n\n| `module.id` | Chip family | `\u003Cchip>` prefix |\n|---|---|---|\n| `p3701`, `p3767` | T234 — Orin | `234` |\n| `p3834` | T264 — Thor | `264` |\n\nIf `module.id` is not in this table, record the chip as\n`unknown (module.id=\u003Cvalue>)` and skip the chip-prefixed devicetree\nfilter.\n\n### Documents pass\n\nFor each field in `documents.*` from the loaded profile:\n\n1. Classify the value as **URL** (starts with `http:\u002F\u002F`, `https:\u002F\u002F`,\n   or `ftp:\u002F\u002F`) or **local path** (anything else).\n2. For URLs: record verbatim. **Do not fetch the URL** — KB\n   generation must remain offline. (A future skill can promote to deep\n   indexing.)\n3. For local paths: check `os.path.exists`. Record the path; if\n   missing on disk, append ` (missing)`.\n\nThe one-line description for each field comes from the marker in\n[`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml)\n— strip the `\u003COPTIONAL: …>` wrapper and use the inner text.\n\nIf the profile has no `documents:` block, render the section with a\nsingle line: `_No documents recorded — run `jetson-link-docs`\nor hand-edit the profile to add references._`\n\n### Render and write the KB\n\nRender the markdown using the structure below. Use today's date\n(YYYY-MM-DD) in the header. Always overwrite any existing KB file at\nthe destination — do not prompt before overwriting; re-runs are the\nintended use.\n\nDestination: `target-platform\u002F\u003Cprofile-stem>.md`.\n\n#### Rendered structure\n\n```markdown\n# Target knowledge base — \u003Cprofile-stem>\n\n> Generated \u003CYYYY-MM-DD> from `\u003Cbsp_image.root_path>` (BSP version `\u003Cbsp_image.version>`).\n> Re-run `jetson-generate-kb` after extracting a new BSP, applying\n> patches, or editing profile fields. This file is a regenerated\n> snapshot — do not hand-edit.\n\n## Profile facts\n\n- **Reference devkit:** `\u003Creference_devkit.name>`\n- **Module:** `\u003Cmodule.id>-\u003Cmodule.sku>` (`\u003Cchip family label>`)\n- **Reference carrier:** `\u003Ccarrier.id>-\u003Ccarrier.sku>`\n- **Custom carrier:** `\u003Ccustom_carrier.name>` (`\u003Ccustom_carrier.id>-\u003Ccustom_carrier.sku>`)  _← omit this row if Case 1_\n- **Active flash conf:** `\u003Cflash_config>`\n- **BSP path:** `\u003Cbsp_image.root_path>`\n- **BSP version:** `\u003Cbsp_image.version>`\n- **Source root:** `\u003Csource.root_path>`  _← or \"_not recorded_\" if NA_\n\n## BSP image layout\n\nTop-level directories under `\u003Cbsp_image.root_path>`:\n\n| Directory | Present | Purpose |\n|---|---|---|\n| `rootfs\u002F`     | ✓ \u002F ✗ | userspace rootfs (nvpmodel, nvfan, systemd units, etc.) |\n| `bootloader\u002F` | ✓ \u002F ✗ | firmware blobs, BCT, MB1\u002FMB2 dts |\n| `kernel\u002F`     | ✓ \u002F ✗ | prebuilt kernel + modules |\n| `source\u002F`     | ✓ \u002F ✗ | BSP source tree (kernel, OOT drivers, DT) |\n| `tools\u002F`      | ✓ \u002F ✗ | flashing helpers, jetson-io, kernel_flash |\n| `nv_tegra\u002F`   | ✓ \u002F ✗ | nvidia firmware tarballs, kernel-supplements |\n\nActive flash conf `\u003Cflash_config>`: present at\n`\u003Cbsp_image.root_path>\u002F\u003Cflash_config>` _or_ `(missing — verify before flashing)`.\n\n### nvpmodel files matching the active SKU\n\nFiltered from `rootfs\u002Fetc\u002Fnvpmodel\u002F` by `nvpmodel_\u003Cmodule.id>_\u003Cmodule.sku>*.conf`:\n\n- `\u003Ceach match, one per line>`\n\nThe active variant at boot is selected by `nvpower.sh` from\n`\u002Fproc\u002Fdevice-tree\u002Fcompatible` plus super \u002F safety state — see\n`jetson-customize-nvpmodel` for the resolution rules.\n\n## Source tree layout\n\n(omit this whole section if `source.root_path` is `NA`\u002Fmissing)\n\nTop-level subtrees under `\u003Csource.root_path>`:\n\n| Subtree | Present | Purpose |\n|---|---|---|\n| `kernel-jammy-src\u002F`   | ✓ \u002F ✗ | mainline 5.x kernel sources |\n| `hardware\u002Fnvidia\u002F`    | ✓ \u002F ✗ | NVIDIA platform DTs (per chip family) |\n| `nvidia-oot\u002F`         | ✓ \u002F ✗ | NVIDIA out-of-tree kernel modules |\n| `nvgpu\u002F`              | ✓ \u002F ✗ | GPU driver |\n| `nvethernetrm\u002F`       | ✓ \u002F ✗ | ethernet driver |\n| `nvdisplay\u002F`          | ✓ \u002F ✗ | display driver |\n| `hwpm\u002F`               | ✓ \u002F ✗ | hardware performance monitor |\n| `kernel-devicetree\u002F`  | ✓ \u002F ✗ | devicetree sources |\n\n### Devicetree files for chip family `\u003Cchip>`\n\n(omit if `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F` is absent)\n\nFiles matching `tegra\u003Cchip>*` under `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F`:\n\n- `\u003Ceach match, one per line — cap at 30, then a \"first 30 of N\" note>`\n\n## Documents\n\n| Field | Reference |\n|---|---|\n| Documents root folder                    | `\u003Cdoc_root>`                    _or_ _not recorded_ |\n| BSP \u002F Jetson Linux developer guide       | `\u003Cbsp_developer_guide>`         _or_ _not recorded_ |\n| Tegra SoC Technical Reference Manual     | `\u003Csoc_tech_ref_manual>`         _or_ _not recorded_ |\n| Jetson module data sheet                 | `\u003Cmodule_data_sheet>`           _or_ _not recorded_ |\n| Jetson module design guide (PDG)         | `\u003Cmodule_design_guide>`         _or_ _not recorded_ |\n| Jetson module thermal design guide (TDG) | `\u003Cmodule_thermal_design_guide>` _or_ _not recorded_ |\n| Jetson module schematic                  | `\u003Cmodule_schematic>`            _or_ _not recorded_ |\n| Reference carrier board specification    | `\u003Ccarrier_board_spec>`          _or_ _not recorded_ |\n| Reference carrier schematic              | `\u003Ccarrier_schematic>`           _or_ _not recorded_ |\n| Custom carrier schematic                 | `\u003Ccustom_carrier_schematic>`    _or_ _not recorded \u002F N\u002FA (no custom carrier)_ |\n| Reference-devkit pinmux spreadsheet      | `\u003Cref_devkit_pinmux_xls>`       _or_ _not recorded_ |\n| Custom-carrier pinmux spreadsheet        | `\u003Ccustom_carrier_pinmux_xls>`   _or_ _not recorded \u002F N\u002FA (no custom carrier)_ |\n\n(Local paths are tagged ` (missing)` if absent on disk. URLs are\nrecorded verbatim and not fetched. If `doc_root` is set, also tag\n` (missing)` on it if the directory itself is gone — that signals\nauto-mapping in `jetson-link-docs` won't work on a re-run.)\n\n## How to refresh this file\n\nRe-run `jetson-generate-kb` whenever any of the following changes:\n\n- the BSP at `\u003Cbsp_image.root_path>` is re-extracted, patched, or upgraded,\n- the source tree at `\u003Csource.root_path>` changes,\n- the active profile's `bsp_image.*` or `documents.*` fields are edited.\n\nThis file is overwritten on every run. Do not hand-edit it — edit the\nsource data (profile YAML or the BSP tree) and re-run instead.\n```\n\n### Confirm\n\nPrint a short summary:\n\n- Output path: `target-platform\u002F\u003Cprofile-stem>.md`.\n- BSP top-level directory count and which canonical subtrees were\n  present \u002F absent.\n- nvpmodel match count for the active SKU.\n- Source-tree section: rendered or skipped (and why).\n- Documents: count of recorded fields, count of local paths flagged\n  `(missing)`.\n\nIf a downstream skill triggered this run, tell the user to re-issue\ntheir original request.\n\n## Gotchas\n\n- **The KB is a snapshot, not a live view.** The dated header is\n  authoritative — if it doesn't match today, the BSP\u002Fsource\u002Fdocs may\n  have changed underneath. Re-run on demand.\n- **Always overwrites.** No prompt before clobbering the previous KB\n  at `target-platform\u002F\u003Cprofile-stem>.md`. This is intentional —\n  re-runnability is the whole point. Tell the user not to hand-edit\n  the file; edit profile YAML or the BSP and regenerate.\n- **Refuses on `bsp_image.root_path = NA`.** A profile with no BSP path\n  produces a content-free KB. Do not write one — instead, point the\n  user at the profile YAML to fill in.\n- **No URL fetching.** Document URLs are recorded verbatim. Promoting\n  to deep indexing (HTTP HEAD, PDF parsing) is out of scope for v0.1.\n- **No recursive scans.** Discovery is one level deep per directory,\n  with at most one targeted glob (nvpmodel + devicetree). Never walk\n  the entire BSP — it's huge and slow.\n- **Cap devicetree listings at 30 entries** to keep the KB readable.\n  Show \"first 30 of N\" when truncating.\n- **Don't auto-invoke from setup skills.** Setup may suggest running\n  this skill in its summary, but the user opts in. Auto-running hides\n  the I\u002FO step and surprises users whose BSP\u002Fdoc paths are incomplete.\n- **Filename collision risk.** The KB sits at\n  `target-platform\u002F\u003Cstem>.md` next to `\u003Cstem>.yaml`. Don't accidentally\n  read `.md` files in the profile-listing logic of\n  `jetson-set-target` (it already filters to `*.yaml`, but check\n  before adding new file types).\n- **Chip-family map is short.** If a future module SKU is added that\n  isn't in the map, the devicetree filter step is skipped — the KB\n  will note `chip: unknown` rather than fabricate a `\u003Cchip>` prefix.\n  Update this skill's chip-family table when a new chip lands.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- `bsp_image:` recorded by `\u002Fjetson-init-image`; this is the only\n  required on-disk tree. If `source.root_path` is missing, render the KB\n  without the source-tree section.\n- Optional: `\u002Fjetson-init-source` already resolved `source:` when the\n  user wants source-tree discovery included.\n- Optional but recommended: `\u002Fjetson-link-docs` already wrote the\n  `documents:` block.\n\n## Limitations\n\n- Read-only against the BSP and source trees; never edits the profile\n  YAML or rewrites source files.\n- Devicetree-file enumeration depends on the chip-family table inside\n  this skill; an unknown module SKU lands in the KB as `chip: unknown`\n  rather than a fabricated prefix.\n- Filename layout is fixed at `target-platform\u002F\u003Cstem>.md` to stay next\n  to the profile YAML; renaming the YAML invalidates the link.\n\n## Troubleshooting\n\n- **`bsp_image.root_path` not found** — re-run `\u002Fjetson-init-image` so\n  the BSP is extracted and the path is recorded before regenerating\n  the KB.\n- **Source tree walk picks up wrong subtrees** — `source.root_path`\n  override is stale; rerun `\u002Fjetson-init-source` or correct the\n  profile field.\n- **`documents:` block missing from the KB** — `\u002Fjetson-link-docs` was\n  never run; the KB falls back to \"no documents bound\" rather than\n  guessing paths.\n- **Devicetree section short \u002F empty** — chip-family table doesn't\n  cover the active SoC; update the table and rerun.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md) — read-order contract this skill follows.\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md) — origin of the canonical BSP\u002Fsource subtree list.\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml) — source of the documents-field one-line descriptions.\n- [`..\u002Fjetson-init-target\u002FSKILL.md`](..\u002Fjetson-init-target\u002FSKILL.md) — sibling skill that authors the active target identity.\n- [`..\u002Fjetson-init-image\u002FSKILL.md`](..\u002Fjetson-init-image\u002FSKILL.md) — sibling skill that authors the BSP image metadata this skill scans.\n- [`..\u002Fjetson-set-target\u002FSKILL.md`](..\u002Fjetson-set-target\u002FSKILL.md) — sibling skill that flips the active pointer this skill resolves.\n","# Generate Target Knowledge Base\n\n## Overview\n\nThis skill produces a **per-profile** markdown reference at\n`target-platform\u002F\u003Cprofile-stem>.md` (sibling to the profile YAML). It\nbundles three things into one file so a future Claude session — or the\nuser — can see the shape of the active target without re-walking the\nfilesystem:\n\n1. **BSP image layout** — top-level directories under\n   `bsp_image.root_path`, presence of canonical subtrees (`rootfs\u002F`,\n   `bootloader\u002F`, `source\u002F`, …), and the nvpmodel variants matching\n   the active module SKU.\n2. **Source tree layout** — top-level subtrees under\n   `source.root_path` (`kernel-jammy-src\u002F`, `hardware\u002Fnvidia\u002F`,\n   `nvidia-oot\u002F`, etc.) and devicetree files matching the chip family.\n3. **Documents** — the `documents.*` references recorded in the\n   profile, with local-path existence checks and one-line descriptions.\n\nThe KB is a **snapshot**, dated in its header. Re-run this skill\nwhenever the underlying data changes — it is intentionally\nre-runnable and overwrites the previous KB on each run.\n\n## When to invoke\n\n- After `jetson-init-image` prepares the BSP for a freshly authored\n  profile.\n- After re-extracting a BSP archive or applying patches under\n  `bsp_image.root_path`.\n- After updating the source tree at `source.root_path`.\n- After editing `bsp_image.*` or `documents.*` in the profile YAML.\n- When a downstream skill asks \"where is X in this BSP?\" and you'd\n  rather check the KB than re-walk the tree.\n\n## Procedure\n\n### Resolve the active target\n\nResolve the active profile per the contract in\n[`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md);\ncache it in memory — the rest of the skill consumes only this\nprofile. Record `\u003Cprofile-stem>` (the bare filename minus `.yaml`)\nas the KB output filename stem.\n\n### Validate inputs\n\n| Field | Required for KB? | If missing |\n|---|---|---|\n| `bsp_image.root_path` | **yes** | Refuse. A KB with no BSP root to scan is just a YAML restatement; tell the user to run `jetson-init-image` or hand-edit the profile. |\n| `source.root_path` | no | Skip the source-tree section; note \"source_root not recorded\" in the KB. |\n| `documents.*` | no | Render an empty Documents table with a \"no documents recorded\" note. |\n\nIf `bsp_image.root_path` is set but the directory does not exist on disk,\nrefuse with a clear message — do not fabricate a layout for a path\nthat isn't there.\n\n### BSP discovery (under `bsp_image.root_path`)\n\nRun **only** the following cheap operations — no recursive scans, no\nfile content reads beyond directory listings:\n\n1. `ls -1` of `bsp_image.root_path` (one level deep). Record which\n   directories are present.\n2. For each canonical subtree below, mark present\u002Fabsent:\n   `rootfs\u002F`, `bootloader\u002F`, `kernel\u002F`, `source\u002F`, `tools\u002F`,\n   `nv_tegra\u002F`.\n3. Verify the active `flash_config` file exists at\n   `\u003Cbsp_image.root_path>\u002F\u003Cflash_config>`. Record its path or\n   `(missing)`.\n4. List `rootfs\u002Fetc\u002Fnvpmodel\u002F` and filter to filenames matching\n   `nvpmodel_\u003Cmodule.id>_\u003Cmodule.sku>*.conf`. Record each match.\n   Use the lower-case module id (e.g. `p3767`) and the YAML-quoted\n   sku string (e.g. `0001`).\n\n### Source tree discovery (under `source.root_path`)\n\nSkip this step entirely if `source.root_path` is `NA` or missing.\nOtherwise, run only:\n\n1. `ls -1` of `source.root_path` (one level deep).\n2. For each canonical subtree below, mark present\u002Fabsent:\n   `kernel-jammy-src\u002F`, `hardware\u002Fnvidia\u002F`, `nvidia-oot\u002F`, `nvgpu\u002F`,\n   `nvethernetrm\u002F`, `nvdisplay\u002F`, `hwpm\u002F`, `kernel-devicetree\u002F`.\n3. If `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F` exists, list filenames\n   matching `tegra\u003Cchip>*` where `\u003Cchip>` is the chip-family numeric\n   prefix (see chip-family map below). Record up to 30 hits; if more,\n   record the count and a \"showing first 30\" note.\n\n#### Chip-family map (used in the \"BSP discovery\" and \"Source tree discovery\" steps)\n\nDerive `\u003Cchip>` from `module.id`:\n\n| `module.id` | Chip family | `\u003Cchip>` prefix |\n|---|---|---|\n| `p3701`, `p3767` | T234 — Orin | `234` |\n| `p3834` | T264 — Thor | `264` |\n\nIf `module.id` is not in this table, record the chip as\n`unknown (module.id=\u003Cvalue>)` and skip the chip-prefixed devicetree\nfilter.\n\n### Documents pass\n\nFor each field in `documents.*` from the loaded profile:\n\n1. Classify the value as **URL** (starts with `http:\u002F\u002F`, `https:\u002F\u002F`,\n   or `ftp:\u002F\u002F`) or **local path** (anything else).\n2. For URLs: record verbatim. **Do not fetch the URL** — KB\n   generation must remain offline. (A future skill can promote to deep\n   indexing.)\n3. For local paths: check `os.path.exists`. Record the path; if\n   missing on disk, append ` (missing)`.\n\nThe one-line description for each field comes from the marker in\n[`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml)\n— strip the `\u003COPTIONAL: …>` wrapper and use the inner text.\n\nIf the profile has no `documents:` block, render the section with a\nsingle line: `_No documents recorded — run `jetson-link-docs`\nor hand-edit the profile to add references._`\n\n### Render and write the KB\n\nRender the markdown using the structure below. Use today's date\n(YYYY-MM-DD) in the header. Always overwrite any existing KB file at\nthe destination — do not prompt before overwriting; re-runs are the\nintended use.\n\nDestination: `target-platform\u002F\u003Cprofile-stem>.md`.\n\n#### Rendered structure\n\n```markdown\n# Target knowledge base — \u003Cprofile-stem>\n\n> Generated \u003CYYYY-MM-DD> from `\u003Cbsp_image.root_path>` (BSP version `\u003Cbsp_image.version>`).\n> Re-run `jetson-generate-kb` after extracting a new BSP, applying\n> patches, or editing profile fields. This file is a regenerated\n> snapshot — do not hand-edit.\n\n## Profile facts\n\n- **Reference devkit:** `\u003Creference_devkit.name>`\n- **Module:** `\u003Cmodule.id>-\u003Cmodule.sku>` (`\u003Cchip family label>`)\n- **Reference carrier:** `\u003Ccarrier.id>-\u003Ccarrier.sku>`\n- **Custom carrier:** `\u003Ccustom_carrier.name>` (`\u003Ccustom_carrier.id>-\u003Ccustom_carrier.sku>`)  _← omit this row if Case 1_\n- **Active flash conf:** `\u003Cflash_config>`\n- **BSP path:** `\u003Cbsp_image.root_path>`\n- **BSP version:** `\u003Cbsp_image.version>`\n- **Source root:** `\u003Csource.root_path>`  _← or \"_not recorded_\" if NA_\n\n## BSP image layout\n\nTop-level directories under `\u003Cbsp_image.root_path>`:\n\n| Directory | Present | Purpose |\n|---|---|---|\n| `rootfs\u002F`     | ✓ \u002F ✗ | userspace rootfs (nvpmodel, nvfan, systemd units, etc.) |\n| `bootloader\u002F` | ✓ \u002F ✗ | firmware blobs, BCT, MB1\u002FMB2 dts |\n| `kernel\u002F`     | ✓ \u002F ✗ | prebuilt kernel + modules |\n| `source\u002F`     | ✓ \u002F ✗ | BSP source tree (kernel, OOT drivers, DT) |\n| `tools\u002F`      | ✓ \u002F ✗ | flashing helpers, jetson-io, kernel_flash |\n| `nv_tegra\u002F`   | ✓ \u002F ✗ | nvidia firmware tarballs, kernel-supplements |\n\nActive flash conf `\u003Cflash_config>`: present at\n`\u003Cbsp_image.root_path>\u002F\u003Cflash_config>` _or_ `(missing — verify before flashing)`.\n\n### nvpmodel files matching the active SKU\n\nFiltered from `rootfs\u002Fetc\u002Fnvpmodel\u002F` by `nvpmodel_\u003Cmodule.id>_\u003Cmodule.sku>*.conf`:\n\n- `\u003Ceach match, one per line>`\n\nThe active variant at boot is selected by `nvpower.sh` from\n`\u002Fproc\u002Fdevice-tree\u002Fcompatible` plus super \u002F safety state — see\n`jetson-customize-nvpmodel` for the resolution rules.\n\n## Source tree layout\n\n(omit this whole section if `source.root_path` is `NA`\u002Fmissing)\n\nTop-level subtrees under `\u003Csource.root_path>`:\n\n| Subtree | Present | Purpose |\n|---|---|---|\n| `kernel-jammy-src\u002F`   | ✓ \u002F ✗ | mainline 5.x kernel sources |\n| `hardware\u002Fnvidia\u002F`    | ✓ \u002F ✗ | NVIDIA platform DTs (per chip family) |\n| `nvidia-oot\u002F`         | ✓ \u002F ✗ | NVIDIA out-of-tree kernel modules |\n| `nvgpu\u002F`              | ✓ \u002F ✗ | GPU driver |\n| `nvethernetrm\u002F`       | ✓ \u002F ✗ | ethernet driver |\n| `nvdisplay\u002F`          | ✓ \u002F ✗ | display driver |\n| `hwpm\u002F`               | ✓ \u002F ✗ | hardware performance monitor |\n| `kernel-devicetree\u002F`  | ✓ \u002F ✗ | devicetree sources |\n\n### Devicetree files for chip family `\u003Cchip>`\n\n(omit if `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F` is absent)\n\nFiles matching `tegra\u003Cchip>*` under `kernel-devicetree\u002Fgeneric-dts\u002Fdts\u002F`:\n\n- `\u003Ceach match, one per line — cap at 30, then a \"first 30 of N\" note>`\n\n## Documents\n\n| Field | Reference |\n|---|---|\n| Documents root folder                    | `\u003Cdoc_root>`                    _or_ _not recorded_ |\n| BSP \u002F Jetson Linux developer guide       | `\u003Cbsp_developer_guide>`         _or_ _not recorded_ |\n| Tegra SoC Technical Reference Manual     | `\u003Csoc_tech_ref_manual>`         _or_ _not recorded_ |\n| Jetson module data sheet                 | `\u003Cmodule_data_sheet>`           _or_ _not recorded_ |\n| Jetson module design guide (PDG)         | `\u003Cmodule_design_guide>`         _or_ _not recorded_ |\n| Jetson module thermal design guide (TDG) | `\u003Cmodule_thermal_design_guide>` _or_ _not recorded_ |\n| Jetson module schematic                  | `\u003Cmodule_schematic>`            _or_ _not recorded_ |\n| Reference carrier board specification    | `\u003Ccarrier_board_spec>`          _or_ _not recorded_ |\n| Reference carrier schematic              | `\u003Ccarrier_schematic>`           _or_ _not recorded_ |\n| Custom carrier schematic                 | `\u003Ccustom_carrier_schematic>`    _or_ _not recorded \u002F N\u002FA (no custom carrier)_ |\n| Reference-devkit pinmux spreadsheet      | `\u003Cref_devkit_pinmux_xls>`       _or_ _not recorded_ |\n| Custom-carrier pinmux spreadsheet        | `\u003Ccustom_carrier_pinmux_xls>`   _or_ _not recorded \u002F N\u002FA (no custom carrier)_ |\n\n(Local paths are tagged ` (missing)` if absent on disk. URLs are\nrecorded verbatim and not fetched. If `doc_root` is set, also tag\n` (missing)` on it if the directory itself is gone — that signals\nauto-mapping in `jetson-link-docs` won't work on a re-run.)\n\n## How to refresh this file\n\nRe-run `jetson-generate-kb` whenever any of the following changes:\n\n- the BSP at `\u003Cbsp_image.root_path>` is re-extracted, patched, or upgraded,\n- the source tree at `\u003Csource.root_path>` changes,\n- the active profile's `bsp_image.*` or `documents.*` fields are edited.\n\nThis file is overwritten on every run. Do not hand-edit it — edit the\nsource data (profile YAML or the BSP tree) and re-run instead.\n```\n\n### Confirm\n\nPrint a short summary:\n\n- Output path: `target-platform\u002F\u003Cprofile-stem>.md`.\n- BSP top-level directory count and which canonical subtrees were\n  present \u002F absent.\n- nvpmodel match count for the active SKU.\n- Source-tree section: rendered or skipped (and why).\n- Documents: count of recorded fields, count of local paths flagged\n  `(missing)`.\n\nIf a downstream skill triggered this run, tell the user to re-issue\ntheir original request.\n\n## Gotchas\n\n- **The KB is a snapshot, not a live view.** The dated header is\n  authoritative — if it doesn't match today, the BSP\u002Fsource\u002Fdocs may\n  have changed underneath. Re-run on demand.\n- **Always overwrites.** No prompt before clobbering the previous KB\n  at `target-platform\u002F\u003Cprofile-stem>.md`. This is intentional —\n  re-runnability is the whole point. Tell the user not to hand-edit\n  the file; edit profile YAML or the BSP and regenerate.\n- **Refuses on `bsp_image.root_path = NA`.** A profile with no BSP path\n  produces a content-free KB. Do not write one — instead, point the\n  user at the profile YAML to fill in.\n- **No URL fetching.** Document URLs are recorded verbatim. Promoting\n  to deep indexing (HTTP HEAD, PDF parsing) is out of scope for v0.1.\n- **No recursive scans.** Discovery is one level deep per directory,\n  with at most one targeted glob (nvpmodel + devicetree). Never walk\n  the entire BSP — it's huge and slow.\n- **Cap devicetree listings at 30 entries** to keep the KB readable.\n  Show \"first 30 of N\" when truncating.\n- **Don't auto-invoke from setup skills.** Setup may suggest running\n  this skill in its summary, but the user opts in. Auto-running hides\n  the I\u002FO step and surprises users whose BSP\u002Fdoc paths are incomplete.\n- **Filename collision risk.** The KB sits at\n  `target-platform\u002F\u003Cstem>.md` next to `\u003Cstem>.yaml`. Don't accidentally\n  read `.md` files in the profile-listing logic of\n  `jetson-set-target` (it already filters to `*.yaml`, but check\n  before adding new file types).\n- **Chip-family map is short.** If a future module SKU is added that\n  isn't in the map, the devicetree filter step is skipped — the KB\n  will note `chip: unknown` rather than fabricate a `\u003Cchip>` prefix.\n  Update this skill's chip-family table when a new chip lands.\n\n## Prerequisites\n\n- Active target profile resolved per\n  `..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`.\n- `bsp_image:` recorded by `\u002Fjetson-init-image`; this is the only\n  required on-disk tree. If `source.root_path` is missing, render the KB\n  without the source-tree section.\n- Optional: `\u002Fjetson-init-source` already resolved `source:` when the\n  user wants source-tree discovery included.\n- Optional but recommended: `\u002Fjetson-link-docs` already wrote the\n  `documents:` block.\n\n## Limitations\n\n- Read-only against the BSP and source trees; never edits the profile\n  YAML or rewrites source files.\n- Devicetree-file enumeration depends on the chip-family table inside\n  this skill; an unknown module SKU lands in the KB as `chip: unknown`\n  rather than a fabricated prefix.\n- Filename layout is fixed at `target-platform\u002F\u003Cstem>.md` to stay next\n  to the profile YAML; renaming the YAML invalidates the link.\n\n## Troubleshooting\n\n- **`bsp_image.root_path` not found** — re-run `\u002Fjetson-init-image` so\n  the BSP is extracted and the path is recorded before regenerating\n  the KB.\n- **Source tree walk picks up wrong subtrees** — `source.root_path`\n  override is stale; rerun `\u002Fjetson-init-source` or correct the\n  profile field.\n- **`documents:` block missing from the KB** — `\u002Fjetson-link-docs` was\n  never run; the KB falls back to \"no documents bound\" rather than\n  guessing paths.\n- **Devicetree section short \u002F empty** — chip-family table doesn't\n  cover the active SoC; update the table and rerun.\n\n## References\n\n- [`..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md`](..\u002F..\u002Fcontext\u002Ftarget-platform-contract.md) — read-order contract this skill follows.\n- [`..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md`](..\u002F..\u002Fcontext\u002Fbsp-customization-workflow.md) — origin of the canonical BSP\u002Fsource subtree list.\n- [`..\u002F..\u002Freferences\u002Fplatform_template.yaml`](..\u002F..\u002Freferences\u002Fplatform_template.yaml) — source of the documents-field one-line descriptions.\n- [`..\u002Fjetson-init-target\u002FSKILL.md`](..\u002Fjetson-init-target\u002FSKILL.md) — sibling skill that authors the active target identity.\n- [`..\u002Fjetson-init-image\u002FSKILL.md`](..\u002Fjetson-init-image\u002FSKILL.md) — sibling skill that authors the BSP image metadata this skill scans.\n- [`..\u002Fjetson-set-target\u002FSKILL.md`](..\u002Fjetson-set-target\u002FSKILL.md) — sibling skill that flips the active pointer this skill resolves.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"0.0.1",{"tags":26,"author":31,"domain":30,"data-classification":32},[27,28,29,30],"target-platform","knowledge-base","documentation","meta","Jetson Team","public","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fnvidia-skills\u002Fjetson-generate-kb",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill jetson-generate-kb",{"tool":47,"command":48},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill jetson-generate-kb",{"tool":50,"command":51},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill jetson-generate-kb","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-generate-kb\u002FSkill.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"metadata.json","REFERENCE","参考文档",421,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fnvidia-skills\u002Fjetson-generate-kb\u002Fmetadata.json",[62,70,75,82,87,94],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":71,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":83,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":95,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]