dark-fleet-analysis

Enumerate agent registry entries and map routing reachability across Mortar and INTENT_RULES.

Updated Mar 12, 2026

Search Tags:#routing #audit #telemetry #semantic-routing #agent-registry #dark-fleet

Ready to run

npx skills add https://github.com/Nerfherder16/BrickLayer --skill dark-fleet-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dark-fleet-analysis
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/dark-fleet-analysis
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill dark-fleet-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dark fleet exposure: identify agent registry entries that exist but are not routable through current routing, and quantify coverage gaps to improve routing efficiency and reliability.

Core Features & Use Cases

Locate the agent registry and enumerate registered agents with their routing status.
Build a reachability map across Mortar/INTENT_RULES targets and semantic routing layers.
Produce fleet statistics that reveal auto-routable, dark fleet, and semantically reachable subsets.
Identify high-value dark agents and provide actionable routing recommendations.

Quick Start

Run a lightweight analysis of your agent registry to surface routing gaps and recommended actions.

Frequently Asked Questions about dark-fleet-analysis

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

FAQPage Schema

What is dark fleet routing and how does it affect agent registry coverage?▼

A dark fleet analysis identifies registered agents that lack auto-routing paths in current definitions, quantifies coverage gaps, and generates routing recommendations to expose dark fleet entries and improve reachability.

How do I find unlinked or unreachable agents in my agent registry?▼

Run a reachability analysis across Mortar, INTENT_RULES, and explicit references to enumerate registered agents, categorize them by routing status, and flag stub or placeholder entries that lack valid routing paths.

Can I audit semantic routing gaps across Mortar and INTENT_RULES targets?▼

Yes, you can audit semantic routing gaps by cross-referencing Mortar and INTENT_RULES targets against the agent registry to isolate semantically reachable agents from dark fleet entries lacking valid routing paths.

How do I generate routing recommendations for high-value dark agents?▼

Analyze fleet statistics to isolate high-value dark agents and generate actionable routing recommendations by mapping their semantic reachability against existing Mortar and INTENT_RULES routing definitions.

Does this dark fleet analysis require external dependencies or components?▼

No, this analysis requires no external dependencies or components. It performs a standalone audit of your agent registry and routing definitions to expose dark fleet entries and generate actionable recommendations.

What is the best way to expose stub or placeholder entries in a semantic routing fleet?▼

The best way to expose stub or placeholder entries is to enumerate the agent registry and cross-reference routing status against Mortar and INTENT_RULES. This flags non-functional entries that inflate fleet size without adding reachability.