fleet-audit-patterns

Detect duplicate or low-value agents via toolkit overlap, orphan status, and superset/subset relationships.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill fleet-audit-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-audit-patterns
Source: https://github.com/droxey/skills/tree/main/fleet-audit-patterns
Command: npx skills add https://github.com/droxey/skills --skill fleet-audit-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fleet audit patterns identify redundant or low-value agents and help teams rationalize agent toolkits, responsibilities, and configurations so resources are used effectively.

Core Features & Use Cases

  • Toolkit overlap detection: Flags when multiple agents share the same core toolkits for merge review, while requiring domain/description cross-checks to avoid false positives.
  • Orphan and stale agent identification: Surfaces agents that are disabled, have no goals, or have vague/outdated goals so they can be retired or corrected.
  • Superset/subset consolidation guidance: Detects strict toolkit superset/subset relationships to recommend merging smaller agents into more capable ones.

Quick Start

Use the fleet-audit-patterns skill to review your fleet and produce recommended actions for merging, retiring, or correcting agents based on toolkit overlap, orphan status, and superset/subset relationships.

Frequently Asked Questions about fleet-audit-patterns

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

FAQPage Schema
What is orphan detection and how does it identify stale agents?

Orphan detection identifies disabled agents, agents with no goals, or agents with vague and outdated goals. The fleet audit surfaces these stale agents so you can retire them or correct their configurations to ensure resources are used effectively.

How do I identify which agents to merge or retire in my fleet?

The best way to consolidate overlapping agents is to detect strict superset and subset toolkit relationships. The fleet audit recommends merging smaller, less capable agents into more comprehensive ones while cross-checking descriptions to avoid false positives.

When should I not merge agents that share the same core toolkits?

Identify merge or retirement candidates by analyzing toolkit overlap, orphan status, and superset/subset relationships. The audit produces specific actionable recommendations for merging, retiring, or correcting agents based on these multi-agent deployment factors.

When should I not merge agents that share the same core toolkits?

You should not merge agents when their domain and agent descriptions indicate they serve distinct purposes, even if their toolkits overlap. The audit applies cross-check safeguards specifically to prevent inappropriate merges that would violate workflow governance.