Name: devops-troubleshooter
Rating: 39.2 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

devops-troubleshooter

Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability.

Quality

38%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/devops-troubleshooter/SKILL.md

The canonical home for this skill is devops-troubleshooter in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

31%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 skill body is a padded capability catalog with no executable commands, code, or concrete debugging procedures, and its single external reference is both buried and broken. It tells Claude what the role covers but not how to actually do the work.

Suggestions

Replace the tool-name enumerations with a small set of concrete, copy-paste-ready debugging commands and snippets (e.g., kubectl debug, log correlation queries, trace-analysis steps).

Move the capability catalog into a reference file and keep SKILL.md as a concise overview with a clearly signaled, valid link.

Add explicit validation/verification checkpoints to the Response Approach (e.g., "confirm fix restored service and add an alert before closing") to lift workflow clarity above the cap.

Dimension	Reasoning	Score
Conciseness	The body is a ~150-line catalog enumerating tool names Claude already knows ("ELK Stack (Elasticsearch, Logstash, Kibana), Loki/Grafana, Fluentd/Fluent Bit"), which is noticeably verbose and padded with redundant capability listings rather than actionable knowledge.	2 / 5
Actionability	No concrete code, commands, or executable steps appear anywhere; the body only describes capability categories ("kubectl mastery: Advanced debugging commands") and offers high-level Response Approach hints, matching the score-2 anchor of minimal concrete guidance missing the specific steps to execute.	2 / 5
Workflow Clarity	The 9-step Response Approach provides a rough sequence, but there are no validation checkpoints for incident-response work that includes production changes, so per the feedback-loop cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Although section headers exist, the large tool/knowledge catalog that belongs in separate reference files is inlined, and the one reference ("resources/implementation-playbook.md") is buried in the Instructions section and points to a non-existent file and directory, matching the score-2 anchor of minimal structure with inlined content and buried references.	2 / 5
	Total	9 / 20 Passed

Description

45%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 clear domain and third-person voice is used correctly, but it lacks concrete actions, any "Use when" trigger guidance, and the natural phrases users say during incidents. It reads as a role summary rather than a trigger-rich skill description.

Suggestions

Add an explicit "Use when..." clause with concrete user trigger phrases (e.g., "Use when the user reports a production outage, pod crash-looping, 5xx errors, or asks for root-cause analysis").

Replace adjectival specializations with concrete actions the skill performs (e.g., "analyzes logs and traces, isolates root cause, runs kubectl debugging commands").

Include natural synonyms and signal terms users actually say (outage, latency, deployment failure, alert fatigue) to improve trigger matching.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Expert DevOps troubleshooter") and focus areas ("rapid incident response, advanced debugging, and modern observability") but lists no concrete actions, only adjectival specializations, matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	A clear "what" is present (expert DevOps troubleshooter specializing in...) but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes several relevant keywords a user might say (DevOps, incident response, debugging, observability), but misses common natural phrasings users actually emit ("production is down", "outage", "pod crash-looping", "5xx errors"), fitting the score-3 anchor of some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"DevOps troubleshooter" is a recognizable niche but broad enough to overlap with general coding, SRE, and platform-engineering skills, matching the score-3 anchor of somewhat specific but with overlap risk.	3 / 5
	Total	11 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/devops-troubleshooter/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.