Files
OpenCode Test d9be8145f8 Refactor remaining skills with resources pattern and allowed-tools
- k8s-quick-status: Add scripts/quick-status.sh, allowed-tools
- sysadmin-health: Add scripts/health-check.sh, allowed-tools
- usage: Add scripts/usage_report.py, simplify SKILL.md
- programmer-add-project: Add allowed-tools

All skills now:
- Have executable scripts for main operations
- Use allowed-tools to restrict capabilities
- Have improved descriptions with trigger phrases
- Follow the "Skill with Bundled Resources" pattern

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-01 02:38:58 -08:00

62 lines
1.4 KiB
Markdown

---
name: k8s-quick-status
description: Quick cluster health pulse check. Use when asked about cluster status, k8s health, or kubernetes overview.
allowed-tools:
- Bash
- Read
---
# K8s Quick Status Skill
Performs a lightweight health pulse check on the Raspberry Pi Kubernetes cluster.
## Quick Command
```bash
~/.claude/skills/k8s-quick-status/scripts/quick-status.sh
```
Or run individual checks:
```bash
# Node status
kubectl get nodes -o wide
# Unhealthy pods
kubectl get pods -A --field-selector=status.phase!=Running,status.phase!=Succeeded
# Warning events
kubectl get events -A --field-selector=type=Warning --sort-by='.lastTimestamp' | tail -10
# ArgoCD apps
argocd app list
```
## Checks Performed
| Check | Command | What It Shows |
|-------|---------|---------------|
| Nodes | `kubectl get nodes` | Readiness, conditions |
| Pods | `kubectl get pods -A` | Unhealthy pods |
| Restarts | jsonpath query | Pods with >5 restarts |
| Events | `kubectl get events` | Recent warnings |
| ArgoCD | `argocd app list` | Sync status |
## Output Format
Report as structured summary:
- **Overall status**: healthy/warning/critical
- **Node summary**: table of nodes
- **Issues**: unhealthy pods, high restarts
- **ArgoCD**: sync status
- **Concerns**: immediate action items
## When to Use
- Quick pulse check: use this skill
- Comprehensive analysis: use `/cluster-status` command
## Autonomy
Read-only - runs without confirmation.