# Map RouterOS Command Trees

RouterOS command trees are hard to inspect and convert into schemas. This skill explains /console/inspect traversal, REST verb mapping, and safe schema generation.

## Install

```bash
npx skillstore add tikoci/routeros-command-tree
```

## Metadata

- Status: approved
- Slug: tikoci-routeros-command-tree
- Skillstore revision: r1
- Version status: missing
- Tree hash: 9e11d0f1f3b10350ee192663359eab2740f80d58f111dde0668667df789cc5d7
- Author: tikoci
- GitHub username: tikoci
- License: MIT
- Repository: https://github.com/tikoci/routeros-skills/tree/main/routeros-command-tree
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- 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, network, filesystem
- Quality score: 70
- Public page: https://skillstore.pages.dev/skills/tikoci-routeros-command-tree
- Manifest: https://skillstore.pages.dev/api/skills/tikoci-routeros-command-tree/manifest

## Capabilities

- Explains RouterOS command tree node types and path formats.
- Shows how /rest/console/inspect child and syntax requests work.
- Describes recursive traversal patterns and dangerous path skips.
- Maps RouterOS CLI commands to REST verbs for schema generation.
- Explains inspect.json, RAML, and OpenAPI output formats.

## Use Cases

- Generate RouterOS API Schemas: Convert inspected command paths into RAML or OpenAPI models for internal tooling.
- Understand RouterOS REST Mapping: Map CLI commands such as add, set, remove, and print to the correct REST verbs.
- Review Command Tree Coverage: Compare inspect.json files across RouterOS versions to document command and package differences.

## Prompt Templates

### Explain the Command Tree

```
Explain how the RouterOS command tree is structured. Include dir, path, cmd, and arg node types.
```

### Plan Inspect Traversal

```
Help me plan a RouterOS /console/inspect traversal. Include request types, path format, rate limits, and dangerous path skips.
```

### Map Commands to REST

```
Map RouterOS CLI commands to REST verbs for schema generation. Explain add, set, remove, get, print, and other commands.
```

### Design a Schema Generator

```
Design a RouterOS inspect.json to OpenAPI generator. Include traversal inputs, command mapping, argument handling, caching, and safety checks.
```

## Limitations

- Does not provide executable scripts or RouterOS credentials.
- Requires RouterOS 7.x or a cached inspect.json file for real data.
- Full live traversal can be slow and send many HTTP requests.
- Command trees vary by RouterOS version and installed packages.

## Best Practices

- Use cached inspect.json data during development whenever possible.
- Skip syntax lookups for documented dangerous path segments.
- Confirm RouterOS version and installed packages before comparing schemas.

## Anti Patterns

- Do not run full live traversal without timeouts and rate limits.
- Do not assume standard REST semantics for RouterOS create and update operations.
- Do not reuse inspect data across RouterOS versions without validation.

## Security Audit

- Audited at: 2026-07-07T06:47:25.017\+00:00
- Summary: Most static findings are false positives caused by Markdown backticks, code fences, RouterOS path examples, and local documentation links. The real concern is operational: live /console/inspect traversal can issue many RouterOS REST requests, and the skill documents syntax lookups that can crash the RouterOS HTTP server unless skipped. No prompt injection or data exfiltration intent was found.

## Stats

- Views: 105
- Downloads: 11
- Favorites: 0
- Popularity score: 0