# Automate RouterOS Netinstall Workflows

RouterOS recovery and reinstall workflows are easy to misorder. This skill gives grounded Netinstall guidance for packages, scripts, interfaces, and first boot behavior.

## Install

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

## Metadata

- Status: approved
- Slug: tikoci-routeros-netinstall
- Skillstore revision: r1
- Version status: missing
- Tree hash: f927561e8dea700f00cbc752161d1d06805e89968dc43edc9bb54af93a649fb8
- Author: tikoci
- GitHub username: tikoci
- License: MIT
- Repository: https://github.com/tikoci/routeros-skills/tree/main/routeros-netinstall
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/tikoci-routeros-netinstall
- Manifest: https://skillstore.pages.dev/api/skills/tikoci-routeros-netinstall/manifest

## Capabilities

- Explains official netinstall-cli syntax and option meanings.
- Distinguishes configure scripts from one-time mode scripts.
- Lists RouterOS package URL patterns and architecture naming rules.
- Shows command patterns for reinstall, empty config, and preserved configuration.
- Highlights etherboot, BOOTP, TFTP, and host networking requirements.

## Use Cases

- Plan a router reinstall: Prepare a RouterOS Netinstall workflow with package order, interface setup, and configuration behavior.
- Document recovery procedures: Create repeatable recovery notes for teams that restore MikroTik routers after failed upgrades.
- Build Netinstall tooling: Use grounded command examples and package rules when writing wrappers around netinstall-cli.

## Prompt Templates

### Explain Netinstall Basics

```
Explain what RouterOS netinstall-cli does, when to use it, and what data it may erase. Keep the answer concise.
```

### Choose Package Names

```
Given RouterOS version <version> and architecture <arch>, list the expected system package and all_packages file names.
```

### Plan a Safe Install Command

```
Help me plan a netinstall-cli command for interface <interface>, architecture <arch>, and RouterOS version <version>. Include risks and approval checks.
```

### Design First-Boot Automation

```
Review this RouterOS first-boot goal and propose whether to use -s or -sm. Explain script order, persistence, and security impact.
```

## Limitations

- It does not verify package checksums or signatures.
- It cannot detect router architecture without user supplied context.
- It does not replace MikroTik release notes or support guidance.
- It describes privileged commands that require careful human approval.

## Best Practices

- Confirm the target device, interface, packages, and backup status before running Netinstall.
- Use a dedicated isolated Layer 2 segment with no competing DHCP server.
- Verify downloaded packages and binaries before using sudo or flashing devices.

## Anti Patterns

- Running examples on a production interface without confirming the target MAC address.
- Using the force flag to ignore storage checks without validating package size and device model.
- Treating a configure script as temporary when it persists across reset-configuration.

## Security Audit

- Audited at: 2026-07-07T07:23:59.259\+00:00
- Summary: Most static backtick findings are false positives from Markdown code formatting and examples. Confirmed risks are the sudo Netinstall commands, privileged interface configuration, a security-relevant vendor download, and a private IP setup example. Semantic review found no prompt injection, but it found root execution after download, destructive flashing risk, and first-boot device-mode changes.

## Stats

- Views: 108
- Downloads: 13
- Favorites: 0
- Popularity score: 0