Skill UI

Performs a systematic and structured investigation to determine the true source of bugs, errors, and unexpected system behavior, rather than merely treating symptoms. This method utilizes techniques like the Five Whys, hypothesis-driven testing, stack trace analysis, and gathering evidence (logs, git diffs) across multiple phases. It is ideal for complex, intermittent, or deeply rooted technical issues in software development.

This skill provides comprehensive tools to download, export, and deeply inspect existing Arize traces and spans. It is essential for understanding the full execution flow of complex LLM applications, debugging runtime errors, and performing root-cause analysis. Users can retrieve detailed data filtered by Trace ID, Span ID, or Session ID, enabling thorough analysis of conversational or multi-step agent behaviors.

This advanced workflow automates the process of analyzing the operational health of specific Azure resources. It ingests and analyzes raw logs, telemetry data, and performance metrics from diverse Azure services (e.g., VMs, Web Apps, Databases). The system performs comprehensive root cause analysis, classifies issues (Critical, High, Medium), and generates actionable, step-by-step remediation plans, significantly reducing manual troubleshooting time.

Creates structured bug reports for defects found during Oracle-to-PostgreSQL database migration, covering severity, root cause, reproduction steps, and remediation. Useful for documenting behavioral differences and validating fixes.

This skill provides advanced debugging capabilities for failing Power Automate cloud flows using the FlowStudio MCP server. Unlike the limited status codes from the standard Graph API, this tool gives agents deep, action-level inputs and outputs, allowing users to find the true root cause of failures. It is essential for diagnosing complex issues like expression failures, connector authentication errors, or internal run errors.

A structured methodology for coordinating multiple, simultaneous investigation threads to determine the root cause of complex system failures, performance regressions, or integration bugs. This skill decomposes a large problem into independent tracks (e.g., database, application code, infrastructure), assigns ownership, and manages structured sync points (Continue/Pivot/Converge) to converge on a solution faster than serial debugging. Essential for high-stakes production incident response.

A comprehensive methodology for pinpointing the root cause of complex bugs, regressions, or unexpected behavior in large codebases. Techniques include binary search debugging, Git bisect for tracking regressions across commits, strategic data/control flow logging, component isolation, and advanced breakpoint strategies (conditional breakpoints, watch expressions). Ideal for scenarios where the bug source is unclear or difficult to reproduce.

This skill provides a structured approach to debugging software issues by prioritizing root cause analysis over quick fixes. It guides users through four phases: investigation, pattern analysis, hypothesis verification, and implementation. Essential for resolving test failures, production bugs, and performance issues efficiently, preventing recurring problems and architectural debt.

This comprehensive guide addresses common and complex errors encountered when automating Apple Notes on macOS using JXA or osascript. It covers three major areas: TCC permission denials, AppleEvent communication failures, and iCloud synchronization issues. The document provides a detailed error reference table, root cause analysis, tested fixes, and diagnostic scripts to help developers successfully automate Notes tasks.

This guide provides a quick reference for diagnosing and fixing common errors encountered when using the Intercom API. It details specific HTTP status codes (e.g., 401, 404, 429), their root causes, and actionable solutions, including code snippets for secure API interaction and implementing backoff logic for rate limiting. Essential for developers troubleshooting integration failures.

This guide provides a quick reference for diagnosing and fixing the top common errors encountered in ClickHouse, including syntax errors, memory limit issues, write permission failures, and data type mismatches. It offers specific error codes, root causes, and actionable SQL solutions for smooth database operation and complex analytics.

A comprehensive guide to troubleshooting the most common Algolia API errors, including 400, 403, 404, and 429. This document details the root causes and provides step-by-step fixes for issues related to invalid API keys, rate limits, missing indexes, and data structure validation, ensuring reliable search functionality.