failure-archaeology

Organize and retrieve historical failure data for root cause analysis.

24|8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/usecompai/compound-operations-model --skill failure-archaeology-usecompai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-archaeology
Source: https://github.com/usecompai/compound-operations-model/tree/main/skills/failure-archaeology
Command: npx skills add https://github.com/usecompai/compound-operations-model --skill failure-archaeology-usecompai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage and retrieve historical failure data to avoid repeating past mistakes and improve system reliability.

Core Features & Use Cases

  • Record Failures: Log incidents, postmortems, and dead ends with root causes and evidence.
  • Retrieve Failures: Quickly find previous failures and their resolutions to inform current debugging and analysis.
  • Use Case: When an error occurs that seems familiar, use this Skill to search for and review past occurrences to speed up troubleshooting.

Quick Start

Use the failure-archaeology skill to search for past incidents related to a specific error message, e.g., "search: 'token error'".

Frequently Asked Questions about failure-archaeology

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

FAQPage Schema
How do I search past incidents and postmortems during root cause analysis?

To perform root cause analysis, you search a structured knowledge base of historical failure data to retrieve past incidents, dead ends, and their documented resolutions to speed up current debugging.

What is the best way to record postmortems and incident tracking data for future retrieval?

Recording postmortems involves using a dedicated script to log new failures, capturing incident details, root causes, and evidence into a structured knowledge base for efficient future retrieval and failure management.

Can I retrieve historical failure data using a specific error message?

Yes, you can retrieve historical failure data by searching the knowledge base with familiar error messages, such as querying "token error", to quickly find previous occurrences and inform your current troubleshooting.

How does searching a failure knowledge base improve debugging and incident tracking?

Searching a failure knowledge base improves debugging by matching current errors against recorded historical failure data, allowing you to bypass previous dead ends and apply proven root cause analysis resolutions immediately.

Do I need a structured knowledge base to log new failures and dead ends?

Yes, logging new failures requires a structured knowledge base to efficiently organize incident tracking records, ensuring that postmortems, root causes, and evidence are properly stored for later retrieval.