CtrlK
BlogDocsLog inGet started
Tessl Logo

error-consolidation-merge-existing

Merges standalone C# diagnostic articles into a consolidated article with redirects and TOC updates. Use after the user approves the source list.

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-merge-existing/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.

A tight, actionable batch procedure with concrete paths, commands, and templates and good external reference signaling. Its primary gap is the absence of explicit validation/verification checkpoints before the destructive source-deletion step, which caps workflow clarity.

Suggestions

Add an explicit validation checkpoint before Step 5 (Delete the Source): verify the redirect entry was created, the TOC entry was removed, and the destination content renders correctly, with a fix-and-retry loop if any check fails.

Show a short toc.yml and front-matter keyword YAML example so the f1_keywords/helpviewer_keywords and TOC displayName edits are unambiguous and copy-paste ready.

Include a per-source verification step (e.g., confirm the new H2 section and master-list entry exist in the destination) before moving to the next file in the batch.

DimensionReasoningScore

Conciseness

The body is lean procedural instruction with concrete paths and templates and no concept explanations Claude already knows; a few sentences (e.g., the placeholder-substitution guidance) could be tightened, keeping it just below a 5.

4 / 5

Actionability

Provides concrete file paths, a copy-paste PowerShell command with fill-in placeholders, and markdown templates; minor gaps (no toc.yml format example, no front-matter keyword YAML example) keep it from a 5.

4 / 5

Workflow Clarity

The five-step batch sequence is clear and well-ordered, but this is a destructive batch operation (source deletion, TOC/redirect changes) with no explicit validate→fix→retry checkpoint, so per the rubric cap it cannot exceed 3.

3 / 5

Progressive Disclosure

Well-organized into labeled sections with clearly signaled one-level-deep references to the redirect skill and its script (no bundle files exist to verify); it stops short of 5 because the body is a full inline procedure rather than an overview pointing to detailed materials.

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.

A focused, third-person description that concretely states its actions and an explicit usage condition with minimal conflict risk. Its main weakness is trigger-term coverage, which relies on technical jargon over the natural phrases a user might say.

DimensionReasoningScore

Specificity

Names the domain ("standalone C# diagnostic articles") and several concrete actions—merging into a consolidated article, redirects, and TOC updates—matching the anchor for several specific actions with minor coverage gaps.

4 / 5

Completeness

Clearly states what it does and includes an explicit "Use after the user approves the source list" trigger clause; the when is explicit but a process-stage condition rather than a natural user-intent phrase, so it stops short of a 5.

4 / 5

Trigger Term Quality

Relevant terms like "C# diagnostic articles", "redirects", and "TOC updates" are present, but natural synonyms users would say ("compiler errors/warnings", "CS codes", "compiler messages") are missing.

3 / 5

Distinctiveness Conflict Risk

Carves a clear, narrow niche (consolidating C# diagnostic articles with redirects and TOC updates) that is unlikely to trigger for unrelated skills, matching the clear-niche anchor.

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.