network-topology-review

Analyze software dependency graphs to identify hubs, bottlenecks, articulation points, cycles, and blast radius.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill network-topology-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: network-topology-review
Source: https://github.com/NlightNFotis/skills/tree/main/network-topology-review
Command: npx skills add https://github.com/NlightNFotis/skills --skill network-topology-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you analyze software systems as graphs so you can spot structural risk before it causes outages, slow delivery, or large change cascades. It is especially useful when a dependency network feels fragile, tightly coupled, or hard to reason about from local code inspection alone.

Core Features & Use Cases

  • Graph-Structured Diagnosis: Reviews systems through nodes, edges, direction, and centrality to identify hubs, bottlenecks, and risky dependency concentration.
  • Failure and Blast Radius Analysis: Finds articulation points, bridges, cycles, and strongly connected components to estimate how outages or breaking changes propagate.
  • Architecture and Refactoring Guidance: Recommends targeted structural changes for service graphs, module imports, event systems, IAM relationships, build dependencies, and ownership networks.
  • Use Case: When one shared library, gateway service, or platform component seems to affect many teams, this Skill helps determine whether it is a safe keystone or a dangerous single point of failure.

Quick Start

Ask the network-topology-review skill to analyze your module or service dependency graph and identify the highest-risk hubs, cycles, articulation points, and likely blast radius.

Frequently Asked Questions about network-topology-review

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

FAQPage Schema
How do I find single points of failure in a microservice dependency graph?

To find single points of failure in a microservice dependency graph, you identify articulation points, bridges, and strongly connected components. This structural analysis exposes risky hubs and estimates the blast radius if a specific service or shared library fails.

What is blast radius analysis in software architecture?

Blast radius analysis in software architecture measures how outages or breaking changes propagate across connected components. By mapping service call topologies and dependency cycles, it estimates the operational impact of a node failure within the network.

How do I detect bottlenecks and cycles in a module import graph?

To detect bottlenecks and cycles in a module import graph, you apply graph analysis to evaluate node centrality and strongly connected components. This structural review identifies tightly coupled modules and highlights where architectural refactoring is needed for decoupling.

Does graph analysis work for assessing IAM relationships and event system topologies?

Graph analysis works for assessing IAM relationships and event system topologies by mapping permissions and event subscriptions as directed edges. This reveals hidden structural hubs, evaluates dependency direction, and supports failure-mode comparisons for reliability planning.

What is the best way to plan service decoupling and migration using dependency mapping?

The best way to plan service decoupling and migration using dependency mapping is to identify high-centrality hubs and articulation points. Structural recommendations then target these risky dependencies to reduce change cascades and isolate blast radius during migrations.