failure-analyzer

Identifies recurring failure patterns in agent runs and outputs improvement patches for PROJECT.md, CLAUDE.md rules, and SKILL.md files.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/munlucky/claude-settings --skill failure-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-analyzer
Source: https://github.com/munlucky/claude-settings/tree/main/.claude/skills/failure-analyzer
Command: npx skills add https://github.com/munlucky/claude-settings --skill failure-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Failure patterns in agent runs hinder project reliability; this skill identifies recurring failures and translates them into concrete improvements for context, skills, agents, and rules.

Core Features & Use Cases

  • Pattern detection across analysisContext.notes and session-logs to categorize failures.
  • Generates structured improvement patches targeting PROJECT.md, rules, and SKILL.md.
  • Provides an actionable feedback loop to reduce recurrence and improve system robustness.
  • Use Case (example): When an orchestration sequence repeatedly times out, propose changes to the prompts, rule guards, and agent sequencing to eliminate the failure pattern.

Quick Start

Review recent failures and run the failure-analyzer to produce a patch with concrete improvements.

Frequently Asked Questions about failure-analyzer

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

FAQPage Schema
How do I analyze agent session logs to identify recurring failure patterns?

Failure pattern detection analyzes session-logs and analysisContext notes to identify recurring issues, categorizing them to produce a structured failureReport for improving system reliability.

How do I generate actionable improvement patches from incident reports?

Incident report analysis generates patch-like systemImprovements mapping fixes to PROJECT.md, CLAUDE.md rules, and individual SKILL.md files, providing an actionable feedback loop suitable for automated application.

When should I run a failure analysis on my orchestration sequences?

Failure analysis runs when multiple agent failures occur or upon explicit request by the orchestrator, examining session-logs and projectMemory to propose changes that eliminate the failure pattern.

Does failure analysis require specific dependencies to process project memory and skill chains?

Failure analysis operates with zero dependencies, directly parsing projectMemory and skillChain data to map system improvements to PROJECT.md and CLAUDE.md rules without requiring external libraries.

What is the best way to translate recurring agent timeouts into concrete system improvements?

Failure pattern detection translates recurring agent timeouts into concrete improvements by proposing changes to prompts, rule guards, and agent sequencing, outputting a patch targeting context and skill fixes.