routeros-syntax-inspection

# RouterOS Syntax Inspection ## Overview RouterOS exposes its **own parser** over the REST API: `/console/inspect` classifies every byte of console input (`highlight`), proposes continuations (`completion`), returns structured help (`syntax`), and enumerates the command tree (`child`); the `:parse` scripting command returns the intermediate language (IL) the engine actually executes. Together these are the ground truth for "is this valid RouterOS?" — version-exact, package-exact, and even runtime-state-exact, which no static grammar can be. This skill is a **probe-selection and wire-format guide**: which surface answers which question, how to read each response, and which claims the responses do and do not support. It is grounded in full-corpus captures (913 scripts × multiple RouterOS versions) published in [tikoci/lsp-routeros-ts](https://github.com/tikoci/lsp-routeros-ts) — the `docs/` references there carry the full evidence [^1]. **"Parse RouterOS" is not one operation.** Pick the probe for the question: | Question | Probe | What it cannot establish | |---|---|---| | Which span is a command, argument, variable, comment, live-state marker? | `request=highlight` | Nested structure; value validity; anything after the first hard error | | Is the script structurally valid; what blocks/expressions result? | `:parse` | Source ranges; partial IL on error; path/argument split without schema data | | What is valid at this cursor position? Enum values? | `request=completion` |...