OpenClaw Automation Healthcheck
Seleccionado

OpenClaw Automation Healthcheck

自动巡检基础设施健康状态并生成告警/日报

3 habilidades 1 instalaciones
openclawautomationhealthcheckdevops
Actualizado hace 3 dias

Instalar

Ejecuta este comando para instalar todas las habilidades en este complemento:

npx skillstore add @openclaw-automation-healthcheck

Las habilidades se instalarán en el directorio .claude/skills/

Descripcion general

Guia de uso

Mejorado por IA

Guia detallada

## Who Is This For

DevOps engineers and on-call responders who need to quickly assess infrastructure health, generate incident runbooks, and produce audit-ready reports — all from a chat interface without switching between monitoring tools.

## 3-Step Quickstart

1. **Run the health check** — ask: `"Use cloud-devops to check the health of my AWS ECS cluster and Kubernetes nodes"`. The skill covers AWS, Azure, GCP, and Kubernetes in one pass.
2. **Generate an infrastructure report** — ask: `"Use infrastructure-reporting to produce a full health report for network segment 10.0.1.0/24"`. You get performance analysis, health status, and actionable recommendations.
3. **Create a runbook** — ask: `"Use devops-runbooks to write an incident response runbook for: service X is down, alert fired at 14:32"`. The skill generates an operational procedure document.

## Step → Skill → Input → Output

| Step | Skill | What You Provide | What You Get |
|------|-------|------------------|--------------|
| Health check | cloud-devops | Cloud provider + resource names | Health status summary |
| Infrastructure report | infrastructure-reporting | Network range or host list | Full report with performance + recommendations |
| Runbook | devops-runbooks | Incident description + timeline | Structured response procedure |

## Common Failures & Fixes

- **cloud-devops returns "permission denied"** → Ensure the agent has read permissions for the target cloud resources. Add a read-only IAM role or API token.
- **infrastructure-reporting shows "no hosts found"** → Check that the network range is correct and the agent can reach the hosts (firewall rules).
- **devops-runbooks output is too generic** → Provide more context: service name, error message, and what you already tried. More input = more specific runbook.

## Success Criteria

You know it worked when:
- cloud-devops returns a color-coded health summary (green/yellow/red per resource)
- infrastructure-reporting generates a report with at least a performance section and a recommendations list
- devops-runbooks outputs a numbered procedure with clear remediation steps

Habilidades

3