skill-dependency-fan-out-inspector

Analyze SKILL.md references to detect dependency fan-out, cycles, and transitive reach.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/grtninja/skill-arbiter --skill skill-dependency-fan-out-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-dependency-fan-out-inspector
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/skill-dependency-fan-out-inspector
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill skill-dependency-fan-out-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Scans skill metadata to reveal hidden dependency costs, fan-out hotspots, and cycles that can escalate cross-skill invocation latency.

Core Features & Use Cases

  • Build a dependency graph from explicit references in SKILL.md
  • Detect fan-out hotspots, transitive reach risks, and cycles
  • Emit JSON and DOT graph artifacts for analysis and debugging

Quick Start

Run the dependency inspector against the skill-candidates root to generate a report and evidence assets.

Frequently Asked Questions about skill-dependency-fan-out-inspector

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

FAQPage Schema
How do I detect dependency cycles and fan-out hotspots in skill metadata?

You can detect dependency cycles and fan-out hotspots by scanning SKILL.md metadata to build a dependency graph, which surfaces cross-skill invocation costs and transitive reach risks in a structured report.

What is transitive reach in a dependency graph?

Transitive reach in a dependency graph measures the downstream skills affected by a single skill invocation, calculated by analyzing explicit references across the skill-candidates folder to map hidden dependency costs.

Can I visualize skill dependencies using DOT graph format?

Yes, you can visualize skill dependencies using DOT graph format. The analysis outputs JSON plus optional DOT graph artifacts for visualization, allowing you to map dependency relationships and debug invocation latency.

How do I find hidden dependency costs in SKILL.md files?

To find hidden dependency costs in SKILL.md files, analyze the explicit dollar-referenced dependencies within the metadata to calculate transitive graph metrics and reveal cross-skill invocation latency.

What are the limitations of dependency graph analysis for skill metadata?

A limitation of dependency graph analysis is that it enforces explicit dollar-referenced dependencies, meaning implicit or undeclared skill references may not be captured in the final fan-out and cycle report.