ensp

v1.1.0

Always use when user asks to create, generate, or design a network topology diagram for eNSP (Enterprise Network Simulation Platform), or mentions creating e...

0· 49·0 current·0 all-time
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (eNSP topology generator) matches the content: SKILL.md and references describe building .topo XML, UUIDs, layout, device models, and writing a file. No unrelated environment variables, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are narrowly scoped to parsing the user request, generating topology XML, and writing a .topo file. The SKILL.md references only local file creation (Write tool) and a local reference doc. It does not instruct reading unrelated files, calling external endpoints, or accessing secrets.
Install Mechanism
There is no install spec or code to download; the skill is instruction-only and will not write or execute external code during install.
Credentials
The skill declares no required environment variables, credentials, or config paths. The actions described (UUID generation, layout calculation, XML assembly, writing a .topo) require no secrets and are proportionate to the purpose.
Persistence & Privilege
always is false and the skill does not request persistent or elevated privileges or modify other skills' configuration. Autonomous invocation is allowed (platform default) and appropriate for a user-invocable generator.
Assessment
This skill appears to do exactly what it says: generate .topo files for eNSP. Before installing, confirm your agent environment provides a safe, limited Write tool (so generated files go only to the intended workspace). Review any generated .topo file before opening it in eNSP (just in case), and avoid granting the agent broad filesystem or credential access — this skill does not need them.

Like a lobster shell, security has layers — review code before you run it.

latestvk978w9gmtz688mk4bd38r1pm4984eker
49downloads
0stars
1versions
Updated 1w ago
v1.1.0
MIT-0

eNSP Topology Skill

Generate eNSP (Enterprise Network Simulation Platform) topology files as native .topo files that can be opened directly in eNSP.

How to create a topology

  1. Parse user's request to identify:

    • Network devices (routers, switches, PCs, Cloud, etc.)
    • Connections between devices
    • Optional: text labels, area boxes
  2. Generate UUIDs for each device using a valid UUID v4 format

  3. Calculate layout coordinates for devices using auto-layout algorithm

  4. Build the .topo XML following the format in references/topo-reference.md

  5. Write the file to current directory using Write tool

  6. Open the result - print the file path so user can open it in eNSP

Output format

Always output a .topo file. The user will open it in eNSP for simulation.

Example filenames:

  • simple-network.topo
  • ospf-topology.topo
  • campus-network.topo

Device types supported

Routers

ModelDescriptionInterface Config
AR201RouterEthernet x8 + Ethernet x1
AR1220Router2GE + 8Ethernet
AR2220RouterGE x1 + GE x2 + Serial x2
AR2240RouterGE x1 + GE x2
AR3260RouterGE x1 + GE x2
RouterGeneric RouterEthernet x2 + GE x4 + Serial x4
NE40EEnterprise Router10x Ethernet (slot format)
NE5000ECore Router10x Ethernet (slot format)
NE9000Core Router10x Ethernet (slot format)
R250DRouterGE x1

Switches

ModelDescriptionInterface Config
S3700SwitchEthernet x22 + GE x2
S5700Switch24GE
CE6800Data Center Switch20x GE (slot format)
CE12800Data Center Switch10x GE (slot format)
CXSwitch10x Ethernet (slot format)

Firewalls

ModelDescriptionInterface Config
USG5500FirewallGE x9
USG6000VFirewallGE x1 (slot0) + GE x7 (slot1)

Wireless

ModelDescriptionInterface Config
AC6005Wireless AC8GE
AC6605Wireless AC24GE
AP2050Wireless AP5GE
AP3030Wireless AP1GE
AP4030Wireless AP2GE
AP4050Wireless AP2GE
AP5030Wireless AP2GE
AP6050Wireless AP2GE
AP7030Wireless AP2GE
AP7050Wireless AP2GE
AP8030Wireless AP3GE
AP8130Wireless AP3GE
AP9131Wireless AP2GE
AD9430LTE Module28GE
STAWireless StationWireless
CellphoneMobile DeviceWireless

Endpoints

ModelDescriptionInterface Config
PCPC1GE
LaptopLaptop1GE
ServerServer1Ethernet
ClientClient1Ethernet
MCSMulticast Server1Ethernet
CloudCloud/BNIEthernet interfaces
FRSWFrame Relay SwitchSerial x16
HUBEthernet HUBEthernet x16

Connection types

TypeDescription
CopperEthernet cable
SerialSerial cable
AutoAuto-detect

Layout algorithm

Use a simple grid-based auto-layout:

Grid spacing: 200px horizontal, 150px vertical
Device size: ~80x60px
Start position: (100, 100)

For each row:
  - Place devices horizontally with 200px gap
  - Move to next row when reaching canvas width (~1200px)

Adjust positions based on device types and connections to create logical groupings.

Adding text labels (txttips)

Common labels for network diagrams:

  • Loopback addresses: Loopback0:10.0.1.1/24
  • Network segments: 10.0.12.0/24
  • Area labels: Area0, Area1, AS 64512
  • Device roles: Core Layer, Access Layer

Adding area boxes (shapes)

Use type="1" shapes with appropriate colors to group devices:

  • Same area devices in one rectangle
  • Different colors for different areas/zones

File naming

  • Use lowercase with hyphens
  • Descriptive name based on topology purpose
  • End with .topo extension

Opening the result

After writing the file, print the absolute path:

Topology saved to: C:\path\to\topology.topo
Please open this file in eNSP to view and simulate.

XML format reference

Consult references/topo-reference.md for complete XML structure including:

  • Device XML format with slots and interfaces
  • Line XML format with interfacePair details
  • Shape XML format for area boxes
  • Txttip XML format for text annotations

Comments

Loading comments...