devops-troubleshooter

Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/devops-troubleshooter/SKILL.md

Quality

Content

20%

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 lengthy capability catalog that enumerates DevOps tools and domains Claude largely already knows, offering little executable guidance. It has a clear response sequence but lacks validation checkpoints and progressive disclosure.

Suggestions

Replace the tool/category enumeration with concrete, copy-paste-ready commands and code (e.g., actual kubectl debug commands, log-grep patterns, trace-analysis steps).

Trim the redundant capability and knowledge-base lists to respect the context window; keep only what Claude would not already infer.

Add validation checkpoints to the Response Approach (e.g., confirm the hypothesis with evidence before fixing, verify the fix restored service before closing) and split detailed reference material into separate files.

Dimension	Reasoning	Score
Conciseness	The body is a verbose enumeration of tool names and capability categories (ELK, Loki, DataDog, Jaeger, Istio, etc.) that largely restates DevOps domain knowledge Claude already has, matching the verbose/padded anchor; it is not a 2 because the padding is pervasive rather than occasional.	1 / 3
Actionability	It describes categories ("kubectl mastery: Advanced debugging commands, resource inspection") without any concrete executable commands, code, or specific procedures, matching the describes-rather-than-instructs anchor; it does not reach 2 because no executable guidance is provided.	1 / 3
Workflow Clarity	The "Response Approach" section gives a 9-step numbered sequence (assess, gather, hypothesize, fix, document, monitor, improve, share, postmortem), but it has no validation checkpoints or error-recovery feedback loops, capping it at 2.	2 / 3
Progressive Disclosure	The file has section organization but is a ~130-line monolithic inline wall of capability listings with no bundle files or references, and the simple-skill exception (under 50 lines) does not apply, so it does not reach 3.	2 / 3
	Total	6 / 12 Passed

Description

77%

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 and complete, clearly answering both what the skill does and when to use it with an explicit trigger clause. Its main weakness is trigger-term breadth and some overlap risk with general debugging skills.

Suggestions

Add common natural trigger terms users would actually say, e.g. "outages, 504s, OOMKills, pod crashes, slow queries, k8s/Kubernetes problems".

Narrow distinctiveness by leading with the DevOps/SRE framing so general code-debugging requests do not match this skill.

Dimension	Reasoning	Score
Specificity	"Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis" lists multiple specific concrete actions and domains, matching the anchor for listing several specific actions.	3 / 3
Completeness	It explicitly states both what it does (the capability list) and when to use it ("Use PROACTIVELY for debugging, incident response, or system troubleshooting"), satisfying the explicit-trigger requirement for a 3.	3 / 3
Trigger Term Quality	"debugging, incident response, or system troubleshooting" includes relevant natural terms but misses common variations users would say (e.g., outage, logs, tracing, k8s, 504, OOM), so it is not a 3.	2 / 3
Distinctiveness Conflict Risk	"DevOps troubleshooter" gives a clear SRE/DevOps niche, but "debugging" and "system troubleshooting" could overlap with general coding-debug skills, so it is not the fully-distinct 3.	2 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/devops-troubleshooter/SKILL.md
Commit: e63f7dd

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.