jetson-customize-camera

Enable MIPI/GMSL camera sensors on a Jetson Thor or Orin custom carrier by rendering a kernel-DT overlay from the in-tree sensor DTSI. Do NOT use for UPHY lane allocation or ODMDATA edits.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/jetson-customize-camera/SKILL.md

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a high-quality, expert-targeted skill body: executable commands, rigorous validation gates with feedback loops, and clean one-level-deep progressive disclosure into real bundle files. The only minor lever is tightening the slight overlap between the in-body procedure summary and references/procedure.md.

Dimension	Reasoning	Score
Conciseness	The body is dense and expert-level, assuming Claude's knowledge of DT overlays, NVCSI, and the L4T tree, with no padding of basic concepts; a few summary lists overlap slightly with the detailed procedure file and could be trimmed, but it is efficient overall.	4 / 5
Actionability	Provides fully executable, copy-paste-ready bash (cpp/dtc/fdtoverlay invocations, git commit, awk/sed splice recipes) plus concrete run-state JSON and headline templates that cover the common clone and custom-sensor cases.	5 / 5
Workflow Clarity	Steps 1-7 are explicitly sequenced with multiple named validation gates (pre-compile single-fragment gate, post-compile deep-tree uniqueness gate, fdtoverlay exit-zero, grep presence checks) and clear feedback loops (cpp failure -> re-run init-source; FDT_ERR_NOTFOUND -> fix labels/target-path).	5 / 5
Progressive Disclosure	The SKILL.md is a clear overview pointing one level deep to real, well-signaled bundle files (procedure.md, csi-dt-bindings.md, overlay-template.md, camera-overlay-templates/) and sibling skills; references are listed explicitly and the procedure is split out appropriately for easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-bounded with a clear domain and useful negative-scope guidance, but it lacks an explicit 'Use when...' trigger clause and omits natural user-facing trigger phrases like 'enable camera' or 'CSI'. Adding a concrete 'Use when...' sentence with those trigger terms would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause naming the natural trigger phrases users actually say (e.g. 'Use when enabling CSI/MIPI/GMSL cameras, wiring Hawk/Owl/IMX sensors, or bringing up tegra-capture-vi/NVCSI on a custom carrier').

Add common synonyms and concrete sensor examples (Hawk, Owl, IMX274) so trigger-term coverage reaches the natural-language layer, not just the technical layer.

Optionally surface the verification/commit output (one kernel-DT overlay commit) so the 'what' side is comprehensive rather than focused only on the rendering action.

Dimension	Reasoning	Score
Specificity	Names the domain (MIPI/GMSL camera sensors on Jetson Thor/Orin custom carriers) and several concrete actions (rendering a kernel-DT overlay from in-tree sensor DTSI), with minor coverage gaps such as no explicit mention of verification or multi-sensor bring-up.	4 / 5
Completeness	The 'what' is clear (render a kernel-DT overlay from in-tree DTSI) but there is no explicit 'Use when...' trigger clause; the boundary guidance ('Do NOT use for UPHY lane allocation or ODMDATA edits') only implies the when and the rubric caps completeness at 3 without an explicit trigger clause.	3 / 5
Trigger Term Quality	Includes relevant keywords ('MIPI', 'GMSL', 'camera sensors', 'Jetson Thor', 'Orin', 'kernel-DT overlay') but is missing the common natural phrases a user would say (e.g. 'enable camera', 'CSI', 'wire a sensor') and file-extension-style synonyms.	3 / 5
Distinctiveness Conflict Risk	The MIPI/GMSL camera-sensor niche plus the explicit exclusion of UPHY lane allocation and ODMDATA edits make it mostly distinct from sibling BSP skills, with only minor overlap risk against other kernel-DT-overlay skills.	4 / 5
	Total	14 / 20 Passed

Validation

75%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 9 suspicious	Warning

	Total	12 / 16 Passed

Repository: NVIDIA/skills
Path: skills/jetson-customize-camera/SKILL.md
Commit: c3168ca

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.