dotnet-inspect-metadata

Query raw ECMA-335 assembly metadata — discover table and heap sections, inspect decoded rows and handles, address table or heap coordinates, and project bounded machine-readable results.

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

Quality

Content

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

The content is an exemplar of a lean, actionable inspection skill: copy-paste commands, no concept over-explanation, and a well-structured discover→query→inspect flow with error conditions surfaced.

Dimension	Reasoning	Score
Conciseness	The body is lean and purposeful — it references ECMA-335 concepts (tables, heaps, handles, row ids) without re-explaining them, and every line earns its place with no padding.	5 / 5
Actionability	Multiple copy-paste-ready 'dnx dotnet-inspect' commands with real flags cover the common cases — discovery, table queries with --rows/--columns, heap inspection, and coordinate addressing.	5 / 5
Workflow Clarity	A clear discover→query→inspect-heaps sequence is present with explicit failure modes surfaced ('ambiguous and fails', 'rejected by -S'), though it stops short of a full validate→fix→retry checkpoint loop.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the self-contained body is organized into clean sections ('Discover before reading', 'Query one table', 'Inspect heaps') with no nested references.	5 / 5
	Total	19 / 20 Passed

Description

67%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 with strong concrete action verbs and a clear niche, but it lacks any explicit 'when to use' trigger guidance and leans on technical jargon rather than natural user phrases.

Suggestions

Add a 'Use when...' clause stating when Claude should reach for this skill, e.g. 'Use when API views are too high-level and you need raw .NET assembly metadata tables, heaps, or handles.'

Include natural trigger terms and synonyms a user would actually say — '.NET', 'DLL', 'assembly', 'metadata tables' — alongside the ECMA-335 jargon to improve trigger_term_quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'discover table and heap sections', 'inspect decoded rows and handles', 'address table or heap coordinates', 'project bounded machine-readable results' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' trigger clause or equivalent explicit 'when' guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Domain-accurate keywords ('ECMA-335', 'assembly metadata', 'tables', 'heaps') are present but jargon-heavy, missing natural synonyms/extensions a user might actually say ('.NET', 'DLL', 'IL').	3 / 5
Distinctiveness Conflict Risk	The niche is extremely narrow and specific — raw ECMA-335 metadata table/heap inspection — making it clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: richlander/dotnet-inspect
Path: skills/metadata/SKILL.md
Commit: 71591ae

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.