CtrlK
BlogDocsLog inGet started
Tessl Logo

troubleshooting-procedure

Call this when a user states an IT issue and requests troubleshooting help. It provides step-by-step procedure for diagnosing and resolving IT issues, including escalation with a ticket summary.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

The content is a tight, highly actionable troubleshooting procedure with a clear sequenced workflow and a well-organized single-file structure. The only minor gap is the absence of an explicit validation/retry loop, which holds workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or over-explanation of concepts Claude already knows; every step earns its place and assumes Claude's competence.

5 / 5

Actionability

Steps are concrete and executable for an instruction-only skill — it specifies exactly what to ask ('the goal, symptom/error message, affected application, or device'), lists specific diagnostic checks, and itemizes the ticket-summary fields, with a real support URL.

5 / 5

Workflow Clarity

A clear numbered sequence (clarify → diagnose → instruct → offer alternatives → escalate) with an explicit 'after 2–3 failed paths' escalation gate and a ticket-summary checklist, but it lacks a strict validate→fix→retry data-validation loop, which keeps it just below the top anchor.

4 / 5

Progressive Disclosure

A short, single-purpose skill under 50 lines, well organized into numbered sections with no need for external references; per the simple-skill note this qualifies for the top score.

5 / 5

Total

19

/

20

Passed

Description

67%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 clearly states both what the skill does and when to invoke it, with concrete actions and an explicit trigger clause. It is slightly held back by limited trigger-term variety and the breadth of 'IT issues' as a domain label.

Suggestions

Broaden trigger terms to include natural phrasings users say, such as 'not working', 'error message', 'broken', or 'can't sign in'.

Tighten the domain label beyond generic 'IT issues' to reduce overlap with other IT/admin skills.

Optionally enumerate the concrete diagnostic actions (e.g., connectivity, sign-in, service status) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions — 'step-by-step procedure for diagnosing and resolving IT issues, including escalation with a ticket summary' — but stops short of comprehensive coverage of specific diagnostic methods.

4 / 5

Completeness

Explicitly answers both 'what' (procedure for diagnosing, resolving, and escalating with a ticket summary) and 'when' ('Call this when a user states an IT issue and requests troubleshooting help'), with the 'when' slightly less detailed than the anchor-5 example.

4 / 5

Trigger Term Quality

Includes natural user phrases like 'IT issue' and 'troubleshooting help', but misses common variations users actually say (e.g., 'not working', 'error', 'broken', 'crash'), so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

The IT-troubleshooting framing is a mostly distinct niche with a clear trigger, though the broad term 'IT issues' carries minor overlap risk with other IT/admin support skills.

4 / 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
microsoft/agent-academy
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.