Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Systematic Kubernetes troubleshooting and incident response.
Install K8s Troubleshooter
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooter --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/k8s-troubleshooter/skills .claude/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .claude/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skillsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooter --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/k8s-troubleshooter/skills .agents/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .agents/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooter --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/k8s-troubleshooter/skills .cursor/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .cursor/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ahmedasmar/devops-claude-skills.git --path k8s-troubleshooter/skills--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooter --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/k8s-troubleshooter/skills .gemini/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .gemini/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooterInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/k8s-troubleshooter/skills .github/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .github/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ahmedasmar/devops-claude-skills k8s-troubleshooter --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ahmedasmar/devops-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/k8s-troubleshooter/skills .opencode/skills/k8s-troubleshooter && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "k8s-troubleshooter" agent skill from https://github.com/ahmedasmar/devops-claude-skills/tree/main/k8s-troubleshooter/skills into .opencode/skills/k8s-troubleshooter/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "k8s-troubleshooter", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
k8s-troubleshooter- GitHub stars
- 203
- Token cost
- ~2.4k tokens
- SKILL.md length
- 719 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Systematic Kubernetes troubleshooting and incident response.
- Works in 6 steps: Gather Context → Initial Triage → Deep Dive Investigation → …
- The user mentions Kubernetes
- SKILL.md covers Core Troubleshooting Workflow, Incident Response, Quick Reference Commands and Diagnostic Scripts, plus 1 more section
- Runs Python scripts from its folder; calls kubectl, python3 and ssh
What it does
K8s Troubleshooter is an agent skill from ahmedasmar/devops-claude-skills. Systematic Kubernetes troubleshooting and incident response. Use this skill whenever the user mentions Kubernetes, K8s, kubectl, pods, containers, or clusters. Triggers include diagnosing CrashLoopBackOff, ImagePullBackOff, OOMKilled, or Pending pods, responding to production incidents, troubleshooting node NotReady or DiskPressure, debugging service connectivity or networking, investigating PVC or storage failures, analyzing performance degradation, checking cluster health, troubleshooting Helm releases, and…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/common_issues.md`, `references/helm_troubleshooting.md` and `references/incident_response.md`).
It sits in DevOps & Cloud, covering Container orchestration. It works with Kubernetes. The repository describes itself as: A Claude Code Skills Marketplace for DevOps workflows.
When your agent uses it
- The user mentions Kubernetes
- Include diagnosing CrashLoopBackOff
- ImagePullBackOff
- Responding to production incidents
Example prompts
- “/k8s-troubleshooter”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Gather Context
- Initial Triage
- Deep Dive Investigation
- Identify Root Cause
- Apply Remediation
- Verify & Monitor
What it can do on your machine
Read from SKILL.md and the folder at commit 1489c33. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
kubectlpython3ssh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use kubectl and ssh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
K8s Troubleshooter loads about 2.4k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 142 tokens; SKILL.md has 719 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 719 words (~2,427 tokens).
“Systematic approach to diagnosing and resolving Kubernetes issues in production environments.”
- name
- k8s-troubleshooter
Files
SKILL.md and 5 other files (scripts, references) in k8s-troubleshooter/skills of ahmedasmar/devops-claude-skills.
- SKILL.md
- references/common_issues.md
- references/helm_troubleshooting.md
- references/incident_response.md
- references/performance_troubleshooting.md
- scripts/check_namespace.py
Open the folder on GitHubat commit 1489c33
Compare with similar skills
K8s Troubleshooter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| K8s Troubleshooter this skillahmedasmar/devops-claude-skills | 203 | — | ~2.4k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere Multi-Tenant Managementkubesphere/kubesphere | 17k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Sim Helmsimstudioai/sim | 30k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Helm Chart ScaffoldingCybereason-Public/owLSM | 280 | 13 repos | ~381 | Automated safety check: Pass | GPL-2.0 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT |
Similar skills
KubeSphere Multi-Tenant Management
kubesphere/kubesphere
Creates and queries KubeSphere users, workspaces and projects and assigns built-in roles, defaulting to least privilege and never deleting anything.
Sim Helm
simstudioai/sim
Install, upgrade, and operate the Sim Helm chart on Kubernetes.
Helm Chart Scaffolding
Cybereason-Public/owLSM
Comprehensive guidance for creating, organizing, and managing Helm charts for packaging and deploying Kubernetes applications.
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
More from ahmedasmar/devops-claude-skills
CI CD
ahmedasmar/devops-claude-skills
CI/CD pipeline design, optimization, DevSecOps security scanning, and troubleshooting.
Iac Terraform
ahmedasmar/devops-claude-skills
Infrastructure as Code with Terraform and Terragrunt. An agent skill from ahmedasmar/devops-claude-skills.
Monitoring Observability
ahmedasmar/devops-claude-skills
Monitoring and observability strategy, implementation, and troubleshooting.
AWS Cost Optimization
ahmedasmar/devops-claude-skills
AWS cost optimization and FinOps workflows. An agent skill from ahmedasmar/devops-claude-skills.
Related
Works with
Categories
Questions about K8s Troubleshooter
What does K8s Troubleshooter do?
Systematic Kubernetes troubleshooting and incident response. K8s Troubleshooter is an agent skill from ahmedasmar/devops-claude-skills. Systematic Kubernetes troubleshooting and incident response.
When should I use K8s Troubleshooter?
K8s Troubleshooter fits situations like: the user mentions Kubernetes; include diagnosing CrashLoopBackOff; imagePullBackOff; responding to production incidents.
How do I install K8s Troubleshooter in Claude Code?
Run `npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a claude-code`. Or copy the skill folder (k8s-troubleshooter/skills in ahmedasmar/devops-claude-skills) into .claude/skills/k8s-troubleshooter in your project. Claude Code loads it when a task matches its description.
How do I install K8s Troubleshooter in Codex?
Run `npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a codex`. Or copy the skill folder (k8s-troubleshooter/skills in ahmedasmar/devops-claude-skills) into .agents/skills/k8s-troubleshooter in your project. Codex loads it when a task matches its description.
Can I use K8s Troubleshooter in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ahmedasmar/devops-claude-skills --skill k8s-troubleshooter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/k8s-troubleshooter, .gemini/skills/k8s-troubleshooter, .github/skills/k8s-troubleshooter and .opencode/skills/k8s-troubleshooter in your project.
What does K8s Troubleshooter need to run?
Going by SKILL.md and its folder, K8s Troubleshooter needs Python for the scripts in its folder and the command-line tools its instructions call (kubectl, python3 and ssh). Our summary lists: Python 3.
Does K8s Troubleshooter access the network?
SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is K8s Troubleshooter safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does K8s Troubleshooter use?
No licence was found for K8s Troubleshooter or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does K8s Troubleshooter use?
About 2.4k tokens (SKILL.md is roughly 9.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15k tokens, read only when the agent opens those files.
What are the alternatives to K8s Troubleshooter?
Skills that share tags, products or a category with K8s Troubleshooter: Kubeshark Installer (kubeshark/kubeshark, 12k stars), KubeSphere Multi-Tenant Management (kubesphere/kubesphere, 17k stars), Sim Helm (simstudioai/sim, 30k stars) and Helm Chart Scaffolding (Cybereason-Public/owLSM, 280 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains K8s Troubleshooter?
ahmedasmar (a GitHub user) maintains it in ahmedasmar/devops-claude-skills, which has 203 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on April 11, 2026.
Source: ahmedasmar/devops-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.