Agent skill · data analytics · github
aws-resource-health-diagnose
Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.
Why this skill is useful
Adds specific AWS CLI commands and diagnostic workflows for analyzing resource health that the AI wouldn't reliably generate on its own.
What it needs
Requires aws-cli installed locally. Requires aws account access. About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
AWS Resource Health & Issue Diagnosis This workflow analyzes a specific AWS resource to assess its health status, diagnose potential issues using CloudWatch logs and metrics, and develop a comprehensive remediation plan for any problems discovered. Prerequisites AWS CLI configured and authenticated Target AWS resource identified (name, type, and optionally region/account) CloudWatch logging and metrics enabled on the target resource Workflow Steps Step 1: Get AWS Diagnostic Best Practices Fetch https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ for monitoring and troubleshooting guidance to inform the diagnostic approach. Step 2: Resource Discovery & Identification Locate the target resource using the appropriate AWS CLI command for its type: If multiple matches are found, prompt the user to specify region/account. Step 3: Health Status Assessment Run service-specific health checks: Key health indicators by service type: Lambda: Error rate, throttle rate, duration P99, concurrent executions RDS: CPU utilization, FreeStorageSpace, DatabaseConnections, ReadLatency/WriteLatency ECS: Running vs desired task count, task stop reason ALB: TargetResponseTime, HTTPCodeELB5XXCount, UnHealthyHostCount SQS: ApproximateNumberOfMessagesNotVisible, ApproximateAgeOfOldestMessage DynamoDB: ConsumedReadCapacityUnits, ThrottledRequests, SuccessfulRequestLatency Step 4: Log & Metrics Analysis Find log groups and run CloudWatch Logs Insights queries: Identify: recurring error patterns, correlation with deployments (CloudTrail), performance trends, dependency failures. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/aws-resource-health-diagnose