LogoClawIndex
CasesSkillsAbout
LogoClawIndex

ClawIndex

OpenClaw Skills & Use Case Index

ClawIndex is an ecosystem-driven index of OpenClaw skills and real-world use cases.

Index

Skills·
Cases

Meta

About·
Disclaimer·
Email·
GitHub
© 2026 ClawIndex All Rights Reserved.

Skills with output: root cause identification

Browse skills that produce this output.

  • systematic-debugging - Systematic Debugging Methodology
    debuggingroot-cause-analysissystematichypothesis-testing

    ★ 2 · Updated 2026-06-30

    Four-phase methodology to identify root causes before proposing fixes for any technical issue

    ⚙ read error messages⚙ reproduce issues⚙ check recent changes
  • systematic-debugging - Debug Environment and Infrastructure Issues
    debuggingengineeringroot-causeinfrastructure

    ★ 3 · Updated 2026-06-30

    Four-phase debugging process requiring root cause identification before fixing environment, config, or infrastructure issues.

    ⚙ read error messages⚙ reproduce issue consistently⚙ check recent changes
  • systematic-debugging - Systematic debugging for technical issues
    debuggingtroubleshootingerror-analysisroot-cause

    ★ 1 · Updated 2026-06-15

    Find root cause before attempting fixes for bugs and failures

    ⚙ read error messages⚙ reproduce bug consistently⚙ check recent changes
  • systematic-debugging - Systematic Root Cause Debugging
    debuggingroot causebug fixingsystematic

    ★ 7 · Updated 2026-06-15

    Follow four-phase process to investigate root causes before fixing bugs and test failures

    ⚙ read error messages⚙ reproduce issues consistently⚙ check recent changes
  • systematic-debugging - Systematic Debugging for Technical Issues
    debuggingtroubleshootingroot cause analysissoftware development

    ★ 20 · Updated 2026-06-15

    Apply four-phase debugging process to find root causes before attempting fixes

    ⚙ read error messages⚙ reproduce issues⚙ check recent changes
  • systematic-debugging - Systematic Root Cause Debugging Process
    debuggingroot cause analysiserror handlingtesting

    ★ 69 · Updated 2026-06-15

    Four-phase debugging methodology to find root cause before fixing bugs, test failures, or unexpected behavior

    ⚙ read error messages⚙ reproduce issues⚙ check recent changes
  • systematic-debugging - Systematic debugging for root causes
    debuggingroot cause analysisproblem solvingdevelopment

    ★ 650 · Updated 2026-06-15

    Apply four-phase debugging process to identify root causes before fixing bugs

    ⚙ read error messages⚙ reproduce errors consistently⚙ check recent changes
  • detect-anomalies-aiops - AI-Powered Anomaly Detection for Operations
    aiopsanomaly detectiontime seriesmachine learning

    ★ 34 · Updated 2026-05-28

    Detect anomalies in operational metrics using machine learning and time series analysis

    ⚙ load time series metrics⚙ detect anomalies⚙ forecast metrics
  • coderabbit-incident-runbook - CodeRabbit Incident Response Runbook
    saasincident-responserunbook

    ★ 2,781 · Updated 2026-05-09

    Execute CodeRabbit incident response procedures for review failures and blocked PRs

    ⚙ check service status⚙ diagnose installation⚙ remove required checks
  • systematic-debugging - Systematic Technical Debugging Method
    debuggingtroubleshootingroot cause analysistesting

    ★ 0 · Updated 2026-05-09

    Debug technical issues by identifying root causes before applying fixes

    ⚙ reproduce bug⚙ isolate issue⚙ trace execution
  • analyze-traces - Analyze OpenTelemetry traces for debugging
    tracinglogsopentelemetryperformance

    ★ 8 · Updated 2026-05-09

    Read and reason about OpenTelemetry traces to debug errors, investigate latency, and audit attribute hygiene

    ⚙ read trace data⚙ filter trace data⚙ inspect span attributes
  • analyze - Deep Analysis for Code, Architecture, and Issues
    analysisdebugginginvestigationcode-review

    ★ 2 · Updated 2026-02-13

    Conducts thorough analysis of code, architecture, issues, bugs, performance bottlenecks, and security concerns

    ⚙ read relevant files⚙ check git history⚙ review issues and PRs