mikrotik_skill

Overview

This skill connects to MikroTik RouterOS devices over the RouterOS API and provides a unified interface to inspect and manage router status, firewall rules, network configuration, and run custom RouterOS commands. It supports multiple devices, environment-variable or workspace-based credential configuration, and returns parsed, human-readable summaries of common RouterOS data. The skill is designed for quick operational checks and lightweight automation of routine tasks.

How this skill works

The skill uses a Python-based API client to open a session to the RouterOS API (default port 8728, SSL 8729 when available) and issues RouterOS commands to collect data. It parses multi-entry responses (interfaces, routes, ARP, firewall rules, DHCP leases, etc.) into compact summaries and structured lists. You can target a specific device by name or rely on environment variables; custom RouterOS commands are forwarded and their raw or parsed output is returned.

When to use it

• Quickly check device health: CPU, memory, storage, uptime.
• Audit firewall rules (filter, NAT, mangle) or IP configurations.
• Inspect interfaces, VLANs, bridges, or interface traffic statistics.
• View DHCP leases, ARP table, WireGuard peers, or users.
• Run custom RouterOS commands for advanced troubleshooting.
• Discover devices and scan the local network for MikroTik routers.

Best practices

• Enable the RouterOS API service and confirm network reachability before use.
• Prefer environment variables for automation; use workspace entries for multi-device contexts.
• Avoid running destructive commands without explicit confirmation and administrative privileges.
• Rotate credentials and avoid using empty passwords on production devices.
• Limit access to the API port with firewall rules and monitor API usage logs.

Example use cases

• Get a concise system health summary for the office router to check CPU, memory, and firmware version.
• List all NAT and filter firewall rules on a branch device during a security review.
• Retrieve interface counters and recent traffic stats to diagnose a bandwidth issue.
• Scan the local LAN to discover MikroTik devices and aggregate MAC/IP/model information.
• Execute a custom RouterOS command such as /ip/route/print to inspect routing tables for troubleshooting.