CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dotnet-inspect-metadata

Inspect raw ECMA-335 metadata in a .NET assembly; discover tables and heaps, read decoded rows and handles, locate exact coordinates and project bounded machine-readable results.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 body is an exemplary lean skill: executable commands throughout, precise tool-specific details, an explicit discover-before-read sequence, and honest coverage caveats. The only minor gap is the lack of explicit validation checkpoints, which matter little for read-only inspection.

DimensionReasoningScore

Conciseness

The body is lean and dense with tool-specific facts ('no verbosity or base category renders them automatically', 'Ranges are inclusive, so 100..199 selects 100 rows') with no padding or explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Every section provides copy-paste-ready executable commands (e.g. 'dnx dotnet-inspect -y -- library MyLib.dll -D @Metadata --effective' and 'library address "#Strings:0x1a4" --library MyLib.dll') covering the common discovery, query, and heap-inspection cases.

5 / 5

Workflow Clarity

A clear sequence is established ('Discover before reading', 'use explain ... then follow the returned resource') with failure-recovery guidance ('ambiguous and fails. Choose one DLL with library'), but there are no explicit validation checkpoints, matching the 'clear sequence with most checkpoints' anchor. The operations are read-only, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

This is a compact, single-topic skill with well-organized sections (discover, query, heaps) and no need for external reference files; the simple-skill exception applies and the structure makes navigation easy.

5 / 5

Total

19

/

20

Passed

Description

70%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 specific, appropriately technical, and highly distinctive within a well-defined niche. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness and weakens discoverability.

Suggestions

Add an explicit trigger clause, e.g. 'Use when API views are too high-level and you need raw .NET assembly metadata tables, heaps, or token coordinates.'

Include common user phrasings and file extensions such as '.dll', 'CLR', or 'assembly metadata' to broaden natural trigger coverage.

Replace or unpack the abstract phrase 'project bounded machine-readable results' with a concrete action like 'output selected rows as TSV or JSONL'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('discover tables and heaps', 'read decoded rows and handles', 'locate exact coordinates'), but 'project bounded machine-readable results' is jargon-abstract, leaving minor gaps in concrete coverage rather than the comprehensive clarity of the top anchor.

4 / 5

Completeness

The 'what' is clear (inspect raw ECMA-335 metadata, discover tables/heaps, read rows and handles), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural domain terms like '.NET assembly', 'metadata', 'ECMA-335', 'tables and heaps' are present, but common user variations such as '.dll', 'CLR', or 'assembly metadata' are missing, matching the 'good coverage with a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Raw ECMA-335 metadata inspection is a clearly delineated niche with distinct technical triggers, making conflict with other skills unlikely.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.