Jetson Generate Kb
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Content generator
- Documents and content
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill creates a static markdown reference file that summarizes the current state of a Jetson target platform. By scanning the BSP root and source tree, it captures the directory layout, identifies relevant configuration files, and lists documented references. The resulting knowledge base serves as a quick-reference snapshot, allowing users and AI agents to understand the target configuration without needing to re-traverse the filesystem. It is designed to be re-runnable, overwriting previous versions whenever the underlying BSP, source tree, or profile metadata changes.
What it does
- Produces a markdown file summarizing the BSP image and source tree layout.
- Verifies the presence of canonical subtrees like rootfs, bootloader, and kernel.
- Detects and lists specific nvpmodel configuration files based on the active module SKU.
- Enumerates relevant devicetree files for the identified chip family.
- Validates the existence of local document paths referenced in the profile.
- Provides a dated snapshot of the target configuration for consistent reference.
When to use it
- After initializing a new BSP image or source tree.
- Following any patches or updates to the BSP or source directories.
- After modifying profile fields related to BSP paths or documentation.
- When you need a quick, offline summary of the current target platform structure.
Advantages
- Provides a centralized, human-readable view of the target configuration.
- Reduces filesystem overhead by providing a snapshot instead of live scanning.
- Ensures documentation and configuration references are validated against the disk.
- Facilitates easier context sharing for downstream AI agent tasks.
Usage examples
- “Generate the knowledge base for my current Jetson target.”
- The agent scans the BSP and source directories, then creates a markdown file at target-platform/my-profile.md containing the layout and document status.
- “Update the target knowledge base after patching the kernel.”
- The agent re-runs the discovery process and overwrites the existing knowledge base file with the updated BSP and source tree information.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/jetson-generate-kb/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-generate-kb.zip -d .agents/skills
Documentation by Jetson Team
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:
BSP image layout — top-level directories under
bsp_image.root_path, presence of canonical subtrees (rootfs/,bootloader/,source/, …), and the nvpmodel variants matching the active module SKU.Source tree layout — top-level subtrees under
source.root_path(kernel-jammy-src/,hardware/nvidia/,nvidia-oot/, etc.) and devicetree files matching the chip family.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-imageprepares the BSP for a freshly authored profile.After re-extracting a BSP archive or applying patches under
bsp_image.root_path.After updating the source tree at
source.root_path.After editing
bsp_image.*ordocuments.*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 |
|---|---|---|
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. |
source.root_path | no | Skip the source-tree section; note "source_root not recorded" in the KB. |
documents.* | no | Render an empty Documents table with a "no documents recorded" note. |
If bsp_image.root_path is set but the directory does not exist on disk,
refuse with a clear message — do not fabricate a layout for a path
that isn't there.
BSP discovery (under bsp_image.root_path)
Run only the following cheap operations — no recursive scans, no file content reads beyond directory listings:
ls -1ofbsp_image.root_path(one level deep). Record which directories are present.For each canonical subtree below, mark present/absent:
rootfs/,bootloader/,kernel/,source/,tools/,nv_tegra/.Verify the active
flash_configfile exists at<bsp_image.root_path>/<flash_config>. Record its path or(missing).List
rootfs/etc/nvpmodel/and filter to filenames matchingnvpmodel_<module.id>_<module.sku>*.conf. Record each match. Use the lower-case module id (e.g.p3767) and the YAML-quoted sku string (e.g.0001).
Source tree discovery (under source.root_path)
Skip this step entirely if source.root_path is NA or missing.
Otherwise, run only:
ls -1ofsource.root_path(one level deep).For each canonical subtree below, mark present/absent:
kernel-jammy-src/,hardware/nvidia/,nvidia-oot/,nvgpu/,nvethernetrm/,nvdisplay/,hwpm/,kernel-devicetree/.If
kernel-devicetree/generic-dts/dts/exists, list filenames matchingtegra<chip>*where<chip>is the chip-family numeric prefix (see chip-family map below). Record up to 30 hits; if more, record the count and a "showing first 30" note.
Chip-family map (used in the "BSP discovery" and "Source tree discovery" steps)
Derive <chip> from module.id:
module.id | Chip family | <chip> prefix |
|---|---|---|
p3701, p3767 | T234 — Orin | 234 |
p3834 | T264 — Thor | 264 |
If module.id is not in this table, record the chip as
unknown (module.id=<value>) and skip the chip-prefixed devicetree
filter.
Documents pass
For each field in documents.* from the loaded profile:
Classify the value as URL (starts with
http://,https://, orftp://) or local path (anything else).For URLs: record verbatim. Do not fetch the URL — KB generation must remain offline. (A future skill can promote to deep indexing.)
For local paths: check
os.path.exists. Record the path; if missing on disk, append(missing).
The one-line description for each field comes from the marker in
../../references/platform_template.yaml
— strip the <OPTIONAL: …> wrapper and use the inner text.
If the profile has no documents: block, render the section with a
single line: _No documents recorded — run jetson-link-docs or hand-edit the profile to add references._
Render and write the KB
Render the markdown using the structure below. Use today's date (YYYY-MM-DD) in the header. Always overwrite any existing KB file at the destination — do not prompt before overwriting; re-runs are the intended use.
Destination: target-platform/<profile-stem>.md.
Rendered structure
# Target knowledge base — <profile-stem>
> Generated <YYYY-MM-DD> from `<bsp_image.root_path>` (BSP version `<bsp_image.version>`).
> Re-run `jetson-generate-kb` after extracting a new BSP, applying
> patches, or editing profile fields. This file is a regenerated
> snapshot — do not hand-edit.
## Profile facts
- **Reference devkit:** `<reference_devkit.name>`
- **Module:** `<module.id>-<module.sku>` (`<chip family label>`)
- **Reference carrier:** `<carrier.id>-<carrier.sku>`
- **Custom carrier:** `<custom_carrier.name>` (`<custom_carrier.id>-<custom_carrier.sku>`) _← omit this row if Case 1_
- **Active flash conf:** `<flash_config>`
- **BSP path:** `<bsp_image.root_path>`
- **BSP version:** `<bsp_image.version>`
- **Source root:** `<source.root_path>` _← or "_not recorded_" if NA_
## BSP image layout
Top-level directories under `<bsp_image.root_path>`:
| Directory | Present | Purpose |
|---|---|---|
| `rootfs/` | ✓ / ✗ | userspace rootfs (nvpmodel, nvfan, systemd units, etc.) |
| `bootloader/` | ✓ / ✗ | firmware blobs, BCT, MB1/MB2 dts |
| `kernel/` | ✓ / ✗ | prebuilt kernel + modules |
| `source/` | ✓ / ✗ | BSP source tree (kernel, OOT drivers, DT) |
| `tools/` | ✓ / ✗ | flashing helpers, jetson-io, kernel_flash |
| `nv_tegra/` | ✓ / ✗ | nvidia firmware tarballs, kernel-supplements |
Active flash conf `<flash_config>`: present at
`<bsp_image.root_path>/<flash_config>` _or_ `(missing — verify before flashing)`.
### nvpmodel files matching the active SKU
Filtered from `rootfs/etc/nvpmodel/` by `nvpmodel_<module.id>_<module.sku>*.conf`:
- `<each match, one per line>`
The active variant at boot is selected by `nvpower.sh` from
`/proc/device-tree/compatible` plus super / safety state — see
`jetson-customize-nvpmodel` for the resolution rules.
## Source tree layout
(omit this whole section if `source.root_path` is `NA`/missing)
Top-level subtrees under `<source.root_path>`:
| Subtree | Present | Purpose |
|---|---|---|
| `kernel-jammy-src/` | ✓ / ✗ | mainline 5.x kernel sources |
| `hardware/nvidia/` | ✓ / ✗ | NVIDIA platform DTs (per chip family) |
| `nvidia-oot/` | ✓ / ✗ | NVIDIA out-of-tree kernel modules |
| `nvgpu/` | ✓ / ✗ | GPU driver |
| `nvethernetrm/` | ✓ / ✗ | ethernet driver |
| `nvdisplay/` | ✓ / ✗ | display driver |
| `hwpm/` | ✓ / ✗ | hardware performance monitor |
| `kernel-devicetree/` | ✓ / ✗ | devicetree sources |
### Devicetree files for chip family `<chip>`
(omit if `kernel-devicetree/generic-dts/dts/` is absent)
Files matching `tegra<chip>*` under `kernel-devicetree/generic-dts/dts/`:
- `<each match, one per line — cap at 30, then a "first 30 of N" note>`
## Documents
| Field | Reference |
|---|---|
| Documents root folder | `<doc_root>` _or_ _not recorded_ |
| BSP / Jetson Linux developer guide | `<bsp_developer_guide>` _or_ _not recorded_ |
| Tegra SoC Technical Reference Manual | `<soc_tech_ref_manual>` _or_ _not recorded_ |
| Jetson module data sheet | `<module_data_sheet>` _or_ _not recorded_ |
| Jetson module design guide (PDG) | `<module_design_guide>` _or_ _not recorded_ |
| Jetson module thermal design guide (TDG) | `<module_thermal_design_guide>` _or_ _not recorded_ |
| Jetson module schematic | `<module_schematic>` _or_ _not recorded_ |
| Reference carrier board specification | `<carrier_board_spec>` _or_ _not recorded_ |
| Reference carrier schematic | `<carrier_schematic>` _or_ _not recorded_ |
| Custom carrier schematic | `<custom_carrier_schematic>` _or_ _not recorded / N/A (no custom carrier)_ |
| Reference-devkit pinmux spreadsheet | `<ref_devkit_pinmux_xls>` _or_ _not recorded_ |
| Custom-carrier pinmux spreadsheet | `<custom_carrier_pinmux_xls>` _or_ _not recorded / N/A (no custom carrier)_ |
(Local paths are tagged ` (missing)` if absent on disk. URLs are
recorded verbatim and not fetched. If `doc_root` is set, also tag
` (missing)` on it if the directory itself is gone — that signals
auto-mapping in `jetson-link-docs` won't work on a re-run.)
## How to refresh this file
Re-run `jetson-generate-kb` whenever any of the following changes:
- the BSP at `<bsp_image.root_path>` is re-extracted, patched, or upgraded,
- the source tree at `<source.root_path>` changes,
- the active profile's `bsp_image.*` or `documents.*` fields are edited.
This file is overwritten on every run. Do not hand-edit it — edit the
source data (profile YAML or the BSP tree) and re-run instead.Confirm
Print a short summary:
Output path:
target-platform/<profile-stem>.md.BSP top-level directory count and which canonical subtrees were present / absent.
nvpmodel match count for the active SKU.
Source-tree section: rendered or skipped (and why).
Documents: count of recorded fields, count of local paths flagged
(missing).
If a downstream skill triggered this run, tell the user to re-issue their original request.
Gotchas
The KB is a snapshot, not a live view. The dated header is authoritative — if it doesn't match today, the BSP/source/docs may have changed underneath. Re-run on demand.
Always overwrites. No prompt before clobbering the previous KB at
target-platform/<profile-stem>.md. This is intentional — re-runnability is the whole point. Tell the user not to hand-edit the file; edit profile YAML or the BSP and regenerate.Refuses on
bsp_image.root_path = NA. A profile with no BSP path produces a content-free KB. Do not write one — instead, point the user at the profile YAML to fill in.No URL fetching. Document URLs are recorded verbatim. Promoting to deep indexing (HTTP HEAD, PDF parsing) is out of scope for v0.1.
No recursive scans. Discovery is one level deep per directory, with at most one targeted glob (nvpmodel + devicetree). Never walk the entire BSP — it's huge and slow.
Cap devicetree listings at 30 entries to keep the KB readable. Show "first 30 of N" when truncating.
Don't auto-invoke from setup skills. Setup may suggest running this skill in its summary, but the user opts in. Auto-running hides the I/O step and surprises users whose BSP/doc paths are incomplete.
Filename collision risk. The KB sits at
target-platform/<stem>.mdnext to<stem>.yaml. Don't accidentally read.mdfiles in the profile-listing logic ofjetson-set-target(it already filters to*.yaml, but check before adding new file types).Chip-family map is short. If a future module SKU is added that isn't in the map, the devicetree filter step is skipped — the KB will note
chip: unknownrather than fabricate a<chip>prefix. Update this skill's chip-family table when a new chip lands.
Prerequisites
Active target profile resolved per
../../context/target-platform-contract.md.bsp_image:recorded by/jetson-init-image; this is the only required on-disk tree. Ifsource.root_pathis missing, render the KB without the source-tree section.Optional:
/jetson-init-sourcealready resolvedsource:when the user wants source-tree discovery included.Optional but recommended:
/jetson-link-docsalready wrote thedocuments:block.
Limitations
Read-only against the BSP and source trees; never edits the profile YAML or rewrites source files.
Devicetree-file enumeration depends on the chip-family table inside this skill; an unknown module SKU lands in the KB as
chip: unknownrather than a fabricated prefix.Filename layout is fixed at
target-platform/<stem>.mdto stay next to the profile YAML; renaming the YAML invalidates the link.
Troubleshooting
bsp_image.root_pathnot found — re-run/jetson-init-imageso the BSP is extracted and the path is recorded before regenerating the KB.Source tree walk picks up wrong subtrees —
source.root_pathoverride is stale; rerun/jetson-init-sourceor correct the profile field.documents:block missing from the KB —/jetson-link-docswas never run; the KB falls back to "no documents bound" rather than guessing paths.Devicetree section short / empty — chip-family table doesn't cover the active SoC; update the table and rerun.
References
../../context/target-platform-contract.md— read-order contract this skill follows.../../context/bsp-customization-workflow.md— origin of the canonical BSP/source subtree list.../../references/platform_template.yaml— source of the documents-field one-line descriptions.../jetson-init-target/SKILL.md— sibling skill that authors the active target identity.../jetson-init-image/SKILL.md— sibling skill that authors the BSP image metadata this skill scans.../jetson-set-target/SKILL.md— sibling skill that flips the active pointer this skill resolves.
Files
- ATTRIBUTION.mdAdded by AutoGineer917 B
- BENCHMARK.md3.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md14.9 KiB
- evals/evals.json3.6 KiB
- skill-card.md3.6 KiB
- skill.oms.sig4.5 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Jetson Team
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/jetson-generate-kb · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Jetson Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-generate-kb.zip