Download skills/aws-resource-health-diagnose/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does aws-resource-health-diagnose live?
The publisher keeps it at https://github.com/github/awesome-copilot.
Which agents can use aws-resource-health-diagnose?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.
name: aws-resource-health-diagnose
description: 'Analyze AWS resource health, diagnose issues from CloudWatch logs and metrics, and create a remediation plan for identified problems.'
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:
Long-term Improvements: Architectural changes for resilience, preventive monitoring, enable AWS Health Dashboard notifications via EventBridge.
Step 7: Report & User Confirmation
Present findings:
🏥 AWS Resource Health Assessment
📊 Resource Overview:
• Resource: [Name] ([Type])
• Status: [Healthy/Warning/Critical]
• Region: [Region] | Account: [Account ID]
🚨 Issues Identified:
• Critical: X | High: Y | Medium: Z | Low: N
🔍 Top Issues:
1. [Issue]: [Description] — Impact: [High/Medium/Low]
2. [Issue]: [Description] — Impact: [High/Medium/Low]
🛠️ Remediation: X immediate, Y short-term, Z long-term actions
❓ Proceed with detailed remediation plan? (y/n)
Then generate a full markdown report covering: health metrics, issues with root cause analysis, phased remediation steps with AWS CLI commands, CloudWatch alarm recommendations, and validation checklist.
Error Handling
Resource Not Found: Ask user to clarify name/region
Authentication Issues: Guide through aws configure
Insufficient Permissions: List required IAM actions (logs:*, cloudwatch:*, pi:*)
No Logs Available: Suggest enabling CloudWatch logging for the resource type
Query Timeouts: Use shorter time windows
Success Criteria
✅ Resource health accurately assessed across all key metrics
✅ All significant issues identified and classified by severity
✅ Root cause analysis completed for major problems
✅ Actionable remediation plan with AWS CLI commands
✅ CloudWatch monitoring recommendations included
✅ Implementation steps include validation and rollback procedures
How do I install aws-resource-health-diagnose?
Download skills/aws-resource-health-diagnose/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does aws-resource-health-diagnose live?
The publisher keeps it at https://github.com/github/awesome-copilot.
Which agents can use aws-resource-health-diagnose?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.