CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jetson-customize-usb

Enable/disable Jetson USB2/USB3 SS ports via kernel-DT overlay. 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
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/jetson-customize-usb/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.

A well-engineered overview body: it front-loads the load-bearing three-place lockstep rule and companion cascade, gives exact DT paths and error signatures for recovery, and defers full procedural detail to real, clearly-signaled reference files. The only real criticism is mild repetition of the core pattern and ownership boundaries across sections.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific with no padding and no explanation of concepts Claude already knows (Tegra xusb architecture, companion rules, and exact error codes are genuinely non-obvious). It falls short of anchor 5 only because the three-place lockstep pattern and uphy-ownership boundary are repeated across Purpose, Overview, Procedure, and Limitations where some consolidation could trim tokens; it is well above anchor 3's 'some unnecessary explanation'.

4 / 5

Actionability

Concrete guidance throughout: exact DT node paths (xusb_padctl/ports/usb<2|3>-N, bus@0/usb@<addr>.phys), tool names (dtc, fdtoverlay, pin_verifier.py), file destinations, and exact failure strings with fixes ("tegra-xusb: failed to enable PHYs: -19" → Rule B violated; "FDT_ERR_NOTFOUND" → use target-path). It sits at anchor 4 rather than 5 because the fully executable step-by-step and overlay fragment examples are deferred to references/procedure.md, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

The six-step procedure is clearly sequenced with explicit validation checkpoints and refusal conditions ("Refuse the run if either is missing", "Refuse to commit an SS-enable until uphy run-state shows the lane allocated", post-merge invariants after fdtoverlay). The Troubleshooting section provides genuine error→cause→fix feedback loops keyed to exact kernel/compiler messages, matching anchor 5's explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

The body is a true overview — summary procedure, key rules, limitations, troubleshooting — that delegates detail to one-level-deep references (procedure.md, gotchas.md, run-state-sidecar.md, usb-architecture.md, usb-dt-bindings.md), all of which exist in the bundle and each with a one-line description in the References section. This matches anchor 5's clear overview with well-signaled references and easy navigation; no content that belongs in a separate file is inlined.

5 / 5

Total

18

/

20

Passed

Description

57%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 highly specific and well-bounded within the Jetson BSP niche, with excellent explicit disambiguation from sibling skills. Its weakness is the missing positive trigger guidance — it says what it does and what it does not cover, but never when to invoke it — which caps completeness and leaves common natural trigger phrases absent.

Suggestions

Add a positive 'Use when...' clause with natural trigger phrases, e.g. "Use when the user asks to enable/disable USB ports, set USB role or host/device mode, wires VBUS-EN/OC pins, or fixes a USB port that fails to enumerate on a custom Jetson carrier."

Mention 1-2 more concrete capabilities to lift specificity, such as "capture per-port wiring (VBUS-EN / OC / CC GPIOs) and set port role/speed" alongside enable/disable.

Include user-recognizable symptom terms like 'lsusb empty' or 'USB port not enumerating' so the description matches how users actually describe the problem.

DimensionReasoningScore

Specificity

"Enable/disable Jetson USB2/USB3 SS ports via kernel-DT overlay" names the domain and one concrete action-pair with its mechanism, but stops short of the several specific actions the skill actually performs (role change, VBUS-EN/OC/CC wiring, companion-graph resolution). It names 1-2 actions rather than listing several, so it fits anchor 3 and not the more comprehensive anchor 4.

3 / 5

Completeness

The "what" is clear and concrete, but the only trigger guidance is negative ("Do NOT use for UPHY lane allocation or ODMDATA edits") — there is no positive "Use when..." clause. Per the judging guideline that a missing explicit trigger clause caps completeness at 3, this cannot score 4 even though the boundary statement adds some routing value.

3 / 5

Trigger Term Quality

Terms like "Jetson", "USB2/USB3 SS ports", "kernel-DT overlay", "UPHY lane allocation", and "ODMDATA" are natural for this BSP niche, but common user phrasings such as "enable USB", "disable USB port", "USB not enumerating", or "USB role/host mode" are absent. Some relevant keywords exist but variations and simpler synonyms are missing, matching anchor 3 rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Enable/disable Jetson USB2/USB3 SS ports via kernel-DT overlay" carves out a clear, narrow niche, and the explicit "Do NOT use for UPHY lane allocation or ODMDATA edits" disambiguates the two closest sibling skills. Conflict risk is minimal, matching anchor 5; anchor 4's 'minor overlap risk with closely related skills' is weaker than what the explicit boundary already provides.

5 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 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

Total

13

/

16

Passed

Repository

NVIDIA/skills

Path

skills/jetson-customize-usb/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.