CtrlK
BlogDocsLog inGet started
Tessl Logo

ilverify-failure

Fix ILVerify baseline failures when IL shape changes (codegen, new types, method signatures). Use when CI fails on ILVerify job.

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

A compact, well-structured reference that gives the exact commands needed to update and re-verify ILVerify baselines with no wasted tokens. The only gap is the absence of an explicit error-recovery branch in the verify step.

Suggestions

In the Verify section, add a one-line error-recovery branch, e.g. 'If it still fails, inspect the new ILVerify output and rerun the update command.'

Optionally note where to find the updated .bsl files in CI artifacts so the user can confirm the baseline regenerated correctly.

DimensionReasoningScore

Conciseness

Lean and efficient: short sections, a copy-paste command, and only the non-obvious note about offset-only diffs being auto-detected; no padding or over-explanation of concepts Claude already knows.

5 / 5

Actionability

Fully executable guidance: the exact update command (TEST_UPDATE_BSL=1 pwsh tests/ILVerify/ilverify.ps1), the /run ilverify PR-comment alternative, the baseline path, and a concrete verify step.

5 / 5

Workflow Clarity

Clear sequence (update baselines then re-run to verify) with an explicit validation checkpoint ('Re-run without TEST_UPDATE_BSL=1, should pass'), but no explicit error-recovery loop spelling out what to do if verification fails.

4 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no external bundle files, organized into clearly labeled sections (When to Use, Offset-Only Differences, Update Baselines, Baselines Location, Verify).

5 / 5

Total

19

/

20

Passed

Description

87%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, third-person description that cleanly states the capability and its trigger, with concrete IL-shape change conditions. It is specific and distinctive; the only minor gap is missing file-extension synonyms in the trigger terms.

DimensionReasoningScore

Specificity

Names the concrete action ('Fix ILVerify baseline failures') plus specific trigger conditions in the parenthetical (codegen, new types, method signatures), giving several concrete anchors with minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (fix ILVerify baseline failures when IL shape changes) and 'when' (Use when CI fails on ILVerify job) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms an engineer would say ('ILVerify baseline failures', 'CI fails on ILVerify job', 'IL shape', 'codegen') but omits file extensions like .bsl and some synonyms, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (ILVerify CI job) with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/dotnet
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.