CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

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, token-efficient instruction skill: the body stays at summary altitude while delegating full detail to two real reference files, and the workflow is sequenced with unusually strong validation gates and destructive-operation safeguards. Remaining blemishes are a twice- or thrice-repeated ODMDATA prohibition, a vestigial "Step 7" placeholder, and several out-of-bundle reference paths that cannot be verified from this bundle.

Suggestions

State the "Do NOT edit ODMDATA" prohibition once (Overview) and reference it elsewhere in a few words instead of repeating the full token list in Step 6.

Remove or renumber the vestigial "Step 7 — (Step folded into Step 6…)" line to avoid a placeholder in the numbered procedure.

Verify or prune the out-of-bundle references (../../scripts/pin_verifier.py, ../../references/*, ../../context/*, sibling SKILL.md paths), or annotate them as cross-skill pointers, so every referenced path resolves from the bundle.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no space is wasted explaining PCIe, device trees, or ODMDATA basics, and tables/steps carry real content per token. The "do not edit ODMDATA" prohibition and its token list (pcie@N_status, pcie@N_max-link-speed, pcie@N_pcie-mode, …) are each repeated nearly verbatim in the Overview and again in Step 6, which is trimmable redundancy, keeping it just below anchor 5.

4 / 5

Actionability

Concrete, executable specifics throughout: exact commands ("dtc", "fdtoverlay", "dmesg | grep pcie"), exact net labels ("PEX<N>__*", "PE<N>_CLKREQ_L"), exact sidecar paths, the overlay fragment marker, and prerequisite refusal checks. Full step-by-step detail is delegated to references/procedure.md, so the body alone has minor gaps versus anchor 5's copy-paste-ready standard.

4 / 5

Workflow Clarity

The nine-step sequence is explicit with validation checkpoints at every risky point: refuse-if-missing gates for <uphy-state>, schematic and pinmux docs; pre-flight dtc + fdtoverlay before commit; a commit preview gate; the Step 8 ODMDATA-vs-overlay cross-check with stop-and-ask on contradiction ("Never run git reset --hard autonomously"); and a troubleshooting section with recovery paths. This matches anchor 5's clear-sequence-with-explicit-validation-and-feedback-loops profile.

5 / 5

Progressive Disclosure

The body is a genuine overview: full procedure and gotchas are split into two well-annotated, one-level-deep reference files (references/procedure.md, references/gotchas.md — both present in the bundle), clearly signaled by section. However, many referenced paths in the References section (../../scripts/pin_verifier.py, ../../references/*, ../../context/*, and five sibling SKILL.md files) do not exist in the actual bundle, so navigation from this file alone is not fully verifiable — good structure, minor gaps.

4 / 5

Total

17

/

20

Passed

Description

78%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 tight, highly specific description with strong trigger keywords and excellent negative-boundary disambiguation from sibling skills. Its main weaknesses are the absence of a positive 'Use when…' trigger clause and a slight over-claim: it says the customization happens "via ODMDATA + kernel-DT overlay" while the body explicitly forbids this skill from editing ODMDATA, which could mislead routing for ODMDATA-only requests.

Suggestions

Add an explicit positive trigger clause, e.g. "Use when the user asks to enable/disable a PCIe controller, set num-lanes, or change link speed on a Jetson Thor/Orin custom carrier, or when a slot doesn't enumerate or trains at the wrong width/speed."

Correct the mechanism claim "via ODMDATA + kernel-DT overlay" to reflect that the skill only emits kernel-DT overlay fragments and cross-checks against ODMDATA committed by /jetson-customize-uphy (e.g. "…via kernel-DT overlay, cross-checked against ODMDATA").

Add one or two common user phrasings ("M.2 slot", "PCIe link width") to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and several concrete per-controller actions ("enable / disable / lanes / link-speed") with a concrete mechanism ("via ODMDATA + kernel-DT overlay") and platform scope ("Jetson Thor or Orin custom carrier"). It stops short of anchor 5 because "via ODMDATA" over-claims relative to the skill body, which states it "MUST NOT edit ODMDATA" and only emits the kernel-DT overlay.

4 / 5

Completeness

The 'what' is clearly stated (per-controller PCIe enable/disable/lanes/link-speed), and 'when' is partially covered by the platform scope ("for a Jetson Thor or Orin custom carrier") plus an explicit negative trigger ("Do NOT use for UPHY lane allocation or endpoint-mode bring-up"). There is no positive 'Use when…' clause, which keeps it below anchor 5 and slightly above the anchor-3/4 boundary given the explicit negative trigger guidance.

4 / 5

Trigger Term Quality

Good natural keyword coverage users would actually say: "PCIe", "enable", "lanes", "link-speed", "Jetson Thor or Orin", "custom carrier". A few natural terms are missing (e.g. "M.2", "slot doesn't enumerate", "num-lanes"), so it falls between anchors 4 and 5 but noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

A clear niche (per-controller PCIe on Jetson Thor/Orin custom carriers) with explicit disambiguation from sibling skills ("Do NOT use for UPHY lane allocation or endpoint-mode bring-up") — minimal conflict risk. Matches anchor 5 cleanly; nothing generic remains that would overlap other skills.

5 / 5

Total

17

/

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

Warning

Total

12

/

16

Passed

Repository

NVIDIA/skills

Path

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