Skip to content
TrustedSkillsbeta
Back to all skills

K8S Debug

Checked
incidentfox·vlatest·cloud

Troubleshoot Kubernetes incidents quickly; incidentfox-k8s-debug analyzes logs & metrics to pinpoint root causes in your cluster.

Repository

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 incidentfox/incidentfox --skill k8s-debug -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

incidentfox

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 incidentfox/incidentfox at 1b6ffad455.

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

Commit
1b6ffad455
Manifest
local/claude_code_pack/skills/k8s-debug/SKILL.md
Scanned
1 file, 127 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 incidentfox-k8s-debug skill assists in debugging Kubernetes (K8s) clusters. It analyzes logs, events, and resource configurations to identify the root cause of issues. This allows for faster incident resolution and improved cluster stability by providing actionable insights.

When to use it

  • Troubleshooting application failures: When an application deployed on a K8s cluster is experiencing errors or unexpected behavior.
  • Investigating performance bottlenecks: To identify resource constraints or inefficient configurations impacting application responsiveness.
  • Diagnosing deployment issues: During failed deployments, this skill can help pinpoint misconfigurations in manifests or environment problems.
  • Analyzing Kubernetes events: When reviewing unusual cluster activity or error messages from K8s components.

Key capabilities

  • Log analysis
  • Event analysis
  • Resource configuration inspection
  • Root cause identification

Example prompts

  • "Analyze the logs for pod 'my-app' and tell me why it keeps crashing."
  • "Show me recent events related to deployment 'my-deployment'."
  • “What is the current resource allocation for namespace ‘production’?”

Tips & gotchas

The skill requires access to your Kubernetes cluster. Ensure appropriate permissions are configured for the AI agent to read logs, events, and resource configurations.