Official agent skill

Jetson Print Device Info

A skill your agent uses when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target.

OfficialApache-2.0Auto-check passedAI & LLM Engineering

Install Jetson Print Device Info

skills CLI

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

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

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-device-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-device-info .claude/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .claude/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-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-device-info -a codex

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

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-device-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-device-info .agents/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .agents/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-info -a cursor

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

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-device-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-device-info .cursor/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .cursor/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-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-device-info -a gemini-cli

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

GitHub CLI

$ gh skill install NVIDIA/skills jetson-print-device-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-device-info .gemini/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .gemini/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-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-device-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-device-info .github/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .github/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-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-device-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-device-info .opencode/skills/jetson-print-device-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-device-info" agent skill from https://github.com/NVIDIA/skills/tree/main/skills/jetson-print-device-info into .opencode/skills/jetson-print-device-info/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jetson-print-device-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-device-info
GitHub stars: 3.5k
Used in: 1 other repo
Token cost: ~1.3k tokens
SKILL.md length: 485 words
Files: 5
Skills in repo: 386
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 device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target.

Works in 5 steps: Capture the module model and validate it… → Extract the L4T release header line —… → Run nvpmodel -q and join its two output… → …
You need to print Jetson device info (module model
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 Device Info is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target. 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. 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 device info (module model
Current power mode) from a running Jetson target

Example prompts

“/jetson-print-device-info”

Workflow steps

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

Capture the module model and validate it is a Jetson target — exit early otherwise
Extract the L4T release header line — skip the rest of the file (long list of library SHAs)
Run nvpmodel -q and join its two output lines (NV Power Mode: and the mode number) onto one line. paste -sd only uses the first char of…
Print the kernel version and uptime
Print the OS version (prefer lsb_release, fall back to /etc/os-release)

What it can do on your machine

Read from SKILL.md and the folder at commit dfdd080. 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 Device Info loads about 1.3k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
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 dfdd080, republished under its Apache-2.0 licence (© NVIDIA). 485 words, ~1,299 tokens.

Download SKILL.mdSave it as .claude/skills/jetson-print-device-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-device-info
description: Use when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target. This is an example skill.
version: 0.0.1
license: Apache-2.0
metadata.author: Jetson Team
metadata.tags: jetson, device, info
metadata.languages: bash
metadata.data-classification: public

jetson-print-device-info

Prints a concise summary of the Jetson device this skill runs on.

This skill is intended as a reference example for the jetson-device-skills repo and the NVIDIA-wide skills CI. It runs on the Jetson target (not the host PC) and performs read-only inspection — useful as a baseline capture before running performance tests.

Purpose

Capture a baseline snapshot of a Jetson target's software stack and power mode before running performance, regression, or compatibility tests.

When to use

Starting a performance run and you want a captured baseline of the device's software stack and power mode.
Verifying that a freshly flashed Jetson matches an expected L4T / JetPack version.

Prerequisites

Running on a Jetson target (not the host PC).
Standard CLIs available: tr, cat, uname, uptime, lsb_release (or /etc/os-release).
nvpmodel available for power mode (optional — skill falls back gracefully).

Inputs

None. The skill reads only from the local Jetson filesystem and standard CLIs.

Instructions

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

Capture the module model and validate it is a Jetson target — exit early otherwise:

bash

# Device-tree strings are null-terminated, so strip NULs before printing.
model=$(tr -d '\0' < /proc/device-tree/model 2>/dev/null)
case "$model" in
  *Jetson*) ;;
  *) echo "Not running on a Jetson target (model: '${model:-unknown}')"; exit 1 ;;
esac
echo "$model"

Extract the L4T release header line — skip the rest of the file (long list of library SHAs):

bash

head -1 /etc/nv_tegra_release 2>/dev/null || echo "L4T release info not found"
# Equivalent: grep -m1 '^# R' /etc/nv_tegra_release

Run nvpmodel -q and join its two output lines (NV Power Mode: <name> and the mode number) onto one line. paste -sd only uses the first char of its delimiter, so use awk to insert the literal / separator:
bash
```
nvpmodel -q 2>/dev/null | awk 'NR==1{a=$0; next} {print a" / "$0}' \
  || echo "nvpmodel not available"
```
Print the kernel version and uptime:
bash
```
uname -r
uptime -p
```

Print the OS version (prefer lsb_release, fall back to /etc/os-release):

bash

lsb_release -ds 2>/dev/null || (. /etc/os-release && echo "$PRETTY_NAME") || echo "OS version not found"

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

Output format

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

text

Model:           <device-tree model string>
L4T release:     <release header line>
Power mode:      <nvpmodel name> / <mode number>
Kernel:          <uname -r>
Uptime:          <uptime -p>
OS version:      <lsb_release / /etc/os-release output>

Examples

Example output on an Orin AGX dev kit (L4T R36 / Ubuntu 22.04):

text

Model:           NVIDIA Jetson AGX Orin Developer Kit
L4T release:     # R36 (release), REVISION: 3.0
Power mode:      NV Power Mode: MAXN / 0
Kernel:          5.15.136-tegra
Uptime:          up 2 hours, 14 minutes
OS version:      Ubuntu 22.04.4 LTS

Example output on an AGX Thor (L4T R39 / Ubuntu 24.04):

text

Model:           NVIDIA Jetson AGX Thor Developer Kit
L4T release:     # R39 (release), REVISION: 0.0
Power mode:      NV Power Mode: 120W / 1
Kernel:          6.8.0-tegra
Uptime:          up 12 minutes
OS version:      Ubuntu 24.04 LTS

Error handling

Each command falls back to a clearly labeled "... not found" / "... not available" string if the underlying file or binary is missing — the skill never errors out mid-report. If /proc/device-tree/model is missing or does not contain a Jetson string, exit early with a clear "not running on a Jetson target" message.

Limitations

Read-only inspection only — does not detect GPU/CPU clocks, thermal state, or per-rail power.
nvpmodel output format varies between L4T versions; the skill prints it verbatim rather than parsing.

Troubleshooting

Error: /proc/device-tree/model: No such file or directory Cause: Running on a host PC, not a Jetson target. Solution: Run the skill on the Jetson device directly (e.g. via SSH).
Error: nvpmodel: command not found Cause: L4T BSP not installed, or running in a minimal container without nvpmodel. Solution: Expected on non-Jetson or stripped environments — the skill prints "nvpmodel not available" and continues.

Notes

Read-only. Do not change power mode, install packages, or modify any files.
If the skill is invoked on a host PC by mistake, /proc/device-tree/model will not contain a Jetson model string — detect that and exit with a clear message rather than printing misleading info.

Files

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

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

Open the folder on GitHubat commit dfdd080

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in NVIDIA/skills, which our catalogue first saw on October 7, 2026.

NVIDIA-AI-IOT/jetson-device-skillsskills/jetson-print-device-info

Compare with similar skills

Jetson Print Device 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 Device Info compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Jetson Print Device Info this skillNVIDIA/skills	3.5k	1 repos	~1.3k	Automated safety check: Pass	Apache-2.0	yesterday
Fla Triton To Gluonfla-org/flash-linear-attention	5.8k	—	~4.2k	Automated safety check: Pass	MIT	today
Megatron-LM on SLURMNVIDIA/Megatron-LM	18k	—	~1.8k	Automated safety check: Pass	Apache-2.0	today
DGX Spark Memory and Thermal Opswshobson/agents	40k	—	~2k	Automated safety check: Pass	MIT	5 days ago
DGX Spark Training Gotchaswshobson/agents	40k	—	~2k	Automated safety check: Pass	MIT	5 days ago
Cosmos Policy EvaluationOrchestra-Research/AI-Research-SKILLs	13k	—	~3.7k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Fla Triton To Gluon
fla-org/flash-linear-attention
Workflow for porting an existing Triton kernel in fla/ops/ to Gluon (triton.experimental.gluon) to gain explicit control over tensor layouts, shared memory, async data movement (cp.async / TMA), MMA…
5.8k GitHub stars~4.2k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Megatron-LM on SLURM
NVIDIA/Megatron-LM
Official
Shows how to launch distributed Megatron-LM training on a SLURM cluster: sbatch skeleton, torch.distributed.run setup, CUDA_DEVICE_MAX_CONNECTIONS rules and failure diagnosis.
18k GitHub stars~1.8k tokensUpdated today
AI & LLM EngineeringAuto-check passed
DGX Spark Memory and Thermal Ops
wshobson/agents
Plans memory headroom, works through out-of-memory failures and watches temperature and power during long ML training jobs on NVIDIA DGX Spark.
40k GitHub stars~2k tokensUpdated 5 days ago
AI & LLM EngineeringAuto-check passed
DGX Spark Training Gotchas
wshobson/agents
Preflight checks and diagnosis for ten known failure modes of ML training on NVIDIA DGX Spark's GB10, spanning launch errors, memory, thermals, bandwidth and precision.
40k GitHub stars~2k tokensUpdated 5 days ago
AI & LLM EngineeringAuto-check passed
Cosmos Policy Evaluation
Orchestra-Research/AI-Research-SKILLs
Sets up and runs NVIDIA Cosmos Policy evaluations on the LIBERO and RoboCasa simulators, including headless GPU rendering and inference latency profiling.
13k GitHub stars~3.7k tokensUpdated 3 mo ago
AI & LLM EngineeringAuto-check passed
OpenVLA-OFT Fine-Tuning
Orchestra-Research/AI-Research-SKILLs
Fine-tunes and evaluates OpenVLA-OFT and OFT+ robot policies with LoRA and continuous action heads on LIBERO simulation and ALOHA real-robot setups.
13k GitHub stars~3.7k tokensUpdated 3 mo ago
AI & LLM EngineeringAuto-check passed

More from NVIDIA/skills

All 386 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.5k 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.5k 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.5k 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.5k 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.5k 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.5k GitHub stars~2.7k tokensUpdated yesterday
Auto-check: notes

Works with

NVIDIA AI Platform

Questions about Jetson Print Device Info

What does Jetson Print Device Info do?

A skill your agent uses when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target. Jetson Print Device Info is an agent skill from NVIDIA/skills, published by the product's own GitHub organization. Use when you need to print Jetson device info (module model, L4T version, kernel, OS version, current power mode) from a running Jetson target.

When should I use Jetson Print Device Info?

Jetson Print Device Info fits situations like: you need to print Jetson device info (module model; current power mode) from a running Jetson target.

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

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

How do I install Jetson Print Device Info in Codex?

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

Can I use Jetson Print Device 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-device-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-device-info, .gemini/skills/jetson-print-device-info, .github/skills/jetson-print-device-info and .opencode/skills/jetson-print-device-info in your project.

What does Jetson Print Device Info need to run?

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

Does Jetson Print Device 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 Device 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 Device Info use?

Jetson Print Device 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 Device Info use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Device Info?

Skills that share tags, products or a category with Jetson Print Device Info: Fla Triton To Gluon (fla-org/flash-linear-attention, 5.8k stars), Megatron-LM on SLURM (NVIDIA/Megatron-LM, 18k stars), DGX Spark Memory and Thermal Ops (wshobson/agents, 40k stars) and DGX Spark Training Gotchas (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jetson Print Device Info?

NVIDIA (a GitHub organization, an official publisher) maintains it in NVIDIA/skills, which has 3,546 GitHub stars. The repository holds 386 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 Device 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-device-info

Purpose

When to use

Prerequisites

Inputs

Instructions

Output format

Examples

Error handling

Limitations

Troubleshooting

Notes

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from NVIDIA/skills

Related

Questions about Jetson Print Device Info