← Back to Skills Marketplace
forealmy

ensp

by forealmy · GitHub ↗ · v1.1.0 · MIT-0
cross-platform ✓ Security Clean
100
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install tmpkze5hyjf
Description
Always use when user asks to create, generate, or design a network topology diagram for eNSP (Enterprise Network Simulation Platform), or mentions creating e...
Usage Guidance
This skill appears coherent and limited to creating local eNSP .topo files. Before using: run the skill in a non-sensitive/isolated working directory (it writes files there), review generated .topo XML if you want to confirm contents before opening in eNSP, and avoid pasting secrets or unrelated credentials into prompts. Because it's an instruction-only skill, there's no installer or network activity to review — the main risk is just the usual file-write behavior, so don't run it from directories containing sensitive files.
Capability Analysis
Type: OpenClaw Skill Name: tmpkze5hyjf Version: 1.1.0 The skill bundle is designed to generate network topology files (.topo) for Huawei's eNSP simulation platform. The instructions in SKILL.md and the technical reference in topo-reference.md provide legitimate XML templates and layout logic for creating these diagrams. There is no evidence of data exfiltration, malicious execution, or harmful prompt-injection instructions.
Capability Tags
crypto
Capability Assessment
Purpose & Capability
Name/description match the instructions: the skill only needs to parse user requests, generate topology XML, and write a .topo file. There are no unrelated binaries, env vars, or credentials requested.
Instruction Scope
SKILL.md stays within scope: parse user intent, create device UUIDs, compute layout, build XML per the included reference, and write the .topo file to the current directory. It does not ask to read unrelated system files, send data to external endpoints, or access secrets.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is downloaded or written to disk by an installer beyond the generated .topo file itself.
Credentials
No environment variables, credentials, or config paths are requested. The declared requirements are minimal and appropriate for generating local topology files.
Persistence & Privilege
always is false and the skill does not request persistent system-level privileges or attempt to modify other skills or agent config. It will write output files to the current working directory as intended.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install tmpkze5hyjf
  3. After installation, invoke the skill by name or use /tmpkze5hyjf
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
eNSP Topology Skill 1.1.0 - Now generates native .topo files for direct use with eNSP - Supports a wide range of Huawei routers, switches, firewalls, wireless, and endpoint devices - Adds auto-layout algorithm for visually organized diagrams - Allows inclusion of text labels and area boxes for clearer topologies - Prints absolute file path after saving the topology for easy access in eNSP
Metadata
Slug tmpkze5hyjf
Version 1.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

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 100 downloads so far.

How do I install ensp?

Run "/install tmpkze5hyjf" 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.

💬 Comments