/install ensp
\r \r
eNSP Topology Skill\r
\r
Generate eNSP (Enterprise Network Simulation Platform) topology files as native .topo files that can be opened directly in eNSP.\r
\r
How to create a topology\r
\r
- Parse user's request to identify:\r
- Network devices (routers, switches, PCs, Cloud, etc.)\r
- Connections between devices\r
- Optional: text labels, area boxes\r \r
- Generate UUIDs for each device using a valid UUID v4 format\r \r
- Calculate layout coordinates for devices using auto-layout algorithm\r \r
- Build the .topo XML following the format in
references/topo-reference.md\r \r - Write the file to current directory using Write tool\r \r
- Open the result - print the file path so user can open it in eNSP\r \r
Output format\r
\r
Always output a .topo file. The user will open it in eNSP for simulation.\r
\r
Example filenames:\r
simple-network.topo\rospf-topology.topo\rcampus-network.topo\r \r
Device types supported\r
\r
Routers\r
\r | Model | Description | Interface Config |\r |-------|-------------|------------------|\r | AR201 | Router | Ethernet x8 + Ethernet x1 |\r | AR1220 | Router | 2GE + 8Ethernet |\r | AR2220 | Router | GE x1 + GE x2 + Serial x2 |\r | AR2240 | Router | GE x1 + GE x2 |\r | AR3260 | Router | GE x1 + GE x2 |\r | Router | Generic Router | Ethernet x2 + GE x4 + Serial x4 |\r | NE40E | Enterprise Router | 10x Ethernet (slot format) |\r | NE5000E | Core Router | 10x Ethernet (slot format) |\r | NE9000 | Core Router | 10x Ethernet (slot format) |\r | R250D | Router | GE x1 |\r \r
Switches\r
\r | Model | Description | Interface Config |\r |-------|-------------|------------------|\r | S3700 | Switch | Ethernet x22 + GE x2 |\r | S5700 | Switch | 24GE |\r | CE6800 | Data Center Switch | 20x GE (slot format) |\r | CE12800 | Data Center Switch | 10x GE (slot format) |\r | CX | Switch | 10x Ethernet (slot format) |\r \r
Firewalls\r
\r | Model | Description | Interface Config |\r |-------|-------------|------------------|\r | USG5500 | Firewall | GE x9 |\r | USG6000V | Firewall | GE x1 (slot0) + GE x7 (slot1) |\r \r
Wireless\r
\r | Model | Description | Interface Config |\r |-------|-------------|------------------|\r | AC6005 | Wireless AC | 8GE |\r | AC6605 | Wireless AC | 24GE |\r | AP2050 | Wireless AP | 5GE |\r | AP3030 | Wireless AP | 1GE |\r | AP4030 | Wireless AP | 2GE |\r | AP4050 | Wireless AP | 2GE |\r | AP5030 | Wireless AP | 2GE |\r | AP6050 | Wireless AP | 2GE |\r | AP7030 | Wireless AP | 2GE |\r | AP7050 | Wireless AP | 2GE |\r | AP8030 | Wireless AP | 3GE |\r | AP8130 | Wireless AP | 3GE |\r | AP9131 | Wireless AP | 2GE |\r | AD9430 | LTE Module | 28GE |\r | STA | Wireless Station | Wireless |\r | Cellphone | Mobile Device | Wireless |\r \r
Endpoints\r
\r | Model | Description | Interface Config |\r |-------|-------------|------------------|\r | PC | PC | 1GE |\r | Laptop | Laptop | 1GE |\r | Server | Server | 1Ethernet |\r | Client | Client | 1Ethernet |\r | MCS | Multicast Server | 1Ethernet |\r | Cloud | Cloud/BNI | Ethernet interfaces |\r | FRSW | Frame Relay Switch | Serial x16 |\r | HUB | Ethernet HUB | Ethernet x16 |\r \r
Connection types\r
\r | Type | Description |\r |------|-------------|\r | Copper | Ethernet cable |\r | Serial | Serial cable |\r | Auto | Auto-detect |\r \r
Layout algorithm\r
\r Use a simple grid-based auto-layout:\r \r
Grid spacing: 200px horizontal, 150px vertical\r
Device size: ~80x60px\r
Start position: (100, 100)\r
\r
For each row:\r
- Place devices horizontally with 200px gap\r
- Move to next row when reaching canvas width (~1200px)\r
```\r
\r
Adjust positions based on device types and connections to create logical groupings.\r
\r
## Adding text labels (txttips)\r
\r
Common labels for network diagrams:\r
- Loopback addresses: `Loopback0:10.0.1.1/24`\r
- Network segments: `10.0.12.0/24`\r
- Area labels: `Area0`, `Area1`, `AS 64512`\r
- Device roles: `Core Layer`, `Access Layer`\r
\r
## Adding area boxes (shapes)\r
\r
Use type="1" shapes with appropriate colors to group devices:\r
- Same area devices in one rectangle\r
- Different colors for different areas/zones\r
\r
## File naming\r
\r
- Use lowercase with hyphens\r
- Descriptive name based on topology purpose\r
- End with `.topo` extension\r
\r
## Opening the result\r
\r
After writing the file, print the absolute path:\r
```\r
Topology saved to: C:\path o opology.topo\r
Please open this file in eNSP to view and simulate.\r
```\r
\r
## XML format reference\r
\r
Consult `references/topo-reference.md` for complete XML structure including:\r
- Device XML format with slots and interfaces\r
- Line XML format with interfacePair details\r
- Shape XML format for area boxes\r
- Txttip XML format for text annotations\r
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ensp - After installation, invoke the skill by name or use
/ensp - Provide required inputs per the skill's parameter spec and get structured output
What is eNSP?
Always use when user asks to create, generate, or design a network topology diagram for eNSP (Enterprise Network Simulation Platform), or mentions creating e... It is an AI Agent Skill for Claude Code / OpenClaw, with 137 downloads so far.
How do I install eNSP?
Run "/install ensp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is eNSP free?
Yes, eNSP is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does eNSP support?
eNSP is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created eNSP?
It is built and maintained by forealmy (@forealmy); the current version is v1.1.0.