ecc-network-architect

Reviews network topology, routing, and segmentation plans and produces phased architecture designs.

Updated Apr 18, 2025
One-click install
npx skills add https://github.com/adriancodes/dotfiles --skill ecc-network-architect-adriancodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecc-network-architect
Source: https://github.com/adriancodes/dotfiles/tree/main/dot_agents/skills/ecc-network-architect
Command: npx skills add https://github.com/adriancodes/dotfiles --skill ecc-network-architect-adriancodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing or reviewing a network topology without a structured process leads to missed requirements, weak segmentation, and risky cutovers. This Skill provides a disciplined, read-only workflow for statically reviewing proposed network designs and producing implementable architecture plans with validation gates and rollback points. ## Core Features & Use Cases - Static Design Review: Inspects supplied topologies, routing designs, and segmentation plans without connecting to devices or running live diagnostics. - Structured Architecture Output: Produces a consistent deliverable covering topology rationale, addressing and segmentation tables, routing and connectivity, management plane, phased implementation, and risk registers. - Optional Focused Skill Handoffs: References companion skills for config validation, BGP diagnostics, interface health, IOS patterns, and SSH automation, with fallback guidance when they are unavailable. - Use Case: A team planning a campus network refresh submits their requirements and existing constraints; the Skill identifies missing inputs (site count, uptime target, compliance scope), recommends a routed topology with explicit segmentation zones, and delivers a phased migration plan with rollback points. ## Quick Start Ask the assistant to review your proposed network topology and segmentation plan and produce a phased architecture design with risks and required follow-up evidence.

Frequently Asked Questions about ecc-network-architect

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

FAQPage Schema
How do I review a network topology design before implementation?▼

Static design review inspects the proposed topology, routing boundaries, and segmentation plan against stated requirements without touching live devices. This Skill restates objectives, identifies missing requirements, selects a topology, and produces a phased plan with validation gates and rollback points.

How to plan network segmentation for campus and branch networks?▼

Define explicit zones for management, server, user, guest, IoT/OT, and regulated environments, each with its own routing boundary and allowed flows. Prefer routed boundaries over stretched layer-2 designs unless a workload requirement proves otherwise.

Can this Skill connect to routers or run live network diagnostics?▼

No, it is strictly read-only and static. It never connects to devices, runs show commands, or collects live logs; instead it requests redacted operator-provided evidence such as BGP neighbor output or timed interface counters.

What information is needed before designing a network architecture?▼

Key inputs include site count, user and device counts, critical applications, compliance scope, uptime targets, existing hardware, budget tier, and cutover tolerance. Missing items that materially change the architecture are flagged as required follow-up questions.

When should I avoid stretched layer-2 network designs?▼

Avoid stretched layer-2 unless a specific workload requirement proves it necessary, since routed boundaries offer better failure isolation and simpler operations. The Skill defaults to the simplest routing design that satisfies scale, operations, and risk constraints.