CtrlK
BlogDocsLog inGet started
Tessl Logo

error-consolidation-verify

Verifies a consolidated C# diagnostic article against Roslyn and checks See also links. Use as the final validation and correction phase.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/error-consolidation-verify/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a concise, actionable, well-structured verification procedure, but it is missing an explicit re-validation feedback loop after the batch fix step.

Suggestions

Add a re-verification checkpoint after Step 4: re-run the Step 3 comparison to confirm every fix now matches Roslyn before presenting results.

Include a concrete search command (e.g. a grep/rg snippet for ErrorCode.cs) to make the lookup fully copy-paste executable.

Add a brief 'Stop conditions' note for when See also targets are missing from the branch so the fix step is unambiguous.

DimensionReasoningScore

Conciseness

Lean procedural guidance that assumes Claude's competence — no padding about what C# or Roslyn is — with code/XML examples that earn their place; only minor tightening opportunities.

4 / 5

Actionability

Provides exact file paths (ErrorCode.cs, CSharpResources.resx), a precise lookup procedure, and a concrete report-table format, though it stops short of giving literal search commands.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced, but the batch 'Fix All Mismatches' step lacks an explicit re-verification checkpoint after corrections, so the validation gap caps this per the batch-operation rule.

3 / 5

Progressive Disclosure

A single self-contained file with well-organized sections (Required Input, Key Paths, Steps 1–6) and no nested references; structure is good with only minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

71%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, distinct, and answers both what and when, but its trigger terms are somewhat jargon-heavy and miss common user phrasings like 'compiler messages' or 'error codes'.

Suggestions

Add natural trigger phrasing users would actually say, e.g. 'Use when verifying compiler messages or error codes in C# docs against Roslyn source'.

Make the 'when' clause more concrete by naming the triggering artifact (e.g. 'after consolidating compiler-messages articles') rather than the generic 'final validation and correction phase'.

Include synonyms such as 'compiler messages' and 'error codes' alongside 'diagnostic article' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain (consolidated C# diagnostic article, Roslyn) and several concrete actions — verifying messages against Roslyn source, checking See also links, and acting as a validation/correction phase — with only minor coverage gaps.

4 / 5

Completeness

Clearly states what it does (verifies the article against Roslyn, checks See also links) and gives a when ('Use as the final validation and correction phase'), though the trigger could be more specific.

4 / 5

Trigger Term Quality

Includes relevant terms like 'C# diagnostic', 'Roslyn', and 'See also links', but misses common natural variations a user might say such as 'compiler messages' or 'error codes', leaning technical.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche — consolidated C# diagnostic articles verified against Roslyn — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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/docs
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.