jetson-customize-pcie

Per-controller PCIe enable / disable / lanes / link-speed for a Jetson Thor or Orin custom carrier via ODMDATA + kernel-DT overlay. Do NOT use for UPHY lane allocation or endpoint-mode bring-up.

Quality

80%

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-pcie/SKILL.md

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-structured, technically dense skill body with strong workflow sequencing, explicit validation/feedback loops, and clean progressive disclosure; only minor redundancy and delegated detail keep conciseness and actionability from full marks.

Dimension	Reasoning	Score
Conciseness	Dense and assumes Claude's competence (no explaining what PCIe or DT overlays are), but the 'do not edit ODMDATA' invariant is restated across Overview, Procedure Step 6, and Limitations — minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete commands and artifacts are named (`dtc`, `fdtoverlay`, `dmesg \| grep pcie`, `pin_verifier.py`, the `/* custom-bsp: pcie:pcie@<addr> */` marker, sidecar paths), but full executable detail is delegated to references/procedure.md, leaving minor gaps in the body itself.	4 / 5
Workflow Clarity	A clearly sequenced nine-step flow with explicit validation checkpoints (pre-flight `dtc`+`fdtoverlay`, Step 8 ODMDATA-vs-overlay consistency cross-check, refuse-if-missing gates) and a feedback loop that stops and asks the user on contradictory rows rather than auto-recovering.	5 / 5
Progressive Disclosure	The body is an overview that delegates the full walkthrough to references/procedure.md and gotchas.md (both real, one level deep), with a well-signaled References section enumerating sibling skills and shared docs for easy navigation.	5 / 5
	Total	18 / 20 Passed

Description

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

A highly specific, well-bounded description with strong distinctiveness, but it lacks a positive 'Use when...' trigger clause, which caps its completeness and leaves a few natural trigger terms uncovered.

Suggestions

Add an explicit positive trigger clause, e.g. 'Use when configuring per-controller PCIe status, lane width, or link speed on a Jetson Thor/Orin custom carrier.'

Include common user synonyms such as 'PCIe controller', 'M.2/slot enumeration', and 'num-lanes' to broaden natural trigger coverage.

Optionally surface a symptom-based trigger (e.g. 'or when a PCIe slot fails to enumerate after flash') to match the body's 'When to invoke' section.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'enable / disable / lanes / link-speed' — bound to specific surfaces ('ODMDATA + kernel-DT overlay') on named hardware (Jetson Thor/Orin), giving comprehensive coverage of the stated capability set.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no positive 'Use when...' trigger clause — only a negative boundary ('Do NOT use for UPHY lane allocation or endpoint-mode bring-up'), which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural user phrasings like 'PCIe enable', 'lanes', 'link-speed', 'Jetson Thor/Orin', 'custom carrier' are present, but common variants a user might say ('PCIe controller', 'M.2', 'slot', 'num-lanes') are absent.	4 / 5
Distinctiveness Conflict Risk	A clear niche (per-controller PCIe on Jetson Thor/Orin via ODMDATA + kernel-DT overlay) with an explicit carve-out from sibling skills (UPHY allocation, endpoint bring-up), yielding minimal conflict risk.	5 / 5
	Total	17 / 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: 10 suspicious	Warning

	Total	12 / 16 Passed

Repository: NVIDIA/skills
Path: skills/jetson-customize-pcie/SKILL.md
Commit: be3d1a4

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.