What problem does it solve? When a MikroTik router returns empty, garbled, or unexpected output over a terminal connection (Telnet, SSH-PTY, MAC-Telnet, WinBox CLI), it is hard to tell whether the router or the client library is at fault. This Skill provides a standalone Telnet probe script plus verified knowledge of RouterOS CLI quirks so you can establish ground truth independently of the tik4net library. ## Core Features & Use Cases - Standalone Telnet probe script: Tools/probes/telnet-cli-probe.ps1 performs Telnet IAC negotiation, VT100 cursor-probe answers, and login handling, then prints the raw bytes the router returns, without using tik4net. - RouterOS CLI quirks reference: Documents verified behaviors such as print as-value producing nothing interactively unless wrapped in :put, detail being required for full fields, print stats for live counters, quoting rules for where expressions, and VT100 terminal-size negotiation. - Use Case: A print as-value command over tik4net's Telnet transport returns nothing. Run the probe script against the router, confirm the router itself emits no output for bare print as-value, then fix the command builder to wrap it in :put [...]. ## Quick Start Run the probe script with the router host and credentials from the integration test App.config and a command like ':put [/interface print detail as-value]' to see the raw bytes the router sends back.
