jetson-link-docs

Bind pre-staged Jetson reference document paths to target-platform profile schemas.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-link-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jetson-link-docs
Source: https://github.com/JORDAN0615/bsp_factory/tree/main/skills/jetson-link-docs
Command: npx skills add https://github.com/JORDAN0615/bsp_factory --skill jetson-link-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually editing target-platform profile YAML to register pre-downloaded Jetson reference documentation is error-prone and time-consuming, and unregistered docs break downstream BSP customization workflows that rely on named document paths.

Core Features & Use Cases

  • Automated Document Matching: Scans a local documents folder to auto-match Jetson reference docs (developer guides, schematics, pinmux files, etc.) to profile slots using case-insensitive glob patterns tailored to SKU and product type.
  • Flexible Manual Entry: Supports manual path entry for unmatched documents, including remote URLs, and handles edge cases like custom carriers, folder-organized document archives, and missing product catalogue entries.
  • Use Case: After staging downloaded Jetson Orin Nano developer guides, module schematics, and carrier board specs in your workspace Documents folder, run this skill to automatically register all matching files in your active target profile so downstream skills like jetson-generate-kb can access the correct references without manual configuration.

Quick Start

Use the jetson-link-docs skill to register your pre-staged Jetson reference documents into the active target-platform profile.

Frequently Asked Questions about jetson-link-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register Jetson reference documentation into my BSP profile?

Registering Jetson reference documentation involves binding pre-staged local file paths to the active target-platform profile schema. This unblocks downstream BSP customization workflows that depend on registered document references using SKU-based glob matching.

How do I automatically match Jetson schematics and pinmux files to my target profile?

Automatically matching Jetson schematics and pinmux files is done by scanning a local documents folder and auto-matching files to profile slots using case-insensitive glob patterns tailored to your specific SKU and product type.

Can I manually enter remote URLs for unmatched Jetson developer guides in my profile?

Yes, you can manually enter remote URLs for unmatched Jetson developer guides. The system supports manual path entry for unmatched documents to handle edge cases like custom carriers, folder-organized archives, and missing product catalogue entries.

Why do unregistered Jetson reference docs break my downstream BSP customization?

Unregistered Jetson reference docs break downstream BSP customization because downstream skills require named document paths to access the correct references. Manually editing target-platform profile YAML to register these docs is error-prone and breaks the workflow.

Does jetson-link-docs support custom carrier board specifications and missing catalogue entries?

Yes, jetson-link-docs supports custom carrier board specifications and missing product catalogue entries through flexible manual entry. It handles edge cases like custom carriers and folder-organized document archives by allowing manual path and URL references for unmatched slots.