fleet-verdict

Produce and send structured verdict packets after local surgery.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-verdict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-verdict
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-verdict
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-verdict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation and distribution of a standardized verdict from each fleet node after completing a local operation, enabling deterministic consensus across the fleet.

Core Features & Use Cases

  • Structured verdict packet with a fixed schema to ensure consistency across all nodes.
  • Support for evidence, risks, dissent, and cross-node synthesis via the Chief Surgeon.
  • Enables fleet-wide decision-making with a stable protocol for local surgeries.

Quick Start

Trigger local surgery on the assigned task and publish the resulting verdict to the fleet.

Frequently Asked Questions about fleet-verdict

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

FAQPage Schema
How do I produce a structured consensus verdict for distributed fleet nodes?

To produce a structured consensus verdict for distributed fleet nodes, trigger local surgery and publish the resulting packet using the 3x3x3 protocol to enforce a fixed schema for deterministic cross-machine consolidation.

What is the 3x3x3 protocol for cross-node critique and synthesis?

The 3x3x3 protocol for cross-node critique and synthesis is a distributed fleet mechanism that standardizes how local surgeries generate verdict packets, ensuring deterministic consolidation across machines via a fixed schema.

How do I send a verdict packet after local surgery in a distributed system?

To send a verdict packet after local surgery in a distributed system, complete the assigned task and publish the structured output to the fleet, enforcing required fields like evidence, risks, and dissent for cross-node synthesis.

Does fleet consensus require a fixed verdict schema for cross-machine decision making?

Fleet consensus requires a fixed verdict schema for cross-machine decision making to ensure deterministic consolidation. This schema mandates fields for evidence, risks, dissent, and Chief Surgeon synthesis.

Can I include dissent and risks in a distributed fleet verdict packet?

You can include dissent and risks in a distributed fleet verdict packet. The fixed schema supports evidence, risks, dissent, and cross-node synthesis via the Chief Surgeon to enable comprehensive fleet-wide decisions.

When do I need to use a fixed verdict schema for local surgery operations?

You need a fixed verdict schema for local surgery operations when working in distributed fleet environments that require deterministic consensus, cross-node critique, and standardized decision-making across multiple machines.