Official agent skill

Jetson Print Bsp Info

A skill your agent uses when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a LinuxforTegra root on the host PC.

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Jetson Print Bsp Info

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/jetson-print-bsp-info .claude/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .claude/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/jetson-print-bsp-info .agents/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .agents/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/jetson-print-bsp-info .cursor/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .cursor/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NVIDIA/skills.git --path skills/jetson-print-bsp-info

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/jetson-print-bsp-info .gemini/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .gemini/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/jetson-print-bsp-info .github/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .github/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-bsp-info --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVIDIA/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/jetson-print-bsp-info .opencode/skills/jetson-print-bsp-info && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "jetson-print-bsp-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-bsp-info into .opencode/skills/jetson-print-bsp-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-bsp-info", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: jetson-print-bsp-info
GitHub stars: 3.6k
Token cost: ~1.3k tokens
SKILL.md length: 508 words
Files: 5
Skills in repo: 390
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a LinuxforTegra root on the host PC.

Works in 4 steps: Resolve L4T_ROOT and validate the… → Extract the L4T release header line. The… → List supported board config files and… → …
You need to print Jetson BSP info (L4T version
SKILL.md covers Purpose, When to use, Prerequisites and Inputs, plus 7 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Jetson Print Bsp Info is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a LinuxforTegra root on the host PC. This is an example skill.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `BENCHMARK.md`, `evals/evals.json` and `skill-card.md`).

It sits in AI & LLM Engineering, covering GPU and accelerator computing. It works with NVIDIA AI Platform and Linux. The repository describes itself as: Agent Skills for NVIDIA products — install into Claude Code, Codex, and other coding agents to run Physical AI, robotics, simulation, CUDA, and RAG workflows end to end. The licence is Apache-2.0.

When your agent uses it

You need to print Jetson BSP info (L4T version
Rootfs state) from a LinuxforTegra root on the host PC

Example prompts

“/jetson-print-bsp-info”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Resolve L4T_ROOT and validate the directory is a Linux_for_Tegra root — exit early otherwise. flash.sh and nv_tegra/ are the two anchor…
Extract the L4T release header line. The canonical host-side location is nv_tegra/nv_tegra_release; the same file is copied into the…
List supported board config files and join them onto one comma-separated line
Check whether the rootfs has been populated. An empty rootfs/ means apply_binaries.sh has not been run yet

What it can do on your machine

Read from SKILL.md and the folder at commit 14a98ae. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jetson Print Bsp Info loads about 1.3k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~44
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVIDIA/skills at commit 14a98ae, republished under its Apache-2.0 licence (© NVIDIA). 508 words, ~1,274 tokens.

Download SKILL.mdSave it as .claude/skills/jetson-print-bsp-info/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: jetson-print-bsp-info
description: Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a Linux_for_Tegra root on the host PC. This is an example skill.
version: 0.0.1
license: Apache-2.0
metadata.author: Jetson Team
metadata.tags: jetson, bsp, info
metadata.languages: bash
metadata.data-classification: public

jetson-print-bsp-info

Prints a concise summary of a Jetson Linux_for_Tegra (BSP) tree on the host PC.

This skill is intended as a reference example for the jetson-bsp-skills repo and the NVIDIA-wide skills CI. It performs read-only inspection — no flashing, no rootfs changes.

Purpose

Capture a baseline snapshot of a Linux_for_Tegra BSP tree (release, board configs, rootfs state) before flashing, so issues like "wrong L4T version" or "rootfs never populated" are caught early.

When to use

A user has unpacked a Jetson BSP tarball and wants to confirm the L4T version, supported boards, and rootfs state before flashing.
You need a quick sanity check that a Linux_for_Tegra/ directory looks valid (expected scripts and config files present).

Prerequisites

Running on the host PC (Linux), not on the Jetson target.
A Linux_for_Tegra/ directory extracted from a Jetson BSP tarball.
Standard CLIs available: ls, head, cat, paste, sed.

Inputs

L4T_ROOT (optional): absolute path to the Linux_for_Tegra/ directory. If unset, use the current working directory.

Instructions

Run each step in order and print the captured values into the report shown under Output format.

Resolve L4T_ROOT and validate the directory is a Linux_for_Tegra root — exit early otherwise. flash.sh and nv_tegra/ are the two anchor artifacts that every BSP ships:

bash

L4T_ROOT="${L4T_ROOT:-$PWD}"
if [ ! -f "$L4T_ROOT/flash.sh" ] || [ ! -d "$L4T_ROOT/nv_tegra" ]; then
  echo "Not a Linux_for_Tegra root: '$L4T_ROOT' (missing flash.sh or nv_tegra/)"
  exit 1
fi
echo "$L4T_ROOT"

Extract the L4T release header line. The canonical host-side location is nv_tegra/nv_tegra_release; the same file is copied into the rootfs by apply_binaries.sh. Only the first line is useful — the rest is a long list of library SHAs:
bash
```
head -1 "$L4T_ROOT/nv_tegra/nv_tegra_release" 2>/dev/null \
  || head -1 "$L4T_ROOT/rootfs/etc/nv_tegra_release" 2>/dev/null \
  || echo "L4T release info not found"
```
List supported board config files and join them onto one comma-separated line:
bash
```
(cd "$L4T_ROOT" && ls *.conf 2>/dev/null) | paste -sd, -
```
Check whether the rootfs has been populated. An empty rootfs/ means apply_binaries.sh has not been run yet:
bash
```
if [ -f "$L4T_ROOT/rootfs/etc/passwd" ]; then
  echo "populated"
else
  echo "empty"
fi
```

Output format

Print a short report with these sections, one line each where possible:

text

L4T root:        <path>
L4T release:     <release header line>
Board configs:   <comma-separated list>
Rootfs:          populated | empty

Show full SKILL.md (222 more words)Show less

Examples

Example output on an Orin AGX BSP (L4T R36):

text

L4T root:        $HOME/Linux_for_Tegra
L4T release:     # R36 (release), REVISION: 3.0
Board configs:   jetson-agx-orin-devkit.conf,jetson-orin-nano-devkit.conf
Rootfs:          populated

Example output on a freshly untarred BSP where apply_binaries.sh has not been run yet:

text

L4T root:        /tmp/Linux_for_Tegra
L4T release:     # R39 (release), REVISION: 0.0
Board configs:   jetson-agx-thor-devkit.conf
Rootfs:          empty

Error handling

Each command falls back to a clearly labeled "... not found" string if the underlying file is missing — the skill never errors out mid-report. If L4T_ROOT does not contain flash.sh and nv_tegra/, exit early with a clear "not a Linux_for_Tegra root" message rather than printing misleading info.

Limitations

Read-only inspection only — does not validate signatures, kernel images, or device-tree overlays.
Only checks the presence of rootfs/etc/passwd as a populated-rootfs proxy; will not detect a half-populated rootfs.
Lists all *.conf board configs in L4T_ROOT/; does not try to infer which one the user intends to flash.

Troubleshooting

Error: Not a Linux_for_Tegra root: '...' (missing flash.sh or nv_tegra/) Cause: L4T_ROOT points at a parent directory, an extracted rootfs, or an unrelated path. Solution: Point L4T_ROOT at the directory that contains flash.sh (typically Linux_for_Tegra/).
Error: L4T release info not found Cause: Neither nv_tegra/nv_tegra_release nor rootfs/etc/nv_tegra_release exists — the BSP tarball may be incomplete or apply_binaries.sh was never run. Solution: Re-extract the BSP tarball or run apply_binaries.sh to populate the rootfs.

Notes

Do not modify any files. This skill is read-only.
If multiple board config files exist, list all of them — do not try to guess which one the user intends to flash.

Files

SKILL.md and 4 other files in skills/jetson-print-bsp-info of NVIDIA/skills.

SKILL.md
BENCHMARK.md
evals/evals.json
skill-card.md
skill.oms.sig

Open the folder on GitHubat commit 14a98ae

Compare with similar skills

Jetson Print Bsp Info next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jetson Print Bsp Info compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jetson Print Bsp Info this skillNVIDIA/skills	3.6k	—	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
Graphsignalgraphsignal/graphsignal	257	—	~6.3k	Automated safety check: Pass	Apache-2.0	yesterday
LLM Torch Profiler Trace AnalysisBBuf/AI-Infra-Auto-Driven-SKILLS	938	—	~2.8k	Automated safety check: Pass	None	5 days ago
Cv DeployLMIXR/CV_Deployment_skill	188	—	~547	Automated safety check: Pass	None	11 days ago
TensorRT-LLM InferenceOrchestra-Research/AI-Research-SKILLs	13k	4 repos	~1.3k	Automated safety check: Pass	MIT	3 mo ago
Triton SkillslowlyC/agent-gpu-skills	169	—	~1.3k	Automated safety check: Pass	MIT	2 mo ago

Similar skills

Graphsignal
graphsignal/graphsignal
Profile AI inference workloads (vLLM, SGLang, TensorRT-LLM, PyTorch, any GPU application) with the Graphsignal profiler and read the results from its local /signals JSON endpoint.
257 GitHub stars~6.3k tokensUpdated yesterday
AI & LLM EngineeringAuto-check passed
LLM Torch Profiler Trace Analysis
BBuf/AI-Infra-Auto-Driven-SKILLS
Analyzes Torch Profiler traces from SGLang, vLLM and TensorRT-LLM servers into kernel attribution, overlap and fusion tables.
938 GitHub stars~2.8k tokensUpdated 5 days ago
AI & LLM EngineeringAuto-check passed
Cv Deploy
LMIXR/CV_Deployment_skill
基于 helpfile 工程经验，协助 agent 配置 CV 主机和边缘设备环境、编译视觉与推理依赖、接入摄像头视频并打包部署服务。适用于 Ubuntu、CentOS、Windows、macOS、Jetson、树莓派和 RK3399 的 CV 工程实施与故障排查，以及相关移动端配套工具；模型训练和纯算法设计不属于本技能主线。
188 GitHub stars~547 tokensUpdated 11 days ago
AI & LLM EngineeringAuto-check passed
TensorRT-LLM Inference
Orchestra-Research/AI-Research-SKILLs
Optimizes and serves LLMs on NVIDIA GPUs with TensorRT-LLM, covering quantization, in-flight batching, multi-GPU parallelism and the trtllm-serve command.
13k GitHub starsUsed in 4 repos~1.3k tokens
AI & LLM EngineeringAuto-check passed
Triton Skill
slowlyC/agent-gpu-skills
Write, debug, and optimize Triton and Gluon GPU kernels from local upstream tutorials, production kernels, language definitions, and compiler source.
169 GitHub stars~1.3k tokensUpdated 2 mo ago
AI & LLM EngineeringAuto-check passed
Megatron-Core LLM Training
Orchestra-Research/AI-Research-SKILLs
Sets up large-scale LLM training with NVIDIA Megatron-Core, choosing tensor, pipeline, data, context and expert parallelism for a given model size and GPU count.
13k GitHub starsUsed in 2 repos~2.4k tokens
AI & LLM EngineeringAuto-check passed

More from NVIDIA/skills

All 390 skills in this repo

Vss Deploy Detection Tracking 2D
NVIDIA/skills
Official
A skill your agent uses when the user wants to deploy, run, debug, tear down, or call the REST API of the RTVI-CV 2D detection / tracking microservice.
3.6k GitHub starsUsed in 1 repo~4.5k tokens
Auto-check passed
HSB IP Def File Tool
NVIDIA/skills
Official
Generates, validates, compares and explains HOLOLINK_def.svh macro files for the HSB IP, using bundled Python scripts and asking before it writes anything.
3.6k GitHub stars~2.9k tokensUpdated yesterday
Auto-check passed
Isaac Sim Mission Control Showcase
NVIDIA/skills
Official
Runs and validates an end-to-end Mission Control demo in a locally installed Isaac Sim, with a Nova Carter robot driven through a Python server.
3.6k GitHub stars~4.8k tokensUpdated yesterday
Auto-check passed
Defect Image Generation with Cosmos AnomalyGen
NVIDIA/skills
Official
Orchestrates defect image generation for PCBA, metal surface and glass inspection with NVIDIA Cosmos AnomalyGen on OSMO, from cold-start Day 0 to real-photo Day 1 labeling.
3.6k GitHub stars~5k tokensUpdated yesterday
Auto-check: notes
Physical AI Video Augmentation on OSMO
NVIDIA/skills
Official
Orchestrates video data augmentation and auto-labeling workflows on OSMO, from flow selection and preflight checks to submission, monitoring and output download.
3.6k GitHub stars~4.7k tokensUpdated yesterday
Auto-check: notes
TAO Detection KPI Analysis
NVIDIA/skills
Official
Runs NVIDIA TAO Data Services KPI analysis on object detection results, comparing predictions to ground truth and writing per-class precision, recall and AP to a CSV.
3.6k GitHub stars~2.7k tokensUpdated yesterday
Auto-check: notes

Works with

Questions about Jetson Print Bsp Info

What does Jetson Print Bsp Info do?

A skill your agent uses when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a LinuxforTegra root on the host PC. Jetson Print Bsp Info is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use when you need to print Jetson BSP info (L4T version, board configs, rootfs state) from a LinuxforTegra root on the host PC.

When should I use Jetson Print Bsp Info?

Jetson Print Bsp Info fits situations like: you need to print Jetson BSP info (L4T version; rootfs state) from a LinuxforTegra root on the host PC.

How do I install Jetson Print Bsp Info in Claude Code?

Run `npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a claude-code`. Or copy the skill folder (skills/jetson-print-bsp-info in NVIDIA/skills) into .claude/skills/jetson-print-bsp-info in your project. Claude Code loads it when a task matches its description.

How do I install Jetson Print Bsp Info in Codex?

Run `npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a codex`. Or copy the skill folder (skills/jetson-print-bsp-info in NVIDIA/skills) into .agents/skills/jetson-print-bsp-info in your project. Codex loads it when a task matches its description.

Can I use Jetson Print Bsp Info in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVIDIA/skills --skill jetson-print-bsp-info -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jetson-print-bsp-info, .gemini/skills/jetson-print-bsp-info, .github/skills/jetson-print-bsp-info and .opencode/skills/jetson-print-bsp-info in your project.

What does Jetson Print Bsp Info need to run?

SKILL.md names no scripts, command-line tools or credentials: Jetson Print Bsp Info is instructions for the agent only.

Does Jetson Print Bsp Info access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Jetson Print Bsp Info safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jetson Print Bsp Info use?

Jetson Print Bsp Info is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jetson Print Bsp Info use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jetson Print Bsp Info?

Skills that share tags, products or a category with Jetson Print Bsp Info: Graphsignal (graphsignal/graphsignal, 257 stars), LLM Torch Profiler Trace Analysis (BBuf/AI-Infra-Auto-Driven-SKILLS, 938 stars), Cv Deploy (LMIXR/CV_Deployment_skill, 188 stars) and TensorRT-LLM Inference (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jetson Print Bsp Info?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,555 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 9, 2026.

Source: NVIDIA/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Jetson Print Bsp Info

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

jetson-print-bsp-info

Purpose

When to use

Prerequisites

Inputs

Instructions

Output format

Examples

Error handling

Limitations

Troubleshooting

Notes

Files

Compare with similar skills

Similar skills

More from NVIDIA/skills

Related

Questions about Jetson Print Bsp Info