ccb-self-recover

Automate CCB system recovery actions after agent failures and config reloads.

17|2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SeemSeam/agent-roles-spec --skill ccb-self-recover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccb-self-recover
Source: https://github.com/SeemSeam/agent-roles-spec/tree/main/roles/ccb-self/skills/ccb-self-recover
Command: npx skills add https://github.com/SeemSeam/agent-roles-spec --skill ccb-self-recover

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill is designed to address system-level failures and disruptions, ensuring that agents and their environments recover from issues like failures, configuration reloads, and more without causing further harm or disruption.

Core Features & Use Cases

  • System-Level Recovery: Manages recovery from complex scenarios such as CCB agent failures, config reload aftermaths, and API/provider failures.
  • Safety-First Approach: Enforces a series of gates and checks to ensure that no actions lead to data corruption or loss during recovery processes.
  • Diverse Actions Supported: Performs actions like clear operations, single-agent restarts, configuration validations, and more based on the diagnostic findings.
  • Use Case: In case of a provider/API failure, this Skill would gather evidence, perform a dry-run, and only materialize the configuration when validated and intended by the user.

Quick Start

Run 'ccb recover' to begin the recovery process.

Frequently Asked Questions about ccb-self-recover

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

FAQPage Schema
How do I recover from a CCB agent failure after a provider or API disruption?

To recover from a CCB agent failure, you run 'ccb recover' to automate diagnostic evidence gathering, validation, and safe reboots of specific agents without causing further disruption or data loss.

What happens to my configuration during system recovery after a config reload?

During system recovery after a config reload, the process enforces safety gates and configuration validations. It ensures changes are validated and intended before materializing them to prevent data corruption.

Can I restart a single agent without disrupting the entire CCB environment?

Yes, you can restart a single agent without disrupting the entire CCB environment. The recovery process supports targeted single-agent restarts within a monitored environment to safely isolate and resolve failures.

Does agent recovery require access to specific control-plane commands?

Yes, agent recovery requires access to CCB control-plane commands. These commands are essential for gathering diagnostic evidence, validating configurations, and executing safe reboots within the monitored environment.

What is the safest way to clear operations after an agent failure?

The safest way to clear operations after an agent failure is to use an automated recovery process that enforces safety gates. It performs dry-runs and validates configurations before materializing any changes to prevent data corruption.