Skill: RouterOS .rsc

This skill guides the creation, editing, and review of RouterOS (.rsc) scripts with safe and idempotent patterns, plus validation before import.

Quick workflow

Define script objective and scope.

Apply idempotent patterns (see References).

Validate syntax and risks with the linter (scripts/lint_rsc.py).

Test import with

dry-run

and

on-error

.

Import in a controlled manner to production.

Essential practices

Prefer

find where ...

+ conditionals before

add

/

set

.

Avoid broad policies in

/system script add policy=...

.

Use

:onerror

and

:jobname

for robustness and single instance.

Never include destructive commands (

system reset-configuration

, etc.).

Parameterize and isolate scopes (

:local

vs

:global

).

Validation and testing

Lint:

python scripts/lint_rsc.py path/to/script.rsc

.

Safe import (RouterOS ≥ 7.16.x):

import test.rsc verbose=yes dry-run

to find multiple errors without applying changes.

do { import test.rsc } on-error={ :put "Failure" }

to capture error.

onerror e in={ import test.rsc } do={ :put "Failure - $e" }

for detailed message.

References (use as needed)

Language and syntax: see references/LANGUAGE.md

.rsc export/import,

dry-run

and

onerror

see references/RSC_GUIDE.md Security and idempotency best practices: see references/SAFE_PRACTICES.md Common examples and patterns: see references/EXAMPLES.md Linter rules: see references/LINTER_RULES.md Notes Scripts should be consistent with RouterOS v7 (preferred) and compatible with v6 where possible. Use print as-value , arrays, and where filters for robust queries. For scheduled execution, use Scheduler with appropriate permissions.