# Build RouterOS /app YAML Manifests

RouterOS /app YAML differs from docker-compose and changes across RouterOS releases. This skill explains the format, validation choices, REST loading patterns, and common mistakes.

## Install

```bash
npx skillstore add tikoci/routeros-app-yaml
```

## Metadata

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

## Capabilities

- Explains RouterOS /app top-level and service fields.
- Shows old and new RouterOS port mapping formats.
- Describes accessIP, accessPort, containerIP, and routerIP placeholders.
- Covers app store YAML arrays and file extension conventions.
- Documents REST API add and list patterns for /app.
- Provides schema and VSCode YAML integration references.

## Use Cases

- Create RouterOS App Manifests: Draft valid /app YAML with services, ports, volumes, configs, and placeholders.
- Translate Compose Designs: Map docker-compose concepts to RouterOS /app fields and identify unsupported options.
- Document App Store Entries: Prepare app store YAML guidance, schema notes, and validation advice for router users.

## Prompt Templates

### Create a Minimal App

```
Create a minimal RouterOS /app YAML for an Nginx web service on port 8080. Explain each field briefly.
```

### Convert Compose Concepts

```
Convert this docker-compose service plan into RouterOS /app YAML. Identify unsupported fields and suggest RouterOS alternatives: [paste plan].
```

### Review a Manifest

```
Review this RouterOS /app YAML for port format, placeholders, environment variables, and unsupported compose keys: [paste YAML].
```

### Design Store Guidance

```
Design a RouterOS /app store entry for a multi-service monitoring app. Include configs, volumes, networks, validation notes, and safe credential placeholders.
```

## Limitations

- Does not connect to routers or deploy apps by itself.
- Does not guarantee behavior on unreleased RouterOS builds.
- Needs user-provided YAML to inspect a specific manifest.
- Does not replace RouterOS security review before production use.

## Best Practices

- Use pinned image versions or digests for production app definitions.
- Replace example credentials with unique secrets before deployment.
- Validate strict schemas in CI and editor schemas during authoring.

## Anti Patterns

- Assuming docker-compose fields work unchanged in RouterOS /app.
- Publishing manifests with admin:admin or changeme credentials.
- Mixing old and new port mapping styles in one service.

## Security Audit

- Audited at: 2026-07-09T09:40:21.969\+00:00
- Summary: All static command, network, role-token, and reconnaissance detections were reviewed as false positives in documentation or YAML examples. No prompt injection, host command execution, or unauthorized network behavior was found. Two content risks remain: weak example credentials and mutable image update patterns.

## Stats

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