routeros-skills

Nineteen skills for MikroTik RouterOS v7: scripting, firewall, containers, hotspot, the REST API and disposable CHR test routers

  • 89 ★ on the repository
  • Last commit
Skill

Minimal access

Why this level

  • The skills are text. Risk appears when an agent applies scripts and firewall rules to a real router, so check configuration on a CHR first.
All reasons and checks

tikoci/routeros-skills

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/routeros-skills

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The skills are text. Risk appears when an agent applies scripts and firewall rules to a real router, so check configuration on a CHR first.

This is third-party code. Review the repository files before installing.

What it does

The repository collects skills that give an agent context on MikroTik RouterOS 7. Each sits in a folder with a `SKILL.md` and a `references/` directory. The README table lists nineteen skills: CLI and REST API basics, `.rsc` scripting, firewall and NAT, containers, hotspot, the `/app` YAML format, the `/console/inspect` command tree, running a CHR virtual router in QEMU, ZeroTier, flashing with `netinstall-cli`, plus notes on the MNDP, MAC-Telnet and TZSP sniffer protocols. Names are split by prefix. `routeros-*` holds knowledge of the system itself, while `routeros-tikoci-*` covers the author tools quickchr and centrs, which let an agent boot a disposable CHR, apply configuration and read it back to check it.

Who it is for. Network engineers and MikroTik administrators who write RouterOS scripts and configuration with Claude Code, Codex or Copilot.

Good fit when

  • An agent writes an `.rsc` script and needs the syntax, `[find]` selectors and scheduler policies
  • Firewall and NAT rules are drafted with rule order and connection tracking in mind
  • A configuration is checked on a disposable CHR virtual router before it reaches hardware
  • Containers on the router are set up through VETH, bridges and OCI images

Not a fit when

  • You want an agent that drives the router over the API with no scripts of your own: MCP servers cover that
  • The device runs RouterOS 6, while the skills cover version 7 only
  • The task is outside MikroTik, as there is no general networking knowledge here

Example request

Write a RouterOS script that checks gateway reachability hourly and logs it, then test it on a CHR

Limitations

The skills hold knowledge and instructions, while the agent gets router access separately through REST API credentials, SSH or the quickchr and centrs tools. Some notes depend on recent versions: the `/app` YAML format needs RouterOS 7.21 or later and custom YAML 7.22 or later. The repository installs by cloning and running `make link`, with no plugin package. After the centrs and quickchr skills were renamed, existing installs have to run `make link` again.

How to disable. Remove the `routeros-*` symlinks from `~/.claude/skills`, `~/.agents/skills` and `~/.copilot/skills`, then the cloned folder if you wish.

FAQ

Which skill should I start with?

Start with `routeros-fundamentals`, since the others build on it. It covers the CLI, REST API, scripting and how the system is organised.

How do I install the skills in Claude Code?

Clone the repository, enter it and run `make link`. It creates symlinks in the skill directories of Claude Code, Codex, Copilot and Hermes, and `make check` verifies the result.

Do I need a physical router to test configuration?

No. The `routeros-qemu-chr` skill and the quickchr tools boot a virtual CHR in QEMU, apply configuration there and read it back.

How do these skills differ from a MikroTik MCP server?

Skills give the agent knowledge and techniques, while an MCP server runs commands on the device. You can use both together.

Which agents see these skills?

Claude Code, GitHub Copilot, Codex and Hermes: `make link` creates links in `~/.claude/skills`, `~/.copilot/skills`, `~/.agents/skills` and `~/.hermes/skills`.

Discussion

No questions or reviews yet.

Skills

An MCP server for MikroTik RouterOS and SwOS: 133 typed tools with dry-run, snapshots and change rollback.

MCP serverBroad access106Repository stars

Skill configures OpenTelemetry: collectors, sampling, security and telemetry from AI agents, without flooding the context.

SkillMinimal access54Repository stars

An MCP server for MikroTik routers: the agent reads and changes RouterOS configuration over SSH on a chat request

MCP serverBroad access334Repository stars

MCP server searches MikroTik RouterOS docs, command trees and device specs through a local SQLite database.

MCP serverMinimal access55Repository stars

A small server and the skb CLI for private skill distribution: publish, version, install and roll back skills across agents

CLIExtended access122Repository stars

31 DevOps skills for Claude Code and Codex: config generators, validators and a Kubernetes debugger for Terraform, Helm, CI and Docker

SkillExtended access339Repository stars

README in short

The README presents the set as a SkillStore for RouterOS 7, lists the skills in a table and explains the name prefixes. Installation comes down to cloning and `make link`, and the repository is the single source for all `routeros-*` skills.

README badge

Report a problem