error-detective

Analyze logs, traces, and metrics to diagnose error patterns across distributed systems.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KojiroSasa/www.havoc-it.ro --skill error-detective-kojirosasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-detective
Source: https://github.com/KojiroSasa/www.havoc-it.ro/tree/main/.agent/skills/qaagent--error-detective
Command: npx skills add https://github.com/KojiroSasa/www.havoc-it.ro --skill error-detective-kojirosasa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Complex distributed-system errors and cascading failures often go unseen until they impact users; this skill analyzes error patterns, correlates logs and metrics, and reveals root causes to prevent outages.

Core Features & Use Cases

  • Error pattern analysis across services and time to surface hidden correlations
  • Cross-service log and trace correlation to map cascading failures
  • Root-cause discovery and proactive prevention through monitoring and change detection

Quick Start

Analyze the current error landscape by providing logs, traces, and recent deployments for the implicated services.

Frequently Asked Questions about error-detective

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

FAQPage Schema
How do I find the root cause of cascading failures in distributed systems?

To find the root cause of cascading failures in distributed systems, you analyze error patterns by correlating logs, traces, metrics, and recent deployments across services to map cascade effects.

What is distributed system log and trace correlation for error detection?

Distributed system log and trace correlation for error detection is the process of mapping data across multi-service architectures to identify complex error patterns and reveal hidden correlations.

Can I diagnose multi-service architecture errors using logs and metrics?

Yes, you can diagnose multi-service architecture errors by providing logs, traces, metrics, and recent changes to map correlations and identify the root causes of complex system failures.

What's the best way to prevent outages from complex error patterns?

The best way to prevent outages from complex error patterns is to perform root-cause discovery and proactive monitoring improvements by analyzing recent deployments and correlating service metrics.

How do I analyze recent deployments to prevent unseen distributed system errors?

To analyze recent deployments and prevent unseen distributed system errors, you map correlations between recent changes and current error patterns across services to proactively improve monitoring.

What data do I need to map correlations and cascade effects across services?

To map correlations and cascade effects across services, you need to provide logs, traces, metrics, and recent deployment data for the implicated services in your multi-service architecture.