phoenix-loop

Generate validated recovery playbooks from recurring failure signatures.

3|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Dalomeve/bot-output --skill phoenix-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-loop
Source: https://github.com/Dalomeve/bot-output/tree/main/skills/phoenix-loop
Command: npx skills add https://github.com/Dalomeve/bot-output --skill phoenix-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams transform repeating failures into reusable, validated recovery knowledge, reducing downtime by converting blockers into documented playbooks.

Core Features & Use Cases

  • Normalize failure signatures to a canonical format for quick lookup.
  • Reuse existing recovery knowledge or build a new recovery playbook when none exists.
  • Promote robust playbooks to a standalone skill only after proven success and clear triggers.

Quick Start

Provide a failing scenario that recurs, and Phoenix Loop will generate a recovery playbook and, if ready, promote it to a new skill.

Frequently Asked Questions about phoenix-loop

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

FAQPage Schema
How do I turn recurring failures into a recovery playbook?

To turn recurring failures into a recovery playbook, provide a repeating failing scenario. The system checks for 2+ occurrences, consults existing memory, and generates deterministic recovery steps validated for reuse.

What is a recovery playbook and when do I need one for fault diagnosis?

A recovery playbook is reusable, validated knowledge that resolves repeating blockers. You need one during fault diagnosis when a failure signature persists without recovery or recurs multiple times, ensuring downtime is reduced.

How do I create a recovery playbook from a failed run?

To create a recovery playbook from a failed run, prompt the system to learn from the failure. It normalizes the failure signature, checks existing memory, and builds a new deterministic recovery repository if none exists.

When should recurring failures be promoted to a standalone skill?

Recurring failures should be promoted to a standalone skill only after the generated recovery playbook achieves proven success with clear triggers. This validation ensures the automated recovery knowledge is robust and reliable.

Can I use existing memory to diagnose recurring failures instead of building a new playbook?

Yes, you can use existing memory. The system consults existing memory or playbooks during fault diagnosis before building a new recovery playbook, ensuring previously validated recovery knowledge is reused for recurring failures.

Does this approach work for blockers that persist without recovery?

Yes, this approach works for blockers that persist without recovery. It normalizes the failure signature to a canonical format for quick lookup and generates a deterministic recovery playbook to resolve the stuck state.