What problem does it solve? Native WinBox (M2) reads and writes against MikroTik RouterOS can return wrong or empty data, silently drop fields, or fail with cryptic 0xFE00xx errors because handler numbers, field keys, and wire encodings are version-volatile and undocumented. This Skill guides the diagnosis and implementation of fixes in the tik4net C# resolver/codec layer by triangulating three sources of truth instead of guessing wire formats. ## Core Features & Use Cases - Path and handler mapping: Add a new RouterOS path to the native transport by locating its window in the .jg catalog and wiring a shipped alias or override in WinboxHandlerMap. - Field encoding/decoding: Implement new UI-type encoders in WinboxFieldResolver.EncodeField and decoders in WinboxRecordCodec.FormatTyped by reading the authoritative types.* functions from webfig master*.js. - Action verbs and streaming monitors: Wire .jg doit/action commands and query/pollcmd monitors through WinboxNativeM2Operations. - Live verification: Probe raw M2 frames with WinboxM2Client test classes and trace real connection writes via OnWriteRow to confirm exact bytes. - Use Case: A firewall dst-port field is silently dropped on write. Use the Skill to find its multinumberrange uitype in the .jg, read types.multinumberrange.put in master*.js, implement the flat u32[] range encoding, and verify the round-trip against a live router. ## Quick Start Ask the AI to add native WinBox support for a RouterOS path or fix a mis-encoded field, providing the router version and the path or field name involved.
