CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jetson-customize-mgbe

Enable Jetson Thor 25G/10G/1G MGBE QSFP via kernel-DT overlay. Do NOT use for UPHY lane allocation or ODMDATA edits.

Quality

76%

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-mgbe/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured, expert-level skill body: clear sequencing with real validation checkpoints and feedback loops, concrete refusal conditions, and a properly split procedure into a one-level-deep reference. The main improvements are trimming the thrice-repeated UPHY/ODMDATA ownership statements and reconciling the duplicated questions.json between assets/ and references/.

DimensionReasoningScore

Conciseness

The body is dense and assumes expertise — no space is spent explaining device trees or flashing — and each gotcha is a concrete failure mode (e.g. 'mdio child needs both #address-cells = <1> AND #size-cells = <0>'). It falls short of anchor 5 because ownership of UPHY/ODMDATA is restated three times (Overview, Prerequisites, Gotchas) and the OVERLAY_DTB_FILE ordering gotcha runs long.

4 / 5

Actionability

The guidance is concrete throughout: named tools ('dtc', 'fdtoverlay', 'pin_verifier.py'), an exact sidecar filename pattern, a marker contract ('/* custom-bsp: mgbe:mgbe... */'), and an explicit refusal condition when schematic/pinmux documents are missing. It is not a 5 because the body itself contains no executable commands — the copy-paste-ready code (dtc decompile, fragment emission) lives in references/procedure.md.

4 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced with explicit validation checkpoints (pin_verifier run in Step 4, cpp/dtc/fdtoverlay pre-flight in Step 6, BPMP DTB decompile before emitting in Step 3) and a real feedback loop (pin mismatch → route to /jetson-customize-pinmux), matching the anchor for clear sequence with explicit validation and error recovery.

5 / 5

Progressive Disclosure

The SKILL.md is a genuine overview that delegates the full procedure to references/procedure.md and question schemas to questions.json, one level deep, with a well-annotated References section. Minor gaps keep it from a 5: assets/questions.json duplicates references/questions.json without being cited in the body, and several referenced paths (../../scripts/pin_verifier.py, ../../references/platform_template.yaml, sibling SKILL.mds) resolve outside this bundle and cannot be verified from its file listing.

4 / 5

Total

17

/

20

Passed

Description

65%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 distinctive within its domain, with a well-scoped negative boundary, but it omits any positive trigger guidance ('Use when...') and uses only one concrete action verb. Adding an explicit 'use when' clause with natural phrases like 'Ethernet', 'bring up the QSFP port', or 'MGBE link is down' would lift completeness and trigger-term coverage.

Suggestions

Add a positive trigger clause, e.g. 'Use when the user asks to enable 25G/10G/1G Ethernet on the Thor QSFP cage, or when ip link shows mgbe<N> down or missing after boot.'

Include common synonyms users would say — 'Ethernet', 'NIC', 'PHY', 'fiber' — alongside the existing MGBE/QSFP jargon.

Optionally mention one more concrete capability (e.g. 'emits the mdio/phy-reset-gpio overlay fragment and verifies HSIO pinmux') to move specificity from one action toward several.

DimensionReasoningScore

Specificity

Names the domain precisely ('Jetson Thor 25G/10G/1G MGBE QSFP') and one concrete action ('Enable ... via kernel-DT overlay') plus an explicit exclusion ('Do NOT use for UPHY lane allocation or ODMDATA edits'), but stops short of the several distinct actions of a 4 — no mention of PHY plumbing, pin verification, or overlay fragment authoring.

3 / 5

Completeness

The 'what' is clear (enable MGBE QSFP via kernel-DT overlay), but there is no positive 'use when' clause — only the negative 'Do NOT use for UPHY lane allocation or ODMDATA edits', which leaves the 'when' weakly implied rather than explicit, matching anchor 3 and triggering the cap for a missing explicit trigger clause.

3 / 5

Trigger Term Quality

Strong domain keywords a Jetson BSP user would naturally say: '25G', '10G', '1G', 'MGBE', 'QSFP', 'UPHY', 'ODMDATA'. Missing common synonyms like 'Ethernet', 'PHY', 'fiber', or 'network', so it falls short of the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Jetson Thor MGBE QSFP' is a clear niche, and the explicit 'Do NOT use for UPHY lane allocation or ODMDATA edits' directly disambiguates against the closest sibling skill, so conflict risk is minimal.

5 / 5

Total

15

/

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: 7 suspicious

Warning

Total

12

/

16

Passed

Repository

NVIDIA/skills

Path

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