network-engineering

v0.1.2

Network-engineering team — agents (network-architect, network-operations-engineer) for the ENTERPRISE network layer below the cloud VPC: campus/datacenter/WAN topology, routing (OSPF/BGP/EIGRP/static) and switching (VLANs, STP, LACP, VXLAN/EVPN), IP addressing/IPAM and DNS/DHCP, segmentation + zero-trust network access (microsegmentation, NAC, SASE/SD-WAN), load balancing, redundancy/HA (HSRP/VRRP, dual-homing), and day-2 ops (change windows, troubleshooting the OSI stack, observability/NetFlow). Knowledge bank with Mermaid decision trees (topology, routing-protocol selection, segmentation) + a dated 2026 capability map, skills, best-practices, templates, an advisory hook (any/any rules, telnet, no change window). Design-before-config; protocol-before-vendor-CLI. Seams: cloud VPC networking -> aws/azure/gcp-cloud; service mesh / k8s networking -> cloud-native-kubernetes; security verdicts -> security-engineering; IaC for network config -> terraform-iac. Requires ravenclaude-core@>=0.7.0.

Claude Code5 Skills

By Matt CorbettLicense: MIT7 GitHub starsUpdated last week

Directory evidence

Runtimes: Claude Code
Parsed components: 5 skill or MCP entries
Source updated: Sep 15, 2026
Manifest status: Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install network-engineering for Claude Code

Installs for the current user

claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install network-engineering@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually

$ git clone https://github.com/mcorbett51090/RavenClaude

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/network-engineering/.

Plugin files

plugins/network-engineering/

├── .claude-plugin/plugin.json
├── skills/design-network-topology/SKILL.md
├── skills/design-segmentation-and-zero-trust/SKILL.md
├── skills/plan-network-change/SKILL.md
├── skills/select-routing-protocol/SKILL.md
└── skills/troubleshoot-connectivity/SKILL.md

Included Skills5

design-network-topologyskills/design-network-topology/SKILL.md

Design a campus/datacenter/branch/WAN network topology by traversing the topology decision tree (scale -> traffic pattern -> redundancy need -> topology), then return the recommended topology (collapsed-core vs 3-tier vs spine-leaf vs hub-and-spoke/SD-WAN), an IP addressing plan (summarizable, room to grow), the redundancy/failure model (HSRP/VRRP, dual-homing, MLAG), and a labelled diagram description. Reach for this when the user asks to "design the network for <site/DC>". Used by `network-architect` (primary).

design-segmentation-and-zero-trustskills/design-segmentation-and-zero-trust/SKILL.md

Design network segmentation and a zero-trust network access posture by traversing the segmentation decision tree (what to isolate -> blast radius -> enforcement point -> identity model), then return the segment plan (VLANs/VRFs/microsegmentation), the east-west + north-south policy model, the NAC/802.1X posture, and the SASE/SD-WAN or firewall enforcement point. Reach for this when the user asks "how do we segment <IoT/OT/guest/PCI> off the network?". Used by `network-architect` (primary); security verdicts escalate to security-engineering.

plan-network-changeskills/plan-network-change/SKILL.md

Turn a network change (routing/VLAN/firewall/cutover) into a staged, reversible plan — blast-radius assessment, change window, pre-checks (baseline), the staged steps with verification gates, and a tested rollback — so no change is a big-bang gamble. Reach for this when the user needs to make a risky network change safely or migrate/cut over network infrastructure. Used by `network-operations-engineer` and `network-architect`.

select-routing-protocolskills/select-routing-protocol/SKILL.md

Choose the right routing protocol (static, OSPF, EIGRP, IS-IS, BGP) for a given boundary and scale by traversing the routing-protocol decision tree (administrative boundary -> scale -> multi-vendor -> convergence/policy need), then return the recommendation, the design knobs (OSPF areas, BGP ASNs/route-reflectors/communities, summarization), and why the alternatives were ruled out. Reach for this when the user asks "OSPF vs BGP vs static between <X>?". Used by `network-architect` (primary).

troubleshoot-connectivityskills/troubleshoot-connectivity/SKILL.md

Isolate a network connectivity fault methodically, bottom-up the OSI stack (L1 link -> L2 VLAN/ARP/MAC -> L3 routing/ACL -> L4 port/firewall -> L7 DNS/app), naming the specific isolating test and confirming command at each layer, then return the ranked most-likely fault and how to confirm it. Reach for this when the user says "X can't reach Y" or reports intermittent/slow connectivity. Used by `network-operations-engineer` (primary).

Plugin manifests1

plugins/network-engineering/.claude-plugin/plugin.json

{
  "name": "network-engineering",
  "version": "0.1.2",
  "description": "Network-engineering team — agents (network-architect, network-operations-engineer) for the ENTERPRISE network layer below the cloud VPC: campus/datacenter/WAN topology, routing (OSPF/BGP/EIGRP/static) and switching (VLANs, STP, LACP, VXLAN/EVPN), IP addressing/IPAM and DNS/DHCP, segmentation + zero-trust network access (microsegmentation, NAC, SASE/SD-WAN), load balancing, redundancy/HA (HSRP/VRRP, dual-homing), and day-2 ops (change windows, troubleshooting the OSI stack, observability/NetFlow). Knowledge bank with Mermaid decision trees (topology, routing-protocol selection, segmentation) + a dated 2026 capability map, skills, best-practices, templates, an advisory hook (any/any rules, telnet, no change window). Design-before-config; protocol-before-vendor-CLI. Seams: cloud VPC networking -> aws/azure/gcp-cloud; service mesh / k8s networking -> cloud-native-kubernetes; security verdicts -> security-engineering; IaC for network config -> terraform-iac. Requires ravenclaude-core@>=0.7.0.",
  "author": {
    "name": "Matt Corbett"
  },
  "homepage": "https://github.com/mcorbett51090/RavenClaude",
  "license": "MIT",
  "keywords": [
    "network-engineering",
    "routing",
    "switching",
    "bgp",
    "ospf",
    "vlan",
    "vxlan",
    "evpn",
    "sd-wan",
    "sase",
    "zero-trust",
    "microsegmentation",
    "load-balancing",
    "dns",
    "dhcp",
    "ipam",
    "nac",
    "hsrp",
    "vrrp",
    "netflow"
  ],
  "requires": {
    "plugins": [
      "ravenclaude-core@>=0.7.0"
    ]
  }
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[network-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/network-engineering)