CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

85%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.

The skill body is an exemplary overview-plus-delegation structure: dense domain expertise with no filler, a clearly sequenced 7-step workflow with explicit validation gates and error-recovery guidance, and well-verified one-level-deep references. Only minor inline redundancy (repeated ODMDATA caveat and repeated cross-reference links) keeps conciseness from a perfect score.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific, non-redundant expertise and assumes Claude's competence (no explanation of what device-tree overlays or MIPI are). Minor trimmable redundancy keeps it below the 5 anchor: the 'No ODMDATA edit' point is stated in both the Overview and Gotchas, and the bsp-customization-kernel-dtb.md reference link is repeated three times.

4 / 5

Actionability

Mostly executable guidance: concrete commands (dtc, cpp, fdtoverlay, 'v4l2-ctl --list-devices', pin_verifier.py), exact file paths, and specific error strings with fixes ('camera_common_regulator_get (null) ERR: -EINVAL' = splice the FULL sensor body). The full executable detail is delegated to references/procedure.md (verified to exist), leaving only minor gaps inline in this file.

4 / 5

Workflow Clarity

Steps 1-7 are clearly sequenced with explicit validation checkpoints ('pre-compile single-fragment gate; post-compile deep-tree uniqueness gate', fdtoverlay verification, commit-message preview gate) and error-recovery feedback loops (Gotchas maps 'cpp failure on dt-bindings/gpio/gpio.h' to re-running /jetson-init-source). This matches the clear-sequence-with-explicit-validation-and-feedback anchor.

5 / 5

Progressive Disclosure

Clean overview with a step summary whose full detail lives in references/procedure.md; every referenced bundle file (procedure.md, csi-dt-bindings.md, overlay-template.md, camera-overlay-templates/ with both .dts.tmpl files) exists as cited, references are one level deep, and each is clearly annotated with its purpose in the References section.

5 / 5

Total

18

/

20

Passed

Description

70%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 concrete, technically specific, and well-bounded with an explicit negative trigger boundary, making it highly distinct within a Jetson BSP skill suite. Its main weakness is the missing affirmative 'Use when...' clause — the invocation condition is only implied by the negative exclusions. Adding trigger phrases like 'Use when enabling CSI/MIPI/GMSL cameras on a custom Jetson carrier' would raise completeness.

Suggestions

Add an affirmative trigger clause, e.g. 'Use when the user asks to enable, wire, or bring up a MIPI, GMSL, or CSI camera sensor on a Jetson Thor/Orin custom carrier.'

Include 'CSI' and 'camera bring-up' as trigger terms, since these are the most natural phrases users would say for this task (the skill body already uses them).

Optionally state the downstream artifact ('emits one camera fragment appended to the composite custom overlay .dts') to round out coverage of the concrete actions.

DimensionReasoningScore

Specificity

Concrete actions are explicit ('Enable MIPI/GMSL camera sensors', 'rendering a kernel-DT overlay from the in-tree sensor DTSI') with a precise mechanism and platform targets (Jetson Thor/Orin custom carrier). It lists a couple of specific actions with the how, but not the multiple-action comprehensive coverage of the 5 anchor, sitting noticeably above the 1-2-actions anchor at 3.

4 / 5

Completeness

The 'what' is clear and specific, but there is no affirmative 'Use when...' trigger clause — only the negative boundary 'Do NOT use for UPHY lane allocation or ODMDATA edits'. Per the rubric guideline, a missing explicit trigger guidance caps completeness at 3; the 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('camera', 'MIPI', 'GMSL', 'Jetson Thor', 'Orin', 'custom carrier') that a Jetson BSP user would actually say, though common variations like 'CSI' and 'sensor bring-up' (which the skill body itself uses) are missing from the description.

4 / 5

Distinctiveness Conflict Risk

Clear niche (MIPI/GMSL camera enablement on Jetson Thor/Orin custom carriers) with an explicit exclusion clause ('Do NOT use for UPHY lane allocation or ODMDATA edits') that separates it from adjacent BSP skills, giving minimal conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

75%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.