routeros-command-tree

Solid

RouterOS command tree introspection via /console/inspect API. Use when: building tools that parse RouterOS commands, generating API schemas from RouterOS, working with /console/inspect, mapping CLI commands to REST verbs, traversing the RouterOS command hierarchy, or when the user mentions inspect, command tree, RAML, or OpenAPI generation for RouterOS.

API & Backend 40 stars 9 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
54
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# RouterOS Command Tree & /console/inspect ## Overview RouterOS organizes all configuration and commands in a **hierarchical tree**. Every path in the CLI (like `/ip/address/add`) corresponds to a node in this tree. The `/console/inspect` REST endpoint lets you **programmatically explore the entire tree** — this is how tools like `restraml` (RAML/OpenAPI schema generator) and `rosetta` (MCP command lookup) build their databases. ## The Command Tree Structure RouterOS's command hierarchy has four node types: | Node Type | Meaning | Example | |---|---|---| | `dir` | Directory — contains child paths | `/ip`, `/system` | | `path` | Path — a navigable level (often has commands) | `/ip/address`, `/interface/bridge` | | `cmd` | Command — an executable action | `add`, `set`, `print`, `remove`, `get`, `export` | | `arg` | Argument — a parameter to a command | `address=`, `interface=`, `disabled=` | ### Tree Example ```text / (root dir) ├── ip/ (dir) │ ├── address/ (path) │ │ ├── add (cmd) │ │ │ ├── address (arg) — "IP address" │ │ │ ├── interface (arg) — "Interface name" │ │ │ └── disabled (arg) — "yes | no" │ │ ├── set (cmd) │ │ ├── remove (cmd) │ │ ├── get (cmd) │ │ ├── print (cmd) │ │ └── export (cmd) │ ├── route/ (path) │ │ └── ... │ └── dns/ (path) │ ├── set (cmd) │ ├── cache/ (path) │ │ ├── print (cmd) │ │ └── flush (cmd) │ └── ... ├── interface/ (dir) │ └── ... ├── system/ (dir) │ └...

Details

Author
tikoci
Repository
tikoci/routeros-skills
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Solid

routeros-syntax-inspection

Inspecting and validating RouterOS command/script syntax against a live device via /console/inspect (highlight, completion, syntax, child) and :parse IL. Use when: validating RouterOS commands before execution, explaining or linting RouterOS scripts, building syntax-aware tooling (LSP servers, validators, agent explain/check commands), interpreting highlight token streams or :parse intermediate language, discovering enum values or argument schemas, or when the user mentions console/inspect, highlight tokens, parseIL, or RouterOS script validation.

40 Updated 1 weeks ago
tikoci
API & Backend Solid

routeros-fundamentals

RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.

40 Updated 1 weeks ago
tikoci
Code & Development Solid

routeros-scripting

RouterOS scripting language and CLI configuration idioms for .rsc files and interactive commands. Use when: writing or reviewing RouterOS scripts, scheduler/netwatch/on-event snippets, idempotent CLI config, :local/:global/:foreach/:do syntax, [find] selectors, print as-value handling, script permissions, or when the user mentions .rsc, RouterOS script, scripting tips, or CLI config automation.

40 Updated 1 weeks ago
tikoci