error-investigation

Diagnose AWS service errors by correlating Lambda responses and CloudWatch logs.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Awannaphasch2016/jousef-landing --skill error-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-investigation
Source: https://github.com/Awannaphasch2016/jousef-landing/tree/main/.claude/skills/error-investigation
Command: npx skills add https://github.com/Awannaphasch2016/jousef-landing --skill error-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers quickly diagnose AWS error scenarios by correlating Lambda responses, payload results, and CloudWatch logs to identify root causes across services.

Core Features & Use Cases

  • Multi-layer verification (Status, Payload, Logs) to confirm failures.
  • AWS service coverage: Lambda, DynamoDB, S3, Step Functions, and CloudWatch Logs.
  • Production incident drill-down with diagnostic patterns and logging best practices.

Quick Start

Invoke a failing Lambda with a test payload, then review the response payload and CloudWatch logs for ERROR patterns. See AWS-DIAGNOSTICS.md for service-specific checks.

Frequently Asked Questions about error-investigation

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

FAQPage Schema
How do I diagnose AWS Lambda failures using CloudWatch logs?

Diagnose AWS Lambda failures by invoking the function with a test payload, then reviewing the response payload and CloudWatch logs for ERROR patterns. A multi-layer verification workflow correlates status codes, payload results, and log anomalies to identify the root cause.

How do I troubleshoot DynamoDB data inconsistencies across AWS services?

Troubleshoot DynamoDB data inconsistencies by correlating Lambda responses and payload results with CloudWatch logs. A structured, multi-layer verification workflow confirms failures across services to pinpoint data anomalies in production environments.

Can I use this approach to diagnose S3 access problems in my production environment?

Yes, you can diagnose S3 access problems in production environments. The workflow identifies permission issues and access anomalies by collecting and correlating failure signals across the application and AWS service layers.

What AWS CLI tools do I need to set up before troubleshooting Step Functions errors?

You need the AWS CLI and CloudWatch Logs Insights configured to collect, correlate, and verify failure signals. These tools are required to query logs, invoke Lambda functions with test payloads, and drill down into Step Functions errors.

Why does my multi-layer verification workflow fail to find the root cause of AWS errors?

Multi-layer verification may fail if AWS CLI or CloudWatch Logs Insights configurations are incomplete. Ensure Lambda logging best practices are applied and that status, payload, and logs are properly correlated to verify failure signals across all service layers.