Agent skill · research science · aiskillstore
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.
Why this skill is useful
Provides detailed RouterOS CLI and REST API commands that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
RouterOS Fundamentals RouterOS Is NOT GNU/Linux RouterOS runs a Linux kernel (5.6.3) but everything above the kernel is MikroTik's proprietary nova system. This is the single most important fact for agents to internalize. What does NOT exist on RouterOS: No /bin, /usr, /etc, /var — no FHS layout No bash, sh, ash, zsh — no Unix shell at all No coreutils (ls, cat, grep, ps, mount, ip, iptables, etc.) No glibc, musl, busybox No apt, pkg, opkg — no package manager (packages are .npk files installed via upload + reboot) No systemctl, service, init system No /proc or /sys accessible from userland No docker, podman — RouterOS has its own /container subsystem (7.x+) What DOES exist: RouterOS CLI — its own language, not shell. Accessed via SSH, serial, WinBox, or WebFig REST API at /rest/ (HTTP, port 80 by default) — the primary programmatic interface RouterOS scripting language (.rsc files) — its own syntax, not bash. See Scripting reference WebFig (web UI) on port 80 WinBox protocol on port 8291 Common agent mistakes to avoid: Do NOT try ssh admin@host 'ls /' — it opens RouterOS CLI, not a shell Do NOT suggest mount, fdisk, mkfs — use /disk commands instead Do NOT look for config files at /etc/ — configuration is in the RouterOS database Do NOT assume ping works the same — it's /tool/ping or /ping in CLI Do NOT suggest installing packages via apt or opkg — upload .npk via SCP then /system/package/apply-changes (7.18+) or /system/reboot (<7.18) See Extra packages reference for the full package list and installation pattern RouterOS CLI Syntax RouterOS CLI uses path-based navigation, not Unix command pipelines: Key syntax differences from shell: = assigns properties (no spaces around it) [find ...] is the query expression (like WHERE) Strings use "" (double quotes only) Comments use # Variables: :local myVar "value" and $myVar No pipes, no redirection, no subshell REST API RouterOS REST API at http://HOST:PORT/rest/. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/routeros-fundamentals