Skip to content
TrustedSkillsbeta
Back to all skills

Devops Troubleshooter

Checked
rmyndharis·vlatest·devops·MIT

Diagnoses and resolves common DevOps pipeline failures, identifying root causes and suggesting remediation steps quickly.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rmyndharis/antigravity-skills --skill devops-troubleshooter -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rmyndharis

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rmyndharis/antigravity-skills at 3eff4af253.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 161 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The DevOps Troubleshooter skill analyzes infrastructure and application logs to identify the root cause of operational issues. It can correlate events across multiple systems, providing a consolidated view of problems impacting deployments and services. This allows for faster diagnosis and resolution of incidents, minimizing downtime and improving overall system stability.

When to use it

  • Debugging Deployment Failures: Investigate why a recent deployment failed, identifying errors in configuration or code.
  • Performance Degradation: Analyze slow response times or increased latency across an application stack.
  • Incident Response: Quickly pinpoint the source of an ongoing outage affecting users.
  • Proactive Problem Identification: Scan logs for recurring patterns that may indicate underlying infrastructure issues.

Key capabilities

  • Log correlation across multiple systems
  • Root cause analysis of operational incidents
  • Infrastructure and application log parsing
  • Event timeline visualization
  • Consolidated incident view

Example prompts

  • "Analyze the last hour of logs from our web servers and database to find the cause of increased latency."
  • "Why did deployment version 1.2.3 fail on staging?"
  • "Show me a timeline of events leading up to the service outage at 10:00 AM PST."

Tips & gotchas

The skill requires access to relevant log files and system metrics. Ensure appropriate permissions are granted for accurate analysis and troubleshooting.