Jetson Video Capability
NVIDIAOfficialCreated by Vinit BansalDistributed by NVIDIA
- Skill
- Tool integration
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured methodology for determining video codec support on NVIDIA Jetson platforms. It integrates data from live API queries, authenticated NVIDIA sample reports, and official documentation to provide a verified capability verdict. The skill enforces strict separation between raw API data, operational evidence, and product-support documentation, ensuring that users receive accurate information regarding codec, profile, chroma, and bit-depth support while avoiding unauthorized assumptions about DRM or performance metrics.
What it does
- Queries PyNvVideoCodec APIs for encoder and decoder capabilities.
- Extracts reports from authenticated native NVIDIA video codec samples.
- Reconciles live findings against official NVIDIA support matrices.
- Classifies capability evidence into API, sample, and documentation categories.
- Provides a structured verdict on codec support for specific hardware configurations.
- Handles scope-gating for DRM and objective quality metrics.
When to use it
- When you need to verify if a specific codec, profile, or bit-depth is supported on a Jetson device.
- When reconciling conflicting information between API outputs and official documentation.
- When preparing a technical report on hardware video encoding/decoding capabilities.
- When you need to determine if a specific video operation is documented as supported.
Advantages
- Ensures high-fidelity results by cross-referencing multiple authoritative sources.
- Prevents incorrect assumptions by strictly separating API results from product support.
- Provides a clear, standardized framework for reporting hardware capabilities.
- Maintains integrity by relying on authenticated samples and official documentation.
Usage examples
- “Check if HEVC 10-bit decoding is supported on my Jetson.”
- The agent will query the relevant API, check the official support matrix, and report whether the capability is documented and operationally verified.
- “What are the encoder capabilities for AV1 on this Jetson?”
- The agent will provide a report based on the native Video Codec SDK or PyNvVideoCodec, reconciled against official NVIDIA documentation.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/jetson-video-capability/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip jetson-video-capability.zip -d .agents/skills
Documentation by Vinit Bansal
Jetson Video Capability
Keep three authorities separate:
API query: raw fields, never operation or product-support proof.
Authenticated NVIDIA sample: report or exact operation evidence.
Applicable NVIDIA documentation: product-support verdict.
Scope gates
For a request solely for PSNR, SSIM, or other objective quality metrics, say this skill does not provide them and a separately authorized quality workflow is required; do nothing else.
For Netflix, Widevine, PlayReady, or clearly content-protected streaming, state only that this skill covers hardware encode/decode of user-supplied non-DRM bitstreams, not content-DRM playback. Do not claim whether the service works, describe Jetson certification, CDM, or secure-playback requirements, or recommend a browser, DRM module, workaround, or bypass; then stop. An unqualified “DRM” may mean Linux DRM/KMS; ask which meaning if context does not resolve it.
A bare “video SDK” is ambiguous: ask native Video Codec SDK, PyNvVideoCodec, or both before probing. An otherwise unqualified capability request uses the native-preferred fallback in surface-selection-contract.md.
Read-only discovery
Capability work depends on jetson-video-setup for a fresh, read-only
installation check. Invoke that skill through public dispatch and consume its
reported exact native package/Samples root or exact PyNvVideoCodec interpreter,
version, and loaded module path. Do not locate or import setup's files. A
missing or mismatched surface is unknown/not_ready, never codec unsupported;
route repair to setup without mutating anything here.
Engine capability queries belong here, not in setup. For PyNvVideoCodec, use
the exact selected interpreter to call the public GetEncoderCaps and
GetDecoderCaps APIs as described in
capability-queries.md. A broad encoder
catalog covers H.264, HEVC, and AV1; a broad decoder catalog covers all ten
families across four chroma formats and three bit depths (120 exact tuples).
A bounded request queries only named members of the applicable catalog set.
Preserve every scoped record, error, and GPU ordinal. Nonzero-GPU helper results
remain unknown when the public helper selects only GPU 0.
For native reports, reuse authenticated package-owned binaries or build only
the required report target in a fresh user-owned tree, then run
AppEncCuda -ec and/or AppDec -dc using the build, identity, and grammar
rules in the capability reference. A query-only request does not authorize
package installation or an encode/decode operation. If the package, source,
tool, interpreter, or runtime-library identity cannot be established, report
the result unknown and name the missing setup prerequisite.
Decision flow
Classify scope and selected surface before any probe.
Query only the selected surface. Preserve raw records, errors, exact GPU, release, interpreter/binary identities, argv, and evidence classification.
Resolve the most exact live product identity using the device-tree paths and NUL handling in capability-queries.md, then cross-check it against NVIDIA's current Video Encode and Decode Support Matrix and the release-matched SDK 13.0 NVENC or NVDEC application note. Never infer SKU from memory, engine count, capability fields, or operation behavior. Preserve source URL, retrieval date, table title, exact row/column labels, and cell value, using that reference's manual capture record. Generic family identity stays non-exact; use candidate-row consensus only when every authenticated candidate agrees.
Report documentation
Noas the final unsupported product verdict even if an API or diagnostic operation is positive; this ends the normal availability check. DocumentationYesestablishes documented support; live availability additionally needs the matching authenticated operation. Missing, unretrievable, or conflicting documentation remains unknown. When documentation is unknown, do not present positive capability fields as available options: label each affected codecunknownbeside them and state the retrieval failure with the verdict.For a PyNvVideoCodec encode-availability operation, request setup's
full-samplesprofile and carry its exact interpreter into the recipe and pipeline stages. Do not select the smaller decode-performance/smoke profile.Run an exact operation only when the user requests live availability and documentation is positive or unknown, or explicitly requests a diagnostic despite a negative verdict. A diagnostic under documentation
Noreports onlyoperation_verifiedoroperation_failedfor that exact tuple and never changes the unsupported product verdict. A tuple is the exact surface, GPU, codec, profile, chroma, bit depth, dimensions, input format, and control set tested. Resolve one recipe withjetson-video-recipe, then usejetson-video-pipelinefor encode followed by independent decode of the exact output identity. A failed tuple never generalizes to the product.
Evidence rules
GetEncoderCapssuccess iscapability_reported,supported=null,operation_status=not_tested.GetDecoderCapsbIsSupported=1/0records raw API true/false and whether returned limits apply; neither value is the documentation verdict.Missing enums, calls, fields, prerequisites, or nonzero-GPU authority are unknown, not unsupported.
Native
-ec/-dctext isofficial_sample_report; preserve raw values and never rewrite them as API or product claims.When reporting Main10 support, note that NVENC can convert verified 8-bit input internally and that P010 is the exact no-input-bit-depth-conversion path; a live claim still requires an authenticated 10-bit operation.
AV1 output is operation evidence only after the pipeline's package-owned decoder consumes the exact artifact and reports the expected frame count.
For a VP9 encode question, report only that VP9 remains a decoder family and no released NVENC route exists. Do not add a generic list of other encoders or offer a diagnostic encode operation.
Presets, tuning, package presence, throughput, and successful concurrent streams do not establish codec support or NVENC/NVDEC engine count.
Codec/API capability, NVENC/NVDEC availability, and successful bounded operations do not establish DMA-BUF, NvSciBuf, CUDA-memory sharing, zero copy, or cross-stage synchronization compatibility.
For a Python API query, create a short task-local program from this Markdown and the installed public SDK, run it with the exact selected interpreter, and keep its raw output with the result. Installation belongs to setup and operation validation belongs to pipeline. This skill owns engine queries, classification, documentation reconciliation, and the compact direct report above.
Files
- ATTRIBUTION.mdAdded by AutoGineer933 B
- BENCHMARK.md7.6 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md7.6 KiB
- evals/evals.json3.5 KiB
- references/capability-queries.md9.4 KiB
- references/surface-selection-contract.md6.0 KiB
- skill-card.md4.5 KiB
- skill.oms.sig5.0 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
- Vinit Bansal
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/jetson-video-capability · 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 Vinit Bansal or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download jetson-video-capability.zip