Agent skill · software engineering · nvidia
jetson-generate-kb
Build a per-target knowledge-base markdown next to the active profile by walking the BSP root and source tree. Use after init-image / init-source; not for editing profile fields.
Why this skill is useful
Adds a script that generates a detailed markdown knowledge base for target platforms, which includes specific directory structures and document references not commonly found in public documentation.
What it needs
Requires jetson installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 2,816 stars on the source repository.
What this skill does
Generate Target Knowledge Base Overview This skill produces a per-profile markdown reference at target-platform/<profile-stem>.md (sibling to the profile YAML). It bundles three things into one file so a future Claude session — or the user — can see the shape of the active target without re-walking the filesystem: 1. BSP image layout — top-level directories under bspimage.rootpath, presence of canonical subtrees (rootfs/, bootloader/, source/, …), and the nvpmodel variants matching the active module SKU. 2. Source tree layout — top-level subtrees under source.rootpath (kernel-jammy-src/, hardware/nvidia/, nvidia-oot/, etc.) and devicetree files matching the chip family. 3. Documents — the documents. references recorded in the profile, with local-path existence checks and one-line descriptions. The KB is a snapshot, dated in its header. Re-run this skill whenever the underlying data changes — it is intentionally re-runnable and overwrites the previous KB on each run. When to invoke After jetson-init-image prepares the BSP for a freshly authored profile. After re-extracting a BSP archive or applying patches under bspimage.rootpath. After updating the source tree at source.rootpath. After editing bspimage. or documents. in the profile YAML. When a downstream skill asks "where is X in this BSP?" and you'd rather check the KB than re-walk the tree. Procedure Resolve the active target Resolve the active profile per the contract in ../../context/target-platform-contract.md; cache it in memory — the rest of the skill consumes only this profile. Record <profile-stem> (the bare filename minus .yaml) as the KB output filename stem. Validate inputs Field Required for KB? If missing --- --- --- bspimage.rootpath 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. source.rootpath no Skip the source-tree section; note "sourceroot not recorded" in the KB. documents. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/jetson-generate-kb