Conciseness

The body is information-dense with almost no explanation of concepts Claude already knows — every paragraph covers tool-specific semantics like "The PDB span is executable source, not a complete member boundary" and "PDBs *carry* SourceLink data; they are not SourceLink themselves". Not 5 because a few convoluted passages (e.g. the "For one package with exactly `SourceLink: Files` selected..." paragraph and the provenance-boundary sentences in the intro) could be tightened or trimmed.

Actionability

Five command blocks give fully executable, copy-paste-ready invocations covering the common cases — `dnx dotnet-inspect -y -- library System.Text.Json -S "SourceLink: Files"`, `member JsonSerializer --platform System.Text.Json Serialize:1 -S "PDB Source"`, and `--print --row 1` variants — with concrete flags (--urls, --paths, --json-array) explained inline. Not 4 because the examples span locate/fetch/print workflows and specific packages rather than leaving minor gaps.

Workflow Clarity

Sections follow a clear sequence — "Find where the source lives" → "Fetch PDB source" → "Inspect or print authored member parts" → "URL forms" — and validation behavior is described (checksum verification of fetched bodies, "Unavailable parts fail rather than selecting a substitute", missing printable documents are reported). Not 5 because the checkpoints are stated as tool behavior rather than explicit validate-then-proceed steps with error-recovery guidance; not 3 because the ordering and failure semantics are consistently made explicit.

Progressive Disclosure

The body is well-organized into focused one-level sections with no nested references and no monolithic wall of text; cross-references to the complementary `decompiler` and `signals` skills are named with their purpose. Not 5 because the document is ~135 lines with detail-heavy passages (row-selection semantics, part-name lists, URL-form options) that could live in reference files, and the sibling-skill mentions lack paths or links.

Specificity

Quotes several concrete actions — "Locate .NET source files and Member spans", "read checksum-matched content locally or remotely" — anchored to a named domain (Portable PDB, SourceLink). It falls below 5 because the trailing clause "preserving provenance and availability boundaries" is abstract rather than a concrete capability, leaving minor gaps in coverage.

Completeness

The "what" is clear (locate source files and member spans via PDB/SourceLink, read checksum-matched content), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric. Not 4 because the "when" is entirely missing rather than merely implicit.

Trigger Term Quality

Relevant keywords like ".NET", "source files", "Portable PDB", and "SourceLink" are present, but common natural variations users would say — "source code", "symbols", "decompile", "NuGet package" — are absent. Not 4 because the coverage of everyday synonyms is thin; not 2 because the terms present are ones a user with this need would plausibly say.

Distinctiveness Conflict Risk

The description occupies a clear niche — Portable PDB checksum-verified .NET source retrieval through SourceLink — with trigger terms unlikely to fire for unrelated skills. Not 4 because the specialized terminology (PDB, SourceLink, Member spans) makes overlap with generic source-reading skills minimal.