# Manage RouterOS v7 With AI Agents

RouterOS differs from standard Linux, so generic shell advice often fails. This skill gives Claude, Codex, and Claude Code RouterOS-specific CLI, REST API, and automation guidance.

## Install

```bash
npx skillstore add tikoci/routeros-fundamentals
```

## Metadata

- Status: approved
- Slug: tikoci-routeros-fundamentals
- Skillstore revision: r1
- Version status: missing
- Tree hash: d15b3e6c552be60bc8c860225b31471b7e89e8fded34aac536a9f65965728a08
- Author: tikoci
- GitHub username: tikoci
- License: MIT
- Repository: https://github.com/tikoci/routeros-skills/tree/main/routeros-fundamentals
- Ref: 3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access, network, scripts, filesystem
- Quality score: 76
- Public page: https://skillstore.pages.dev/skills/tikoci-routeros-fundamentals
- Manifest: https://skillstore.pages.dev/api/skills/tikoci-routeros-fundamentals/manifest

## Capabilities

- Explains RouterOS CLI syntax and key differences from GNU/Linux systems.
- Maps RouterOS REST verbs to CLI actions and common endpoint patterns.
- Covers RouterOS v7 packages, licensing, users, SSH keys, networking, firewall rules, and device-mode behavior.
- Documents async REST commands, blocking endpoints, timeout handling, and post-boot race conditions.
- Provides examples for curl, TypeScript fetch, RouterOS scripts, and CHR automation workflows.

## Use Cases

- Plan RouterOS REST Changes: Prepare safe REST API changes for firewall, users, packages, DNS, routes, and interfaces.
- Automate CHR Provisioning: Build CHR setup flows that handle package enablement, reboot behavior, device-mode updates, and readiness polling.
- Translate Linux Assumptions: Convert generic Linux commands into RouterOS CLI or REST workflows before generating operational instructions.

## Prompt Templates

### Explain RouterOS Basics

```
Explain how RouterOS v7 differs from GNU/Linux for CLI, files, packages, and service management. Keep the answer practical for an AI agent.
```

### Plan A REST Task

```
I need to change RouterOS v7 settings through REST. Identify the correct endpoint, HTTP verb, request shape, verification step, and any RouterOS gotchas.
```

### Review Firewall Changes

```
Review this planned RouterOS firewall change for ordering, rule placement, verification, and lockout risk. Explain what should be checked before applying it.
```

### Design CHR Automation

```
Design a CHR automation flow for RouterOS v7 that handles boot readiness, user setup, SSH keys, package changes, blocking REST commands, and post-change validation.
```

## Limitations

- Covers RouterOS 7.x only; RouterOS v6 behavior may differ.
- Reference files are not executable and do not connect to routers by themselves.
- Some endpoint behavior is marked as CHR-specific or derived from documentation.
- Live router validation requires separate authorized access and tooling.

## Best Practices

- Confirm RouterOS version, hardware type, and lab versus production context before applying examples.
- Replace placeholder hosts and local CHR addresses with authorized router targets only.
- Back up configuration and verify router state after any REST or CLI change.

## Anti Patterns

- Treating RouterOS SSH as a Linux shell with commands such as ls, apt, or systemctl.
- Adding firewall rules without controlling placement or verifying evaluation order.
- Running blocking REST commands without timeouts, polling, or recovery steps.

## Security Audit

- Audited at: 2026-07-09T09:44:39.677\+00:00
- Summary: The static scan flagged command, network, credential, filesystem, and destructive-command patterns, but they occur in markdown reference examples for RouterOS administration. I found no prompt-injection text, executable payloads, embedded private keys, unauthorized network callbacks, or local filesystem access in the skill files.

## Stats

- Views: 193
- Downloads: 18
- Favorites: 0
- Popularity score: 0