fleet-inspector

Audit XOmnibus engines in parallel and generate a unified health report.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill fleet-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-inspector
Source: https://github.com/BertCalm/xo-ox-claude-config/tree/main/skills/fleet-inspector
Command: npx skills add https://github.com/BertCalm/xo-ox-claude-config --skill fleet-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, real-time health dashboard for the entire XOmnibus fleet of engines, identifying areas needing attention across source code, presets, documentation, and build status.

Core Features & Use Cases

  • Fleet-wide Audit: Scans all engines in parallel for a unified health report.
  • Detailed Health Metrics: Checks source code integrity, preset counts and mood distribution, documentation completeness, and doctrine compliance.
  • Gap Identification: Pinpoints specific areas of weakness, such as missing presets, incomplete documentation, or doctrine failures.
  • Prioritization: Recommends specific actions and engines for focus based on identified gaps.
  • Use Case: Before planning a development sprint, use the Fleet Inspector to get a clear overview of the fleet's status, identify the most critical engines needing work, and prioritize tasks accordingly.

Quick Start

Use the fleet inspector skill to get a full overview of the fleet's current health status.

Frequently Asked Questions about fleet-inspector

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

FAQPage Schema
How do I run a fleet-wide code audit and documentation check for all XOmnibus engines?

A fleet health dashboard provides a real-time overview of all XOmnibus engines, scanning source code integrity, preset health, documentation status, and doctrine compliance to pinpoint specific gaps and recommend maintenance priorities.

What's the best way to identify missing presets and doctrine compliance failures across a large engine fleet?

A comprehensive fleet audit identifies specific gaps like missing presets, incomplete documentation, and doctrine failures by analyzing each engine individually, then aggregates the results into a prioritized maintenance report.

Can I use parallel agents to scan a large XOmnibus fleet for source code and documentation status?

Yes, the Fleet Inspector utilizes parallel agents to efficiently scan large XOmnibus fleets, analyzing source code, preset health, documentation completeness, and doctrine compliance simultaneously to generate a unified report.

How does fleet management prioritization work when identifying gaps in engine documentation and source code?

Fleet management prioritization works by comparing identified gaps across all engines, such as missing presets or doctrine failures, and generating a prioritized list of recommended actions to guide development sprints and maintenance focus.

Does fleet health monitoring work without external dependencies for checking doctrine compliance?

Yes, the Fleet Inspector operates without external dependencies to conduct comprehensive health audits, checking doctrine compliance, source code integrity, and documentation completeness using only its internal parallel agents.

Why does the fleet health dashboard recommend focusing on specific engines for development sprints?

The fleet health dashboard recommends specific engines for development focus based on detected gaps in source code integrity, preset distribution, and documentation status, ensuring development sprints address the most critical fleet issues first.