CtrlK
BlogDocsLog inGet started
Tessl Logo

error-consolidation-search

Finds C# diagnostics related to a consolidation theme. Use after setup to review documented and catch-all candidates through explicit approval gates.

60

Quality

71%

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

Quality

Content

88%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 well-sequenced, highly actionable three-phase workflow with explicit human approval gates and concrete file paths. It is concise and well-structured, with only minor room to externalize example material.

DimensionReasoningScore

Conciseness

The body is efficient with concrete paths, numbered steps, and example tables; the only slightly padded section is the placeholder-substitution paragraph in Phase C, which is detailed but justified by the specific transformation rule.

4 / 5

Actionability

Guidance is fully executable: exact file paths, specific transformations ('CS0463' to '463'), ErrorCode.cs/CSharpResources.resx lookups, markdown templates, and an example table format cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

Three phases (A/B/C) are clearly sequenced with explicit approval gates ('Wait for the user before proceeding', 'Wait for explicit approval') and batch-handling rules, providing validation checkpoints for this batch operation.

5 / 5

Progressive Disclosure

A single self-contained file with well-organized sections (Required Inputs, Key Paths, Phase A/B/C) and no nested references; good structure, though at ~95 lines a couple of the longer reference-table examples could live in a bundle file.

4 / 5

Total

18

/

20

Passed

Description

53%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 names a specific niche and includes a use-when clause, but relies on workflow-internal jargon and a weak trigger ('Use after setup') rather than natural user phrases. It is adequate but not exemplary.

Suggestions

Replace 'Use after setup' with a concrete natural trigger, e.g. 'Use when the user wants to find C# compiler errors or warnings related to an existing consolidation theme.'

Add common synonyms users actually say, such as 'C# error codes', 'compiler messages', 'CS#### codes', alongside 'diagnostics'.

Clarify the boundary with the merge skill (e.g. 'Search only; merging happens in error-consolidation-merge-existing') to reduce overlap risk.

DimensionReasoningScore

Specificity

Names the C# diagnostics domain and a couple concrete actions ('Finds C# diagnostics', 'review documented and catch-all candidates', 'explicit approval gates'), but coverage is not comprehensive — no mention of the search/merge distinction or output format.

3 / 5

Completeness

Gives a clear 'what' (finds and reviews C# diagnostics) and a 'when' clause ('Use after setup'), but the trigger is weak and references another skill's setup rather than a natural user situation, so 'when' is only weakly implied.

3 / 5

Trigger Term Quality

Contains relevant terms ('C# diagnostics', 'consolidation theme', 'catch-all candidates') but leans on internal jargon and misses natural user phrasings like 'error codes', 'compiler errors', or 'CS####'.

3 / 5

Distinctiveness Conflict Risk

The 'C# diagnostics related to a consolidation theme' niche is mostly distinct with clear triggers, though minor overlap risk exists with the sibling error-consolidation-merge skill.

4 / 5

Total

13

/

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.