ops-monitor

Monitor deployed infrastructure health using CloudWatch metrics across environments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill ops-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-monitor
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/faber-cloud/.archive/phase4-clean-separation/ops-monitor
Command: npx skills add https://github.com/fractary/claude-plugins --skill ops-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, aws-cli, jq, and includes references (resource) components.

What problem does it solve?

Manually tracking the health and performance of deployed infrastructure is complex and prone to oversight, leading to undetected issues. This skill automates monitoring, providing proactive insights and actionable recommendations.

Core Features & Use Cases

  • Health Checks: Automatically check the status of all deployed resources across environments.
  • Metrics Analysis: Query and analyze CloudWatch metrics for performance trends and anomalies.
  • Reporting & Recommendations: Generate detailed health reports with status summaries and optimization recommendations.
  • Use Case: Perform a health check on all services in the 'prod' environment, identify any degraded services, and get recommendations for performance optimization.

Quick Start

Perform a health-check on all services in the 'test' environment.

Frequently Asked Questions about ops-monitor

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

FAQPage Schema
How do I monitor infrastructure health across AWS environments?

Monitor infrastructure health by querying CloudWatch metrics and resource registries across test or prod environments. This skill automates status checks, analyzes performance trends, detects anomalies, and generates health reports with actionable recommendations for all deployed resources.

Can I automate health checks on all services in production?

Yes. Automate health checks across all services in your prod environment, identify degraded resources, and receive optimization recommendations. The skill applies across environments and optional service filters to detect issues proactively.

How do I detect performance anomalies in CloudWatch metrics?

Query and analyze CloudWatch metrics to identify performance anomalies and trends. The skill categorizes health status, exports structured outputs, and applies configurable timeframes to surface degradation patterns across your infrastructure.

What AWS tools do I need to set up infrastructure monitoring?

You need AWS CLI, CloudWatch access, Bash, and jq for querying and processing metrics. The skill loads configuration and resource registries, then queries CloudWatch to determine resource status and generate reports.

Can I monitor multiple environments with different service subsets?

Yes. Apply monitoring across environments (test or prod) with optional service and metric filters. Customize timeframes and scope to analyze specific resource subsets, then export structured health reports and recommendations.

What are the limitations of automated infrastructure monitoring?

Automated monitoring depends on CloudWatch data availability, AWS CLI access, and accurate resource registry configuration. Coverage is limited to queryable metrics; custom application-level anomalies require integration with additional monitoring layers.