<< All versions
Skill v1.0.2
currentAutomated scan82/100automateyournetwork/netclaw/eve-ng-console-ops
4 files
──Details
PublishedOctober 2, 2026 at 02:56 AM
Content Hashsha256:35093da500e9dd95...
Git SHAbcc313490395
Bump Typepatch
──Files
Files (1 file, 1.7 KB)
SKILL.md1.7 KBactive
SKILL.md · 35 lines · 1.7 KB
version: "1.0.2" name: eve-ng-console-ops description: Execute live CLI commands on running EVE-NG nodes over telnet console. Use when running show commands, making live config changes, verifying protocol state, testing connectivity, checking console readiness, or interacting with IOS, Junos, VPCS, EOS, or NX-OS nodes. user-invocable: true metadata: {"openclaw":{"requires":{"bins":["python3"],"env":["EVE_URL","EVE_USER","EVE_PASSWORD"]}}}
EVE-NG Console Operations
Use this skill for live console interaction with running nodes.
Workflow
- Discover the node console first.
- Determine the landed mode before sending commands.
- Use the OS-specific execution tool.
- For config changes, verify command results in the returned transcript before claiming success.
- Read
{baseDir}/references/console-guardrails.mdwhen boot state, mode handling, or Junos commit behavior matters.
Available tools
eve_discover_nodeeve_exec_ioseve_exec_junoseve_exec_vpcseve_exec_eoseve_exec_nxos
Failure Behavior
- If a tool call fails with an authentication or connection error, check that
EVE_PASSWORD,EVE_URL,EVE_USERare set and valid before assuming a data or device problem. - On a tool error (timeout, unreachable host, malformed response), report the failure and its error message directly to the user rather than fabricating or guessing at results.
- For a confirmed read-only call, check connectivity and retry once if appropriate. For any call that changes state or sends a message, a timeout does not prove the action failed: inspect current state or delivery status before retrying, preserve the required approval/change gates, and do not repeat an action whose outcome is unknown.