mikrotik-whisperer

Manages MikroTik routers with voucher generation, hotspot control, and real-time monitoring.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill mikrotik-whisperer-alwahdi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mikrotik-whisperer
Source: https://github.com/Alwahdi/mikrotik-whisperer
Command: npx skills add https://github.com/Alwahdi/mikrotik-whisperer --skill mikrotik-whisperer-alwahdi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multiple MikroTik routers manually is error-prone and time-consuming, especially when generating hotspot vouchers, tracking sales, and monitoring router health across locations. This Skill provides the operational context and conventions of the MikroTik Whisperer platform so an agent can work within its service-layer architecture, coding standards, and RouterOS integration patterns. ## Core Features & Use Cases - Voucher Management: Bulk voucher generation with customizable prefixes, profiles, and expiry tracking via VoucherService. - Router Operations: MikroTik RouterOS command execution with retry logic, exponential backoff, and timeout handling through MikrotikService. - Sales & Monitoring: Revenue analytics, sales-point reporting, and real-time dashboard data for bandwidth and system health. - Use Case: A hotspot operator needs 100 vouchers for a '1GB-24H' profile on a specific router. The agent follows the platform's ServiceResult pattern and Zod validation rules to generate, validate, and persist the vouchers through the service layer. ## Quick Start Ask the agent to generate a batch of hotspot vouchers for a given router profile following the project's service-layer and coding guidelines.

Frequently Asked Questions about mikrotik-whisperer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate hotspot vouchers for a MikroTik router programmatically?

Use the VoucherService in the service layer, which validates parameters with Zod schemas, generates unique voucher codes with a configurable prefix, and persists them to Supabase. Bulk generation runs as a background job returning a jobId for tracking.

How does the platform handle MikroTik RouterOS connection failures?

MikrotikService wraps command execution with retry logic using exponential backoff (1s, 2s, 4s) and configurable timeouts. Errors are returned via the ServiceResult pattern with a retryable flag distinguishing network failures from validation or auth errors.

What tech stack does this MikroTik management platform use?

The stack is a Turborepo monorepo with Next.js App Router, React 19, TypeScript, Tailwind CSS, and shadcn/ui on the frontend, Supabase for auth and database, an Express-based local MikroTik agent, and an Expo mobile app.

What are the testing requirements for contributing to this project?

Services require over 80% coverage and utilities over 90%, enforced in CI. MikroTik integration tests covering connection handling, retries, and timeouts are the highest priority, with Vitest for unit tests and Playwright for E2E journeys.

When should I not use the retry mechanism for router commands?

Do not retry validation errors (400), authentication errors (401), or authorization errors (403), as these will fail deterministically. Retry only network timeouts, temporary unavailability (503), and rate limiting (429).