Jetson Link Docs
NVIDIAOfficialCreated by Jetson TeamDistributed by NVIDIA
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The jetson-link-docs skill manages the documentation references within a Jetson or IGX target-platform profile. It scans a specified directory for reference materials like developer guides, schematics, and pinmux files, then updates the profile YAML with these file paths. This skill acts as a registry tool, ensuring that downstream automation skills can locate necessary documentation by name. It does not download or move files, focusing strictly on mapping existing local assets to the project configuration.
What it does
- Scans a designated root directory for Jetson reference documents using glob patterns.
- Automatically matches files to specific profile slots based on SKU and product tokens.
- Provides an interactive prompt for manual selection when multiple or no files match a slot.
- Updates the active target-platform profile with validated document paths.
- Preserves existing YAML comments and formatting using a round-tripping loader.
- Allows for the registration of URLs alongside local file paths.
When to use it
- After initializing a target profile and staging reference documents on your local disk.
- When downstream skills report missing document references.
- To update or correct document paths in an existing project profile.
- When you need to link custom carrier board schematics or pinmux files to a profile.
Advantages
- Ensures consistent document referencing across different automation tasks.
- Reduces manual configuration effort through intelligent auto-matching.
- Prevents incorrect bindings by requiring user confirmation for ambiguous matches.
- Maintains the integrity of the profile YAML structure and comments.
Usage examples
- “Link my local Jetson documents to the active profile.”
- The agent scans the default documents directory, identifies matching PDFs, and prompts for confirmation to update the profile.
- “I have a custom carrier board; register my schematics.”
- The agent identifies the custom carrier block in the profile, scans for relevant schematic files, and updates the profile with the correct paths.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/jetson-link-docs/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-link-docs.zip -d .agents/skills
Documentation by Jetson Team
jetson-link-docs
Overview
This skill writes the documents: block of the active Jetson /
IGX target-platform profile YAML so downstream skills
(/jetson-generate-kb, /jetson-customize-pinmux, camera / pcie /
uphy, etc.) can resolve doc paths by name. It walks the user through
every document slot in the profile schema, tries to auto-bind each
slot to a file under <documents.root_path>/ via case-insensitive
glob matching, and writes the resulting paths back into the active
profile.
Scope is registering pointers only — this skill does not fetch
or download. The files must already exist on disk under
<documents.root_path>/.
When to invoke
After
/jetson-init-targetfinishes and the user has documents on disk to register.The user wants to add, change, or remove document references on an existing profile.
A downstream skill (e.g.
jetson-generate-kb) reports "no documents recorded" and the user wants to fix that.
Procedure
Resolve the active target
Resolve the active profile + <workspace> per the contract in
../../context/target-platform-contract.md.
Cache the loaded profile in memory — this skill mutates it in
the "Write the documents: block back to the profile" step.
Load the document-slot schema
Load
../../references/platform_template.yaml.
Parse the documents: block. Each per-document field is marked
<OPTIONAL: description>. Use the marker description as prompt text
verbatim. Match markers with the regex
^<(REQUIRED|OPTIONAL|DERIVED):\s*(.*)>$ after YAML parsing strips
surrounding quotes.
Skip custom_carrier_schematic and custom_carrier_pinmux_xls
entirely when the active profile has no custom_carrier: block —
both are meaningless without one. This filter applies through the "Scan and auto-match" and "Manual prompts for unmatched fields" steps.
Resolve documents.root_path
Default: <workspace>/Documents. If the profile already records
documents.root_path, use it. Otherwise, if <workspace>/Documents/
exists, use it (the field is omitted from the written profile —
downstream skills fall back to the workspace default). If neither is
available, prompt the user for an absolute path, or accept Enter /
cancel to skip the auto-scan. A user-provided path that doesn't
exist is treated as skipped (warn, don't refuse — the field is
OPTIONAL); manual prompts in the "Manual prompts for unmatched fields" step still run.
Resolve the product token
Read the Product Token column from
../../references/bsp-platforms-catalogue.md
for the row matching reference_devkit.name. The token is a
case-insensitive glob fragment (e.g. *orin*nano*, *agx*thor*)
consumed by the fallback patterns in the "Scan and auto-match" step.
If reference_devkit.name has no row in the catalogue, log a warning
and proceed without a product-token fallback — the "Scan and auto-match" step still works
with strictly SKU-keyed matching.
For custom carriers, derive <custom-token> from custom_carrier.name
using this recipe: lowercase, replace each space with *, wrap in
* on both ends. E.g. "Acme Vision X1" → *acme*vision*x1*.
Scan and auto-match
Skip this step entirely if documents.root_path did not resolve in
the "Resolve documents.root_path" step (no scan target → no auto-suggest; fall through to manual
prompts in the "Manual prompts for unmatched fields" step).
Scan the directory once (one level deep) and try to auto-match each
remaining <OPTIONAL:…> field using the case-insensitive globs below.
Use the lower-case module.id / carrier.id / custom_carrier.id
strings from the profile in the SKU column.
| Field | SKU glob (primary) | Product-token glob (fallback) |
|---|---|---|
bsp_developer_guide | *developer*guide*.pdf, *BSP*guide*.pdf | (no fallback — pattern is product-agnostic) |
soc_tech_ref_manual | *TRM*.pdf, *tech*ref*manual*.pdf | (no fallback — same) |
module_data_sheet | *<module.id>*data*sheet*.pdf, *<module.id>*datasheet*.pdf | <token>data*sheet*.pdf, <token>datasheet*.pdf |
module_design_guide | *<module.id>*design*guide*.pdf, *<module.id>*PDG*.pdf | <token>design*guide*.pdf, <token>PDG*.pdf |
module_thermal_design_guide | *<module.id>*thermal*.pdf (covers "Thermal Design Guide" / "TDG") | <token>thermal*.pdf |
module_schematic | *<module.id>*schem*.pdf | <token>schem*.pdf |
carrier_board_spec | *<carrier.id>*board*spec*.pdf, *<carrier.id>*spec*.pdf | <token>carrier*spec*.pdf |
carrier_schematic | *<carrier.id>*schem*.pdf | <token>carrier*schem*.pdf |
custom_carrier_schematic | *<custom_carrier.id>*schem*.pdf (only if custom carrier) | <custom-token>schem*.pdf (only if custom carrier) |
ref_devkit_pinmux_xls | *<carrier.id>*pinmux*.xls* (matches .xls, .xlsx, .xlsm) | <token>pinmux*.xls* |
custom_carrier_pinmux_xls | *<custom_carrier.id>*pinmux*.xls* (only if custom carrier) | <custom-token>pinmux*.xls* (only if custom carrier) |
<token> is the catalogue-resolved product token; <custom-token>
is derived from custom_carrier.name per the "Resolve the product token" step. Tokens already
include leading/trailing *, so the table does not repeat them.
Match policy per field
For each field that has auto-match results:
Take the union of hits across the SKU glob and the product- token glob, then deduplicate by absolute path — a file matched by both globs counts once.
Exactly 1 unique hit → show the path and prompt
use this? (yes/no, default yes). Onyes, record it and skip the manual prompt for that field. Onno, fall through to the manual prompt in the "Manual prompts for unmatched fields" step.0 hits → skip auto-suggest entirely for that field; fall through to the "Manual prompts for unmatched fields" step.
2+ unique hits → present them as a numbered list in the "Manual prompts for unmatched fields" step so the user can pick by number rather than typing a path; include a
skip / NAoption. Never silently bind a multi-hit candidate.Never silently bind without user confirmation — wrong-schematic / wrong-pinmux bindings are real and costly.
If documents.root_path is folder-organised one level deeper than
flat (NVIDIA archives often are: Schematics/, Design-Guides/,
Pinmux/, etc.), the file globs may return zero hits even when the
right documents exist. v0.2 only scans one level deep — when 0 hits
is suspicious (documents.root_path exists but no fields auto-bound),
surface the limitation to the user and offer to fall through to
manual prompts.
Manual prompts for unmatched fields
For every field that wasn't auto-bound (and wasn't filtered out in
the "Load the document-slot schema" step), prompt using the marker description from the "Load the document-slot schema" step as prompt
text, in document order. Accept Enter and NA interchangeably as
"skip this field". When the "Match policy per field" step produced 2+ candidate hits for a
field, present them as a numbered list with a skip / NA option
rather than asking for a free-text path.
Validate that user-provided paths exist on disk (warn if not, but do
not refuse — the user may be recording a planned path). URLs (values
starting with http://, https://, or ftp://) are accepted
verbatim and not validated.
Write the documents: block back to the profile
Edit target-platform/<active>.yaml in place. Preserve all other
top-level blocks (reference_devkit:, custom_carrier:,
bsp_image:, source:) and their comments verbatim. Write only the
fields the user provided — omit skipped / NA fields entirely (no
NA placeholders, no empty keys).
Edge behavior: when every field was skipped (including
documents.root_path), drop the documents: block entirely from
the profile — never write documents: {} or a block of NA values.
When only documents.root_path was provided (no per-document
binding), record it alone — the path has value as a hint for future
re-runs. On re-run with an existing documents: block, merge:
existing bindings are preserved unless the user picks a new file or
NA; newly bound fields are added.
Confirm
Print a summary:
Profile path written.
documents.root_path— resolved value (or "default — omitted").Auto-bound fields: count + per-field one-line list.
Manually entered fields: count + list.
Skipped fields: count.
A reminder that
jetson-generate-kbre-readsdocuments.*and should be re-run if a KB exists.
If a downstream skill triggered this run, tell the user to re-issue their original request; do not silently re-trigger it.
Gotchas
Active profile must exist. This skill writes back to whichever profile is active. If no profile is active, refuse and route to
jetson-set-target/jetson-init-target.Product-token globs are intentionally broad. A token like
*orin*nano*matches both Orin-Nano-specific docs and combined Orin-NX/Nano docs (e.g.Jetson-Orin-NX-Nano-Design-Guide_…). That is usually correct for module-side docs (NVIDIA ships combined manuals), but verify on schematic / pinmux / spec fields where wrong-product binding is costly.Update
bsp-platforms-catalogue.mdwhen adding new product rows. The Product Token column is consumed by the "Resolve the product token" step; a missing token degrades the auto-scan to SKU-only matching (the skill warns and continues, but doc-richdocuments.root_pathscans will degrade silently from "5 auto-binds" to "fewer auto- binds").Use a round-tripping YAML loader. the "Write the
documents:block back to the profile" step mutates an existing YAML file. Plainyaml.safe_load+yaml.safe_dumploses comments, block ordering, and quoting style — useruamel.yamlor equivalent so hand-edited fields and comments survive.Re-runnable. Re-running merges new bindings; existing bindings are preserved unless the user explicitly changes them. Safe to invoke as part of a profile refresh.
Prerequisites
Active target profile resolved per
../../context/target-platform-contract.md.Documents available either under the recorded
documents.root_path, under default<workspace>/Documents/, or as user-provided paths / URLs during manual prompts. A missing root only disables auto-scan; it is not a hard prerequisite.ruamel.yamlor another round-tripping YAML writer for the profile edit step.
Limitations
Registers pointers only; never downloads, copies, or renames files.
Per-document field set is fixed to the schema in
../../references/platform_template.yaml— no ad-hoc keys.Glob matching is filename-only; bad filenames in
documents.root_pathwill under-bind and require manual selection.
Troubleshooting
documents.root_pathmissing — auto-scan is skipped. Provide an absolute root path, enter individual document paths / URLs manually, or skip the fields you do not want to bind.Multiple files match a single slot — the skill stops and prompts; pick or rename the file. Example: two
Jetson-Linux-Developer-Guide*.pdffiles → keep the active version, rename the stale one.Profile comments lost after write — a non-round-tripping YAML writer was used; switch to
ruamel.yamland rerun against a fresh pristine copy.Validation fails because a binding points outside
documents.root_path—documents.*are relative paths only; move the file under the root and retry.
References
../../context/target-platform-contract.md— target-platform contract; this skill consumes and mutates the active profile.../../references/bsp-platforms-catalogue.md— source of the Product Token column for the "Resolve the product token" step.../../references/platform_template.yaml— schema for thedocuments:block (source of truth for prompts and field list).../jetson-init-target/SKILL.md— sibling skill that authors target identity (reference_devkit:, optionalcustom_carrier:).../jetson-init-image/SKILL.md— sibling skill that authorsbsp_image:.../jetson-init-source/SKILL.md— sibling skill: clones shared repos and handlessource.root_pathoverrides.../jetson-generate-kb/SKILL.md— sibling skill: consumes thedocuments:block this skill writes.
Files
- ATTRIBUTION.mdAdded by AutoGineer911 B
- BENCHMARK.md3.7 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md13.1 KiB
- evals/evals.json4.5 KiB
- skill-card.md3.8 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-link-docs · 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-link-docs.zip