infrastructure-health

Run tiered health checks across cloud infrastructure components.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Number531/Legal-API --skill infrastructure-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infrastructure-health
Source: https://github.com/Number531/Legal-API/tree/main/.claude/skills/infrastructure-health
Command: npx skills add https://github.com/Number531/Legal-API --skill infrastructure-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, psql, jq, gcloud, npm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Tiered infrastructure health monitoring for Super Legal MCP platform, monitors GCE instances, PostgreSQL/pgvector, Anthropic API circuit breakers, 36 API clients, Gemini embedding service, memory trends, EPO OAuth tokens, Prometheus alerts, session hygiene, API key expiration, Docker image drift, and dependency vulnerabilities. Triggers on: "infrastructure health", "health check", "infra status", "system health", "check infrastructure", "run health checks", "/infrastructure-health", or any request to monitor Super Legal production/staging status. Designed for /loop scheduling, with Tier 1 (critical/5m), Tier 2 (important/15m), Tier 3 (periodic/daily), and --all full sweep.

Core Features & Use Cases

  • Tiered execution: supports Tier 1, Tier 2, Tier 3 cadences and loop scheduling for deterministic sweeps.
  • Multi-subskill health: references gce-instance.md, postgresql.md, anthropic-api.md, embedding-service.md, memory-trends.md, epo-oauth.md, docker-image-drift.md, dependency-vulnerabilities.md, admin-endpoints.md, and more for holistic visibility.
  • Endpoint-driven operation: /health like endpoints for quick checks and structured payloads to drive automated remediation decisions.

Quick Start

Invoke the infrastructure-health endpoint to run a full health sweep and receive tiered results.

Frequently Asked Questions about infrastructure-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate tiered infrastructure health checks for cloud components?

Automate tiered infrastructure health checks by executing critical, important, and periodic surveillance across cloud components. It runs deterministic sweeps on GCE instances, PostgreSQL, and API endpoints, returning structured health payloads for remediation decisions.

What is tiered health monitoring and when do I need it for production infrastructure?

Tiered health monitoring is a surveillance approach dividing checks into critical, important, and periodic cadences. You need it for production infrastructure to systematically track uptime across components like GCE instances and PostgreSQL without manual intervention.

How do I schedule recurring health checks for cloud infrastructure using a loop?

Schedule recurring health checks for cloud infrastructure by integrating the monitoring flow with loop scheduling. It supports deterministic execution cadences, running Tier 1 checks every 5 minutes and Tier 3 checks daily for continuous visibility.

Does this infrastructure health monitoring approach work with PostgreSQL and gcloud environments?

This infrastructure health monitoring works directly with PostgreSQL and gcloud environments, alongside dependencies like curl, psql, and jq. It reads from reference scripts to execute checks across your cloud components and returns standardized health data.

Can I run a full infrastructure health sweep across all system endpoints at once?

You can run a full infrastructure health sweep across all system endpoints at once by triggering a complete check. This executes all tiered health checks holistically, covering API circuit breakers, memory trends, Docker image drift, and dependency vulnerabilities.

What are the limitations of using deterministic execution for SRE health monitoring?

The limitation of using deterministic execution for SRE health monitoring is that it relies on fixed tiered cadences and predefined scripts. It does not dynamically adapt check frequencies based on real-time traffic anomalies or sudden latency spikes outside the schedule.