Efficiently diagnose and fix local and cluster-based service issues.
Install
mkdir -p .claude/skills/ops-c9r-io && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13467" && unzip -o skill.zip -d .claude/skills/ops-c9r-io && rm skill.zipInstalls to .claude/skills/ops-c9r-io
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run tests, check logs, and troubleshoot services in Docker Compose and Kubernetes environments. Use when debugging local dev env issues, inspecting container/pod logs, restarting services, checking health, or triaging deployment rollouts.Key capabilities
- →Identify failure location as local or cluster
- →Collect service status, logs, and health endpoint data
- →Restart a single service in Docker Compose or Kubernetes
- →Reset a Docker Compose environment
- →Debug Kubernetes rollout status and events
- →Access shell within Docker containers or Kubernetes pods
How it works
The skill provides commands to inspect and manage services in Docker Compose and Kubernetes environments, facilitating troubleshooting.
Inputs & outputs
When to use ops
- →Debugging Docker services
- →Inspecting Kubernetes pod logs
- →Checking service health
- →Triaging deployment failures
About this skill
Operations
Discover the runtime contract before acting. In this repository the default operational surface is a host-running orchestratord daemon, not Docker Compose or Kubernetes.
Agent Orchestrator Triage
-
Inspect repository and daemon state:
git status --short orchestrator daemon status orchestrator debug --component daemon -
Inspect task state and bounded logs:
orchestrator task list orchestrator task logs <task-id> -n 200 -
The default runtime root is
~/.orchestratord/; respectORCHESTRATORD_DATA_DIRwhen it is set. Prefer CLI queries over reading SQLite or killing a PID directly. -
For source failures, run the narrowest relevant test first, then broaden to
cargo test --workspace. -
For Web UI failures, use scripts from
gui/package.json, normallynpm testornpm run test:e2efromgui/. -
Use
orchestrator daemon stopfor a graceful stop. Restart only when the user asked for a state-changing operational action.
Optional Container or Cluster Branch
Use Docker Compose only when a compose file exists in the target repository. Use Kubernetes only when a manifest or kustomization tree exists and the user has placed that cluster in scope. When neither exists, mark those checks not applicable instead of substituting assets from project-bootstrap.
For an applicable generated project, the conventional files are docker/docker-compose.yml, scripts/reset-docker.sh, and k8s/base/. Confirm each exact path before running it.
Evidence and Guardrails
- Collect status, the smallest relevant log tail, and a health or CLI check.
- Never delete the daemon database or runtime directory during routine triage.
- Never send an unscoped signal from a stale PID file.
- Do not restart every service when one bounded component is failing.
- Report the failing command, exit code, and relevant evidence rather than claiming recovery from process existence alone.
When not to use it
- →The user needs to run project-specific tests not covered by common examples
- →The user needs to troubleshoot systems not based on Docker Compose or Kubernetes
Limitations
- →It assumes `docker-compose.yml` is at `docker/docker-compose.yml` for Docker Compose
- →It assumes Kubernetes configurations are under `k8s/base/` and deploy scripts under `deploy/`
- →It relies on `kubectl` and `docker compose` commands
How it compares
This workflow centralizes common operational commands for Docker and Kubernetes, simplifying debugging compared to manually looking up commands.
Compared to similar skills
ops side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| ops (this skill) | 0 | 5mo | Review | Intermediate |
| mlops-engineer | 3 | 4mo | No flags | Advanced |
| senior-devops | 7 | 7mo | Review | Advanced |
| server-management | 1 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
mlops-engineer
sickn33
Build comprehensive ML pipelines, experiment tracking, and model registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated training, deployment, and monitoring across cloud platforms. Use PROACTIVELY for ML infrastructure, experiment management, or pipeline automation.
senior-devops
davila7
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.
server-management
davila7
Server management principles and decision-making. Process management, monitoring strategy, and scaling decisions. Teaches thinking, not commands.
debug-cluster
openshift
Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting control plane issues.
domain-cloud-native
actionbook
Use when building cloud-native apps. Keywords: kubernetes, k8s, docker, container, grpc, tonic, microservice, service mesh, observability, tracing, metrics, health check, cloud, deployment, 云原生, 微服务, 容器
mimir
grafana
>