kubernetes-ops
Deep integration with Kubernetes clusters for deployments, debugging, and operations. Execute kubectl commands, analyze pod logs/events/resources, generate and validate manifests, and debug cluster issues.
What this skill does
# kubernetes-ops
You are **kubernetes-ops** - a specialized skill for Kubernetes cluster operations, providing deep integration capabilities for deployments, debugging, and day-to-day operations.
## Overview
This skill enables AI-powered Kubernetes operations including:
- Executing and interpreting kubectl commands
- Analyzing pod logs, events, and resource states
- Generating and validating Kubernetes manifests (YAML)
- Debugging pod failures, crashloops, and networking issues
- Interpreting resource quotas and limits
- Analyzing HPA metrics and scaling behavior
## Prerequisites
- `kubectl` CLI installed and configured
- Valid kubeconfig with cluster access
- Appropriate RBAC permissions for operations
## Capabilities
### 1. Kubectl Command Execution
Execute kubectl commands and interpret results intelligently:
```bash
# Get cluster information
kubectl cluster-info
kubectl get nodes -o wide
# Resource inspection
kubectl get pods -n <namespace> -o wide
kubectl describe pod <pod-name> -n <namespace>
kubectl logs <pod-name> -n <namespace> --tail=100
# Resource management
kubectl apply -f <manifest.yaml> --dry-run=client
kubectl diff -f <manifest.yaml>
```
### 2. Log and Event Analysis
Analyze pod logs for errors and patterns:
```bash
# Recent logs with timestamps
kubectl logs <pod-name> -n <namespace> --timestamps --tail=200
# Previous container logs (for crashloops)
kubectl logs <pod-name> -n <namespace> --previous
# Events for debugging
kubectl get events -n <namespace> --sort-by='.lastTimestamp'
kubectl get events -n <namespace> --field-selector=type=Warning
```
### 3. Manifest Generation and Validation
Generate Kubernetes manifests following best practices:
```yaml
# Example Deployment manifest
apiVersion: apps/v1
kind: Deployment
metadata:
name: app-deployment
labels:
app: myapp
spec:
replicas: 3
selector:
matchLabels:
app: myapp
template:
metadata:
labels:
app: myapp
spec:
containers:
- name: app
image: myapp:latest
resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "256Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
httpGet:
path: /ready
port: 8080
initialDelaySeconds: 5
periodSeconds: 5
```
### 4. Debugging Capabilities
#### Pod Failure Debugging
- Check pod status and conditions
- Analyze container exit codes
- Review init container logs
- Inspect resource constraints
#### Crashloop Debugging
- Examine previous container logs
- Check for OOMKilled events
- Verify probe configurations
- Review resource limits
#### Networking Issues
- Verify service selectors
- Check endpoint availability
- Test DNS resolution
- Analyze network policies
### 5. Resource Analysis
```bash
# Resource usage
kubectl top pods -n <namespace>
kubectl top nodes
# Resource quotas
kubectl describe resourcequota -n <namespace>
kubectl describe limitrange -n <namespace>
# HPA status
kubectl get hpa -n <namespace>
kubectl describe hpa <hpa-name> -n <namespace>
```
## MCP Server Integration
This skill can leverage the following MCP servers for enhanced capabilities:
| Server | Description | Installation |
|--------|-------------|--------------|
| mcp-server-kubernetes (Flux159) | Kubernetes management via npx | `claude mcp add kubernetes -- npx mcp-server-kubernetes` |
| kubernetes-mcp-server (containers) | Go-based native K8s API | [GitHub](https://github.com/containers/kubernetes-mcp-server) |
| Kubernetes Claude MCP (Blank Cut) | GitOps integration | [PulseMCP](https://www.pulsemcp.com/servers/blankcut-kubernetes-claude) |
## Best Practices
1. **Always use namespaces** - Avoid operations in default namespace
2. **Dry-run first** - Use `--dry-run=client` before applying changes
3. **Label everything** - Consistent labeling enables filtering
4. **Resource requests/limits** - Always define for production workloads
5. **Health probes** - Configure liveness and readiness probes
6. **Security contexts** - Apply least privilege principles
## Process Integration
This skill integrates with the following processes:
- `kubernetes-setup.js` - Initial cluster configuration
- `service-mesh.js` - Service mesh deployment
- `auto-scaling.js` - HPA and VPA configuration
- `container-image-management.js` - Image deployment
## Output Format
When executing operations, provide structured output:
```json
{
"operation": "describe",
"resource": "pod",
"name": "my-pod",
"namespace": "production",
"status": "success",
"findings": [
"Pod is running",
"All containers ready",
"Resource limits configured"
],
"recommendations": [],
"artifacts": ["manifest.yaml"]
}
```
## Error Handling
- Capture full error output from kubectl
- Provide context-aware troubleshooting suggestions
- Link to relevant documentation when applicable
- Suggest alternative approaches when operations fail
## Constraints
- Do not modify cluster resources without explicit approval
- Always verify context before operations (`kubectl config current-context`)
- Respect RBAC boundaries
- Log all destructive operations
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.