CtrlK
BlogDocsLog inGet started
Tessl Logo

error-consolidation-consolidate

Reorganizes a consolidated C# diagnostic article into approved resolution themes. Use after the article's diagnostic set is complete.

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-consolidate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a well-structured, actionable instruction-only skill with explicit templates, an approval checkpoint, and a verification checklist. The main gap is the absence of an explicit error-recovery loop tied to the Final Checks.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining known concepts, with only minor illustrative blocks (the proposal example) that could be trimmed, fitting the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Copy-paste-ready markdown templates for the master list, thematic H2, and proposal format give concrete executable guidance, with only small gaps such as the loose 'read two or three other files' instruction.

4 / 5

Workflow Clarity

A clear Phase A → approval gate → Phase B sequence plus a four-item Final Checks checklist provides strong sequencing and validation for a destructive/batch rewrite, but it lacks an explicit fix-and-retry loop if a check fails, capping it below 5.

4 / 5

Progressive Disclosure

The skill is self-contained with well-organized sections and only one-level references to existing repo `*-errors.md` example files; no bundle files exist, so structure is good but the ~100-line body keeps it just short of the lean 5 anchor.

4 / 5

Total

16

/

20

Passed

Description

66%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 third-person, specific to a clear niche, and supplies both a 'what' and a 'when' clause. It is held back by single-action coverage and technical-leaning trigger terms that lack common user phrasings.

Suggestions

Add a 'Use when...' clause anchored in user intent (e.g. 'Use when consolidating C# compiler errors or reorganizing compiler-message docs by resolution theme').

List one or two more concrete actions (e.g. 'groups error codes by shared fixes and removes absorbed sections') to lift specificity.

Include natural synonyms users might say, such as 'compiler errors' or 'error messages', alongside 'diagnostic article'.

DimensionReasoningScore

Specificity

Names the domain ('consolidated C# diagnostic article') and one concrete action ('Reorganizes... into approved resolution themes'), but does not list multiple specific actions, matching the '1-2 concrete actions' anchor rather than the comprehensive 5.

3 / 5

Completeness

Both 'what' (reorganize into resolution themes) and 'when' ('Use after the article's diagnostic set is complete') are explicit, but the trigger is a sequencing condition rather than a concrete user-intent phrase, so it stops short of the 5 anchor.

4 / 5

Trigger Term Quality

Relevant terms like 'C# diagnostic article' and 'resolution themes' are present but lean technical; common user-facing variations (e.g. 'compiler errors', 'error messages') are missing, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The narrow niche of consolidating C# compiler-message articles into thematic sections is highly specific with minimal overlap risk against other skills.

5 / 5

Total

15

/

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.