fleet-escalation

Name: fleet-escalation
Availability: InStock
Author: wolvesfield

Manage multi-level fleet escalations with four response levels and conflict resolution.

Updated Aug 27, 2026

Search Tags:#risk management #escalation #incident management #fleet management #agent conflict #operational protocol

Ready to run

npx skills add https://github.com/wolvesfield/CIPHER-MCP --skill fleet-escalation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fleet-escalation
Source: https://github.com/wolvesfield/CIPHER-MCP/tree/main/core/skills/fleet-escalation
Command: npx skills add https://github.com/wolvesfield/CIPHER-MCP --skill fleet-escalation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework for managing critical incidents, agent conflicts, and scope deviations, ensuring timely and appropriate responses to maintain operational integrity.

Core Features & Use Cases

Multi-level Escalation: Defines and manages four distinct escalation levels (IMMEDIATE, SAME-DAY, PLAN-LEVEL, PATTERN) with specific triggers and actions.
Conflict Resolution: Implements a priority-based system for resolving conflicts when multiple agents modify the same file.
Fleet Logging: Standardizes the logging of all escalation events for auditability.
Use Case: When a critical security vulnerability is detected (IMMEDIATE escalation), the skill halts all operations, notifies the user, and awaits explicit direction, preventing further risk.

Quick Start

Use the fleet-escalation skill to log an immediate escalation due to a critical CVE.

Frequently Asked Questions about fleet-escalation

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

FAQPage Schema

How do I manage critical incidents and agent conflicts in a fleet?▼

Fleet escalation manages critical incidents and agent conflicts by applying a multi-level response protocol with four distinct levels to ensure operational integrity and timely resolution.

What is the best way to resolve conflicts when multiple agents modify the same file?▼

Conflict resolution for agents modifying the same file is handled through a priority-based system that determines which agent takes precedence, preventing scope deviations and data corruption.

How does a multi-level escalation framework work for incident management?▼

A multi-level escalation framework defines four levels—IMMEDIATE, SAME-DAY, PLAN-LEVEL, and PATTERN—each with specific triggers and required actions to systematically address incidents of varying severity.

When do I need to trigger an IMMEDIATE escalation during fleet operations?▼

An IMMEDIATE escalation is triggered when critical vulnerabilities, such as a severe CVE, are detected, halting all operations, notifying the user, and awaiting explicit direction to prevent further risk.

Can I use this escalation protocol to log all operational events for auditing?▼

Yes, the fleet escalation framework standardizes the systematic logging of all escalation events, ensuring full auditability and traceability for critical incident management and conflict resolution.

What distinguishes PATTERN level escalation from PLAN-LEVEL in incident response?▼

PATTERN level escalation addresses recurring operational deviations over time, whereas PLAN-LEVEL manages significant scope deviations requiring adjustments to the overall operational plan and strategy.